[SERVER-37049] MongoDB 3.6.7 arbiters continuously log "Using sessions while not fully upgraded to FCV3.6" even though replset is FCV3.6 Created: 07/Sep/18  Updated: 18/Sep/18  Resolved: 07/Sep/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.6.7
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: James Kovacs Assignee: Tess Avitabile (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-36777 Excessive logging with sessions in FC... Closed
Operating System: ALL
Steps To Reproduce:

m 3.6.7
mlaunch init --replicaset --nodes 2 --arbiter
tail -f data/replset/arb/mongod.log
 

Arbiter log shows a constant stream of:

2018-09-07T11:03:32.057-0600 I -        [conn12] Using sessions while not fully upgraded to FCV3.6
2018-09-07T11:03:33.089-0600 I -        [conn11] Using sessions while not fully upgraded to FCV3.6
2018-09-07T11:03:34.060-0600 I -        [conn12] Using sessions while not fully upgraded to FCV3.6
2018-09-07T11:03:35.091-0600 I -        [conn11] Using sessions while not fully upgraded to FCV3.6

mlaunch stop
m 3.6.6
mlaunch start

Arbiter restarts and FCV messages stop appearing.

mlaunch stop
m 3.6.7
mlaunch start

Arbiter restarts and FCV messages spam the arbiter log again.

Participants:
Case:

 Description   

Arbiters in MongoDB 3.6.7 continuously log the following once per second even though the FCV for the replset is FCV3.6:

2018-09-07T11:14:41.656-0600 I -        [conn6] Using sessions while not fully upgraded to FCV3.6
2018-09-07T11:14:42.657-0600 I -        [conn10] Using sessions while not fully upgraded to FCV3.6
2018-09-07T11:14:43.657-0600 I -        [conn6] Using sessions while not fully upgraded to FCV3.6
2018-09-07T11:14:44.658-0600 I -        [conn10] Using sessions while not fully upgraded to FCV3.6

 
Verifying FCV version...

> db.adminCommand({getParameter:1, featureCompatibilityVersion:1})
{
  "featureCompatibilityVersion": {
    "version": "3.6"
  },
  "ok": 1,
  "operationTime": Timestamp(1536341388, 1),
  "$clusterTime": {
    "clusterTime": Timestamp(1536341388, 1),
    "signature": {
      "hash": BinData(0, "AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
      "keyId": NumberLong("0")
    }
  }
}



 Comments   
Comment by Kelsey Schubert [ 07/Sep/18 ]

Thanks for the clarification, Tess. This issue will be resolved in 3.6.8 by SERVER-36777.

Comment by Tess Avitabile (Inactive) [ 07/Sep/18 ]

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.

Generated at Thu Feb 08 04:44:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.