Skip to content

Commit

Permalink
Update primary reconfig configs (#4167)
Browse files Browse the repository at this point in the history
Co-authored-by: Sid Sethi <3323835+SidSethi@users.noreply.github.com>
  • Loading branch information
dmanjunath and SidSethi committed Oct 25, 2022
1 parent 06233f8 commit 9d0338e
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
1 change: 1 addition & 0 deletions creator-node/compose/env/base.env
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ enforceWriteQuorum=true
recoverOrphanedDataQueueRateLimitInterval=60000 #1min in ms
recoverOrphanedDataQueueRateLimitJobsPerInterval=1
mergePrimaryAndSecondaryEnabled=true
reconfigModePrimaryOnly=false

# peerSetManager
peerHealthCheckRequestTimeout=2000 # ms
Expand Down
5 changes: 2 additions & 3 deletions creator-node/src/config.js
Original file line number Diff line number Diff line change
Expand Up @@ -449,7 +449,7 @@ const config = convict({
doc: 'Override for `snapbackHighestReconfigMode` to only reconfig primary from replica set',
format: Boolean,
env: 'reconfigModePrimaryOnly',
default: false
default: true
},
devMode: {
doc: 'Used to differentiate production vs dev mode for node',
Expand Down Expand Up @@ -669,8 +669,7 @@ const config = convict({
doc: "Max number of seconds since first failed health check before a primary's users start issuing replica set updates",
format: 'nat',
env: 'maxNumberSecondsPrimaryRemainsUnhealthy',
// 24 hours in seconds
default: 86400 // 24hr in s
default: 600 // 10min in s
},
maxNumberSecondsSecondaryRemainsUnhealthy: {
doc: "Max number of seconds since first failed health check before a secondary's users start issuing replica set updates",
Expand Down

0 comments on commit 9d0338e

Please sign in to comment.