[SERVER-40441] Arbiter nodes log error messages when try to create session collection or check if it exists Created: 02/Apr/19  Updated: 29/Oct/23  Resolved: 20/May/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.8
Fix Version/s: 4.0.20, 4.2.8, 4.4.0-rc8, 4.2.9, 4.7.0

Type: Bug Priority: Minor - P4
Reporter: Misha Tyulenev Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
duplicates SERVER-36964 Prevent secondaries in SessionsCollec... Closed
Related
related to SERVER-54064 Sessions on arbiters accumulate and c... Closed
related to SERVER-48674 Check if replication is enabled befor... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4, v4.2, v4.0
Sprint: Sharding 2020-06-01
Participants:
Case:

 Description   

Arbiters do not need to try to set up sessions collection.
Currently they are (3.6.8 - confirmed) [LogicalSessionCacheReap] Sessions collection is not set up; waiting until next sessions reap interval: Can not create config.system.sessions collection



 Comments   
Comment by Githook User [ 10/Jun/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-40441 Make arbiters not try to setup the sessions collection or check if it exists in LogicalSessionCache refresh/reap thread

(cherry picked from commit 35c86a14e2ad2ef8d14fe7ea3ea02951f30e646a)
Branch: v4.0
https://github.com/mongodb/mongo/commit/7648b1dd2ff5d90d48e2df144b851be7cb388b3d

Comment by Githook User [ 10/Jun/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-40441 Make arbiters not try to setup the sessions collection or check if it exists in LogicalSessionCache refresh/reap thread

(cherry picked from commit 35c86a14e2ad2ef8d14fe7ea3ea02951f30e646a)
Branch: v4.2
https://github.com/mongodb/mongo/commit/e67ebe7d74a60bd414fe7bd8b617d8a896dcec42

Comment by Githook User [ 01/Jun/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-40441 Make arbiters not try to setup the sessions collection or check if it exists in LogicalSessionCache refresh/reap thread

(cherry picked from commit 35c86a14e2ad2ef8d14fe7ea3ea02951f30e646a)
Branch: v4.4
https://github.com/mongodb/mongo/commit/644bfcb9c679a47f5a492c7aa38671e5f812f069

Comment by Githook User [ 20/May/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-40441 Make arbiters not try to setup the sessions collection or check if it exists in LogicalSessionCache refresh/reap thread
Branch: master
https://github.com/mongodb/mongo/commit/35c86a14e2ad2ef8d14fe7ea3ea02951f30e646a

Comment by Misha Tyulenev [ 23/Apr/20 ]

Arbiters are showing the

Sessions collection is not set up; waiting until next sessions refresh interval: config.system.sessions does not exist

error each time the refresh logical sessions cache is running.
SERVER-36964 is not fixing the issue with arbiters as it fails at the time it checks the existence of the config.system.sessions collection

Comment by Misha Tyulenev [ 02/Apr/19 ]

Thanks blake.oler resolving as a dup

Comment by Blake Oler [ 02/Apr/19 ]

Additionally, I think this was fixed by SERVER-36964 which went in with 3.6.9. With that change, secondaries (and arbiters) will not attempt to create the sessions collection.

Comment by Blake Oler [ 02/Apr/19 ]

misha.tyulenev This error code is misleading – all this message means is that we're not in FCV 3.6.

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