[SERVER-15511] Segfault in ismaster1.js due to accessing _members without locking in ReplSetImpl::shouldChangeSyncTarget Created: 02/Oct/14  Updated: 25/Oct/14  Resolved: 02/Oct/14

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

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

TEST HISTORY

http://buildlogs.mongodb.org/MCI_amazon/builds/108094/test/replicasets_auth_0/ismaster1.js

Error while calling isMaster on connection to ip-10-95-186-41:31002: Error: socket exception [CONNECT_ERROR] for 127.0.0.1:31002 (127.0.0.1) failed
assert.soon failed, msg:Nodes did not sync in less than a minute
Error: assert.soon failed, msg:Nodes did not sync in less than a minute
    at Error (<anonymous>)
    at doassert (src/mongo/shell/assert.js:11:14)
    at Function.assert.soon (src/mongo/shell/assert.js:181:51)
    at /data/mci/shell/src/jstests/replsets/ismaster1.js:203:8



 Comments   
Comment by Githook User [ 02/Oct/14 ]

Author:

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

Message: SERVER-15511 Make sure to lock when accessing _members in ReplSetImpl::shouldChangeSyncTarget
Branch: master
https://github.com/mongodb/mongo/commit/84220a31cdcda093347dea33fce56bcfdc4fe9ed

Comment by Eric Milkie [ 02/Oct/14 ]

Looks like a segfault in BGSync::shouldChangeSyncTarget(). The locking must be problematic, since it was in the middle of a reconfig when the crash occurred. Spencer can you take a look?

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