[SERVER-16032] Replication should not have multiple active OperationContexts on the same thread Created: 07/Nov/14  Updated: 04/Dec/14  Resolved: 01/Dec/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.8.0-rc2

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-14062 Remove the global OperationContext re... Closed
Related
is related to SERVER-15957 Get OperationContext for ReplicationC... Closed
Participants:

 Description   

Currently there are two call stacks which do that:

 m31000|  mongod(mongo::OperationContextImpl::OperationContextImpl() 0xF4) [0xaf3e34]
 m31000|  mongod(mongo::repl::startMasterSlave() 0x1A) [0xc37ada]
 m31000|  mongod(mongo::repl::ReplicationCoordinatorImpl::startReplication(mongo::OperationContext*) 0xE0) [0xc61c40]
 m31000|  mongod(mongo::initAndListen(int) 0x1954) [0x7e3744]

and

 m31100|  mongod(mongo::OperationContextImpl::OperationContextImpl() 0xF4) [0xaf3e34]
 m31100|  mongod(mongo::repl::ReplicationCoordinatorExternalStateImpl::createOperationContext(std::string const&) 0x34) [0xc552f4]
 m31100|  mongod(mongo::repl::ReplicationCoordinatorImpl::signalDrainComplete() 0xAB) [0xc64c9b]
 m31100|  mongod(mongo::repl::SyncTail::tryPopAndWaitForMore(mongo::repl::SyncTail::OpQueue*, mongo::repl::ReplicationCoordinator*) 0x34D) [0xccd40d]
 m31100|  mongod(mongo::repl::SyncTail::oplogApplication() 0x450) [0xcceb10]
 m31100|  mongod(mongo::repl::runSyncThread() 0x1DF) [0xcc576f]



 Comments   
Comment by Githook User [ 01/Dec/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-16032 Prevent applier from creating a new OperationContext when there is already one active
Branch: master
https://github.com/mongodb/mongo/commit/2684c73fc835681b00f9822009a5621fb12d26bc

Comment by Githook User [ 24/Nov/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-16032 SERVER-15957 Get OperationContext for ReplicationCoordinator::signalDrainComplete from the caller
Branch: master
https://github.com/mongodb/mongo/commit/725c657adc955aed8f832641553861162b448d18

Comment by Githook User [ 14/Nov/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-16032 Don't create a new OperationContext for starting master/slave
Branch: master
https://github.com/mongodb/mongo/commit/3a8c58f22a02fca264932802596a223b4e49efcb

Comment by Githook User [ 13/Nov/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: Revert "SERVER-16032 SERVER-15957 Get OperationContext for ReplicationCoordinator::signalDrainComplete from the caller"

This reverts commit 622bb23dca571100644c8dd927bd844a3ceae19e.
Branch: master
https://github.com/mongodb/mongo/commit/d1cba25b72f41a2374eae4f74e12299196149580

Comment by Githook User [ 12/Nov/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-16032 SERVER-15957 Get OperationContext for ReplicationCoordinator::signalDrainComplete from the caller
Branch: master
https://github.com/mongodb/mongo/commit/622bb23dca571100644c8dd927bd844a3ceae19e

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