[SERVER-24318] clarify BackgroundSync ownership Created: 31/May/16  Updated: 24/Feb/17  Resolved: 01/Jun/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.8

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-24053 Null pointer crash in BackgroundSync:... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.2
Sprint: Repl 15 (06/03/16)
Participants:
Linked BF Score: 0

 Description   

Removing BackgroundSync::get(), and removing the static instance of it, in favor of an owned single instance. This should fix the crashes that can result from a race between startup and shutdown of replication threads.



 Comments   
Comment by Githook User [ 01/Jun/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-24318 change BackgroundSync to one owned object by the Repl ExternalState, to simplify lifetime issues
Branch: master
https://github.com/mongodb/mongo/commit/b360d5833b6c20ddc64b8a18456b359aa718e3fe

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