[SERVER-13856] MongoDB crash on addition to a replica set Created: 07/May/14 Updated: 24/Jan/15 Resolved: 23/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dharshan Rangegowda | Assignee: | Matt Dannenberg |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
I added a new server to an existing replica set and the mongod instance on the new replica set hit the following assert and stopped. I am provide the full log if needed. The version is 2.4.8 Wed May 7 02:08:56.572 [conn74760] authenticate db: data { authenticate: 1, user: "admin", nonce: "b72c73378e4a2ed4", key: "ab9cb1fa033cbe6cee07d97661ac6507" }Wed May 7 02:08:56.572 [conn74767] end connection 162.243.83.99:42063 (276 connections now open) ***aborting after fassert() failure |
| Comments |
| Comment by Thomas Rueckstiess [ 24/Jul/14 ] | |||||||||||||||||||
|
Hi Dharshan, have you had a chance to read Matt's last comment? If this is still an issue for you, can you answer his questions regarding the updates? Regards, | |||||||||||||||||||
| Comment by Matt Dannenberg [ 09/Jul/14 ] | |||||||||||||||||||
|
Thanks. Your indexes do not look like they are the cause of the trouble. Do you perform any updates on the documents in the capped "cache.metrics" collection? If so, what changes are made and to which fields? | |||||||||||||||||||
| Comment by Dharshan Rangegowda [ 11/Jun/14 ] | |||||||||||||||||||
|
Here you go
| |||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 10/Jun/14 ] | |||||||||||||||||||
|
we still need more information to make progress on this ticket. If this is still an issue for you, can you please send us the information Matt requested above? Thanks, | |||||||||||||||||||
| Comment by Matt Dannenberg [ 28/May/14 ] | |||||||||||||||||||
|
Hey Dharshan, Could you please post the indexes which you have on the "cache.metrics" collection (result of db.cache.metrics.getIndexes())? Thanks, | |||||||||||||||||||
| Comment by Dharshan Rangegowda [ 25/May/14 ] | |||||||||||||||||||
|
Here you go
| |||||||||||||||||||
| Comment by Andy Schwerin [ 08/May/14 ] | |||||||||||||||||||
|
dharshanr@scalegrid.net, could you also report the capacity limit of the "cache.metrics" collection? | |||||||||||||||||||
| Comment by Andy Schwerin [ 08/May/14 ] | |||||||||||||||||||
|
The relevant log lines are the following:
dharshanr@scalegrid.net, can you please report what indexes you have on the "cache.metrics" collection? | |||||||||||||||||||
| Comment by Dharshan Rangegowda [ 08/May/14 ] | |||||||||||||||||||
|
Here you go - Full log attached. | |||||||||||||||||||
| Comment by Andy Schwerin [ 07/May/14 ] | |||||||||||||||||||
|
dharshanr@scalegrid.net, somewhere within 20-30 lines above what you posted from your logs should be a line that says something like "fassert failed" and a number. Can you paste the logs from there to the end? |