[SERVER-36963] SessionsCollectionRS incorrectly creates and destroys RemoteCommandTargeters Created: 31/Aug/18  Updated: 29/Oct/23  Resolved: 12/Aug/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.6.7, 4.0.2, 4.1.2
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 27

 Description   

SessionsCollectionRS often sends commands from the secondary node to the primary node. When it does so, it creates a local RemoteCommandTargeter which goes out of scope after the command is sent. Along with this, a ReplicaSetMonitor is created on the RemoteCommandTargeter that is created and destroyed.

It would be cleaner for SessionsCollectionRS to hold a reference to a singular RemoteCommandTargeter upon construction.



 Comments   
Comment by Githook User [ 12/Aug/19 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-36963 SessionsCollectionRS maintains a RemoteCommandTargeter
Branch: master
https://github.com/mongodb/mongo/commit/2b2b266aef6f15d240b9ac485cee80bb09687bf5

Comment by Misha Tyulenev [ 01/Nov/18 ]

Removing from the epic as its a "nice to have" feature that makes a non-critical code path a bit faster but less reliable.

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