Loading...

XML

Word

Printable

JSON

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4
Steps To Reproduce:
Hide

The following test passes:

(function() { "use strict"; var rst = new ReplSetTest({nodes: 1}); rst.startSet(); rst.initiate(); var node = rst.getPrimary(); assert(!node.adminCommand({replSetGetConfig: 1}).config.hasOwnProperty("term")); assert.commandWorked(node.adminCommand({replSetStepDown: 1, force: true})); sleep(2000); assert.commandWorked(node.adminCommand({replSetStepUp: 1})); assert(!node.adminCommand({replSetGetConfig: 1}).config.hasOwnProperty("term")); rst.stopSet(); })();
Show
The following test passes: (function() { "use strict" ; var rst = new ReplSetTest({nodes: 1}); rst.startSet(); rst.initiate(); var node = rst.getPrimary(); assert (!node.adminCommand({replSetGetConfig: 1}).config.hasOwnProperty( "term" )); assert .commandWorked(node.adminCommand({replSetStepDown: 1, force: true })); sleep(2000); assert .commandWorked(node.adminCommand({replSetStepUp: 1})); assert (!node.adminCommand({replSetGetConfig: 1}).config.hasOwnProperty( "term" )); rst.stopSet(); })();
Sprint:
Repl 2020-04-06, Repl 2020-04-20
Linked BF Score:
50

After ~~SERVER-46571~~, the initial replica set config term is -1. The replica set config term only gets incremented on stepup if the config term is initialized. Thus the config term does not get initialized until the user runs a replSetReconfig command.

related to

SERVER-46571 Shard server replica set nodes shouldn't write config 'term' field on startup in FCV 4.2

SERVER-45081 Increment the config term via reconfig on step-up

SERVER-47189 Do a safe reconfig to add config term on upgrade to FCV=4.4