[SERVER-2525] Segfaults can occur when attaching to a mongod process going down Created: 10/Feb/11  Updated: 12/Jul/16  Resolved: 04/Mar/11

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

Type: Bug Priority: Minor - P4
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 2.6.35-25-generic


Attachments: File shard_start_mongod.js    
Operating System: Linux
Participants:

 Description   

If connecting to a mongod process going down, it appears that a segfault can occur if the process goes down while negotiating a connection. Steps to reproduce are basically:

Start up a mongod instances of shutting down

Connect to the instance (may not be necessary)
Send a term signal to the instance
Try to reconnect to the instance while in the process of shutting down

Attachment only runs on linux.

Not really a big issue for the shell, though somewhat annoying, but in general may affect stability of replica failover and sharding.



 Comments   
Comment by Greg Studer [ 10/Feb/11 ]

Fix completed, waiting for 1.8

Comment by Greg Studer [ 10/Feb/11 ]

Shell-specific error, caused by assertation error thrown in callback propagating up to spidermonkey code. Does not affect replication/sharding.

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