Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Minor - P4
Fix Version/s: 4.0.20, 4.2.8, 4.4.0-rc8, 4.2.9, 4.7.0
Affects Version/s: 3.6.8
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4, v4.2, v4.0
Sprint:
Sharding 2020-06-01
Case:
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

duplicates

SERVER-36964 Prevent secondaries in SessionsCollectionRS from attempting to set up the sessions collection.

Closed

related to

SERVER-54064 Sessions on arbiters accumulate and cannot be cleared out

Closed

SERVER-48674 Check if replication is enabled before checking if the node is an arbiter in LogicalSessionCacheImpl

Closed

Assignee:: Cheahuychou Mao
Reporter:: Misha Tyulenev (Inactive)
Participants:: Blake Oler, Cheahuychou Mao, Githook User, Misha Tyulenev
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Apr 02 2019 02:49:48 PM UTC
Updated:: Oct 29 2023 10:22:23 PM UTC
Resolved:: May 20 2020 10:28:32 AM UTC
Confidence Status Last Update:: 15/May/20 6:34 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates