[SERVER-1614] [replica sets] issues after running repair Created: 11/Aug/10 Updated: 12/Jul/16 Resolved: 11/Aug/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.6.0 |
| Fix Version/s: | 1.6.1, 1.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
To reproduce: 1. Set up a replica set with three members. Initialize it. Each set displays this: In addition, if you look at the original master, collections appear to be missing from the local database: This case is also confirmed by the two reports mentioned in this forum post: |
| Comments |
| Comment by auto [ 16/Aug/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: |
| Comment by auto [ 11/Aug/10 ] |
|
Author: {'login': 'dwight', 'name': 'dwight', 'email': 'dwight@10gen.com'}Message: |
| Comment by Dwight Merriman [ 11/Aug/10 ] |
|
WORKAROUND / to fix this Cause : local.system.replset not recreated on a repair. Workaround : manually repopulate it with the single config document. Recommend you backup first. Basically what we want to do is (from the shell) : > use local however, the above won't work as you can't normally insert directly into a system collection. there is a hacky workaround though using rename: > use local Pretty sure it will work after that. You probably only have to do a single member and it will all come back then (I think). Let me know. |
| Comment by Kyle Banker [ 11/Aug/10 ] |
|
Here's some more incredibly unusual behavior. After repairing, I connect to the original master node. Since there's no primary, I set slave ok: > db.getMongo().setSlaveOk(); After running those commands, the db segfaults: Wed Aug 11 13:48:57 [initandlisten] connection accepted from 127.0.0.1:53058 #3 Wed Aug 11 13:49:15 Backtrace: Wed Aug 11 13:49:15 dbexit: |