[SERVER-14185] Mongo Crashed after StepDown Created: 06/Jun/14 Updated: 10/Jun/14 Resolved: 09/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.6.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Himanshu Matta | Assignee: | Bruce Lucas (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | replication | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS - Amazon Linux |
||
| Issue Links: |
|
||||||||||||
| Operating System: | Linux | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Hi, When we fire "rs.stepDown()" command then our primary gets crashed instead of converting to Secondary. It shouldn't happen. Please figure it, why it's happening ? Let me know if you want anything else. |
| Comments |
| Comment by Bruce Lucas (Inactive) [ 09/Jun/14 ] |
|
We'll track the fix for the issue with mapReduce and stepDown in |
| Comment by J Rassi [ 09/Jun/14 ] |
|
xbhanu: you're encountering |
| Comment by Bhanu [ 09/Jun/14 ] |
|
Yup. It started happening with me today as well. Pasting the error snippet from logs:- 2014-06-09T07:11:40.856-0400 [conn20] replSet info voting yea for arsenic43.nyc:27017 (4) |
| Comment by Himanshu Matta [ 06/Jun/14 ] |
|
Yes, Solve this asap. |
| Comment by Himanshu Matta [ 06/Jun/14 ] |
|
Forget about Drivers version. Let's focus only on mongod process crashed issue which is not related to any driver version. We found two types of logs which seems related to crashed- ***aborting after fassert() failure 2014-06-03T12:33:13.845+0000 [conn1552] SEVERE: Got signal: 6 (Aborted). 2)2014-06-03T12:02:54.929+0000 [rsHealthPoll] warning: Failed to connect to 10.0.0.67:10007, reason: errno:111 Connection refused Let me know if these logs are not enough then I'll upload the whole log file. |
| Comment by Jeremy Mikola [ 06/Jun/14 ] |
|
Please elaborate on the actual errors you are seeing. Saying the "primary gets crashed" implies that the mongod process itself is terminating, which wouldn't have much to do with the driver. If you mean to say that the driver is crashing, please specify if there is a segfault or simply an exception. And if so, either provide the core dump or full stack trace, respectively. Server logs for the relevant mongod processes would be helpful in the event of a server crash. For diagnosing a driver crash or error, please attempt to collect driver logs via the MongoLog class. The example on MongoLog::setCallback() can be used to collect log info at all levels and from all modules within the driver. You can customize the callback function accordingly to either print the output directly or append it to an output file. Lastly, I see that you mentioned driver version 1.4.1 in the "Environment" field of this ticket, but the "Affects Version" is 1.5.0. Please confirm which driver version you are using. If you are on 1.4.1, note that it was released approximately one year ago. I would suggest you update to a more recent version and attempt to reproduce your issue with 1.5.3 (the latest stable release). Versions may be found on http://pecl.php.net/mongo |