You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[FAB-3185] move historyDatabase to ledger in core.yaml
historyDatabase is under 'state' section in core.yaml. 'history'
should be a peer of 'state', with the config option being called
something like enableHistoryDatabase. This will allow for other history
config options distinct from state config options.
This is the default core.yaml with the new history section and
enableHistoryDatabase config option:
ledger:
blockchain:
state:
# stateDatabase - options are "goleveldb", "CouchDB"
# goleveldb - default state database stored in goleveldb.
# CouchDB - store state database in CouchDB
stateDatabase: goleveldb
couchDBConfig:
couchDBAddress: 127.0.0.1:5984
username:
password:
# Number of retries for CouchDB errors
maxRetries: 3
# Number of retries for CouchDB errors during peer startup
maxRetriesOnStartup: 10
# CouchDB request timeout (unit: duration, e.g. 20s)
requestTimeout: 20s
# Limit on the number of records to return per query
queryLimit: 10000
history:
# enableHistoryDatabase - options are true or false
# Indicates if the history of key updates should be stored in goleveldb
enableHistoryDatabase: true
The history section in chaincodetest.yaml is not used, update it for
consistency.
Change-Id: I15ac35e280dbf194647ca0c866fcbee515af8a68
Signed-off-by: Chris Elder <[email protected]>
0 commit comments