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
To account for cases when peer and couchdb start at same time,
2 minutes of retries are done. This does not work well for chaincode
execution though. Need to fix it such that peer startup verification
retries more times than endorsement/commit interactions with CouchDB,
ideally configurable.
Add two new CouchDB configuration options in core.yaml
couchDBConfig:
couchDBAddress: 127.0.0.1:5984
username:
password:
maxRetries: 3
maxRetriesOnStartup: 10
- maxRetries will control the max number of retries for http errors
when connecting with CouchDB.
- maxRetriesOnStartup will be a separate configuration option for
specifying the number of retries during startup. This needs to be
a larger number than the normal retries.
- Handling of 404 error is already handled correctly
- 500 errors and 4XX errors will not be retried.
- Add a change to VerifyConnection to allow for the maxRetriesOnStartup to
be used for retry logic in handleRequest
Change-Id: Ibdf48444ef0728825a168bf4deebde5fa43f12ac
Signed-off-by: Chris Elder <[email protected]>
0 commit comments