[SERVER-9416] ns name too long leads to Fatal Assertion 16360 and replica set failure Created: 22/Apr/13 Updated: 10/Dec/14 Resolved: 29/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Oskar Liljeblad | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian GNU/Linux unstable, mongodb-server 1:2.4.2-1 |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Originally we had three servers in the replica set, but now only one. The reason is that as soon as we add another, they will crash with the following error, and the PRIMARY server will become SECONDARY.
It didn't matter that we removed the collection - it seemed to be replicated from the journal on some server somehow. To fix the problem we had to remove all the data files on a server and restart replication. So it is not reproducable right now. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 29/Aug/13 ] | |
|
duplicate of | |
| Comment by Stennie Steneker (Inactive) [ 03/May/13 ] | |
|
Hi Oskar, Thank you for reporting this bug; I have been able to reproduce the issue using MongoDB 2.4.2. From the error message provided, it appears that the namespace which is too long is a temporary collection for a MapReduce job:
There is some extra padding reserved for the namespace, so while your namespace is 121 characters it does trigger the 128 character error on the first attempt to insert into the collection. However, subsequent insertions succeed and insert an entry into the oplog with the long namespace. As a consequence, these insertions are creating oplog entries which cannot be applied on the secondary and trigger the Fatal Assertion 16360 that you encountered. We will investigate the code fix for this issue. Regards, | |
| Comment by Oskar Liljeblad [ 22/Apr/13 ] | |
|
I should also note that the collection causing the problem is db: metadata_0bff5fe8-8f84-4122-a618-460b63bac265 (102 characters including '.') |