[SERVER-36248] Do not reject sessions in FCV 3.4 Created: 23/Jul/18  Updated: 29/Oct/23  Resolved: 26/Jul/18

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-36241 Disable implicit session in major_ver... Closed
is duplicated by SERVER-36563 forcePrimaryRefreshAndWaitForReplicat... Closed
Related
is related to SERVER-36777 Excessive logging with sessions in FC... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-07-30
Participants:
Linked BF Score: 40

 Description   

There are several issues related to how server should work with sessions in FCV3.4

  • Mongo drivers v3.6 use implicit sessions regardless if the binary is FCV3.4 or FCV3.6: SERVER-33763
  • MongoDB fails upgrade /downgrade if it creates sessions collection: SERVER-35795, SERVER-34683

so this leads that for the transient FCV3.4 we need some form of a non -persistent sessions supported by a server i.e. provide the best effort and predictable failure which allows drivers to use implicit sessions with FCV3.4



 Comments   
Comment by Githook User [ 26/Jul/18 ]

Author:

{'username': 'mikety', 'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com'}

Message: SERVER-36248 Do not reject sessions in FCV 3.4
Branch: v3.6
https://github.com/mongodb/mongo/commit/1dd7544c6db8b7def577400a3ec354d5cc8a9c97

Comment by Ian Whalen (Inactive) [ 26/Jul/18 ]

kaloian.manassiev misha.tyulenev schwerin we've now had this 100% breakage on master rhel 6.2 since the ~22nd. Can we please prioritize getting this in?

Comment by Ian Whalen (Inactive) [ 24/Jul/18 ]

kaloian.manassiev it'd be great if you could prioritize this review please. We've got 100% broken tests on 4.0 and master which this should address.

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