-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Critical - P2
-
None
-
Affects Version/s: 3.6.0-rc3
-
Component/s: Replication
-
None
-
Replication
-
ALL
After SERVER-31777, arbiters no longer report logicalSessionTimeoutMinutes:
repl0:ARBITER> db.version()
3.6.0-rc3-54-gbf53cbe
repl0:ARBITER> db.isMaster()
{
"hosts" : [
"localhost:27017",
"localhost:27018"
],
"arbiters" : [
"localhost:27019"
],
"setName" : "repl0",
"setVersion" : 1,
"ismaster" : false,
"secondary" : false,
"primary" : "localhost:27017",
"arbiterOnly" : true,
"me" : "localhost:27019",
"lastWrite" : {
"opTime" : {
"ts" : Timestamp(1510354652, 1),
"t" : NumberLong(1)
},
"lastWriteDate" : ISODate("2017-11-10T22:57:32Z"),
"majorityOpTime" : {
"ts" : Timestamp(1510354652, 1),
"t" : NumberLong(1)
},
"majorityWriteDate" : ISODate("2017-11-10T22:57:32Z")
},
"maxBsonObjectSize" : 16777216,
"maxMessageSizeBytes" : 48000000,
"maxWriteBatchSize" : 100000,
"localTime" : ISODate("2017-11-10T22:57:45.968Z"),
"minWireVersion" : 0,
"maxWireVersion" : 6,
"readOnly" : false,
"ok" : 1
}
repl0:ARBITER> db.adminCommand({'getParameter':1, featureCompatibilityVersion:1})
{ "featureCompatibilityVersion" : { "version" : "3.4" }, "ok" : 1 }
This breaks the Driver Sessions spec process for How to Check Whether a Deployment Supports Sessions.
- causes
-
-
- Closed
-
- is depended on by
-
DRIVERS-423 Non data-bearing servers must be excluded when determining if a cluster supports sessions
-
- Closed
-