Menu
I have upgraded MongoDB replica set to 3.6 following this instruction https://docs.mongodb.com/manual/release-notes/3.6-upgrade-replica-set/. When I executed command
db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } )
both Primary and Secondary updated feature compatibility to 3.6, but Arbiter feature compatibility remained 3.4.
Why it remained 3.4 and how to make Arbiter have same feature compatibility as Primary as Secondary?
385
The Arbiter acts as the primary enemy of the game, charged with the destruction of humanity by the Prophet of Regret. He is ultimately killed by human forces at the game's climax.
Node replication is the process of incrementally copying, or replicating , data that belongs to backup-archive client nodes. Data is replicated from one Tivoli® Storage Manager server to another Tivoli Storage Manager server. The server from which client node data is replicated is called a source replication server .
Arbiters are mongod instances that are part of a replica set but do not hold data (i.e. do not provide data redundancy). They can, however, participate in elections. Arbiters have minimal resource requirements and do not require dedicated hardware.
b) A replica set in MongoDB is a group of mongod processes that provide redundancy and high availability. c) You can also maintain an arbiter as part of a replica set. Explanation: Data redundancy is reduced by replicating the copies of data.
From MongoDB 3.6.7 arbiters continuously log "Using sessions while not fully upgraded to FCV3.6" even though replset is FCV3.6:
Arbiters always have the downgrade value of FCV, regardless of the FCV of the replica set. So if the arbiter has binary version 3.6, it will always have FCV=3.4. They never learn the FCV, since they do not replicate the admin.system.version collection. Arbiters' behavior is not allowed to depend on FCV for this reason.
77
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
