[SERVER-10590] can't run rs.status(), invalid utf-8 string Created: 21/Aug/13 Updated: 10/Dec/14 Resolved: 24/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | charity majors | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Around 10:40 pm last night, all my mongo alerts went off for one of our shards because rs.status() is now returning junk. parse:PRIMARY> rs.status() It's returning the same junk on the primary and all secondaries. Any idea how to fix? It's basically impossible for us to run a repairDatabase on this shard due to the 1) size of the data and 2) resetting all the padding factors would kill us. Thanks. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 24/Aug/13 ] |
|
moved to community private ticket. |
| Comment by charity majors [ 21/Aug/13 ] |
|
Any ideas for narrowing down the corrupted collection? I'm able to run db.stats() on all databases. Not finding anything in the log around that time. Happy to upload the logfile if you move this ticket to private. |
| Comment by charity majors [ 21/Aug/13 ] |
|
Replication is also busted. Wed Aug 21 16:24:03 [rsSync] Assertion: 10334:Invalid BSONObj size: 247791731 (0x7300C50E) first element: ¹^HÈ@@^Ptimezone_offset_epoch_ms: ?type=-16 |