[SERVER-9376] FindAndModify not working after crash of secondary servers Created: 17/Apr/13  Updated: 10/Dec/14  Resolved: 04/Apr/14

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

Type: Question Priority: Major - P3
Reporter: Morten Fjeldstad Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I have a program that has been running perfectly for over 8 months using both mongodb 2.2 series and lately v2.4.1. I have 3 mongodb servers configured in a replicaset with authentication enabled and replication working. Life was good!

Until today.

All of a sudden BOTH the SECONDARY servers in the replicaset crash with segmentation faults at the same time!

After restarting the servers and relaunching my app, I noticed a very strange behaviour that I have no idea of how to fix:

The app can connect to the replicaset, and authenticate.
The app can query data using find().
The app can NOT succesfully run a findAndModify() command any more. It always returns nothing/null/zip/nada...

I have not done any changes to the code since it was working and I have ran the query I use for "findAndModify()" in the shell (using findOne()) and it returns the expected document.

The logs looks perfectly normal, except for the following entry that seems to coincide with when my application tries to do a findAndModify():

command denied:

{ replSetGetStatus: 1 }

Any ideas what is wrong and/or how to troubleshoot it?



 Comments   
Comment by Stennie Steneker (Inactive) [ 24/Apr/13 ]

Hi Morton,

Are you able to attach the mongod log from a secondary, or at a minimum the full log lines with the segmentation fault / stacktrace when the secondaries crashed?

We can't investigate further without more specific details.

Thanks,
Stephen

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