[SERVER-5150] drop collection : now errors with sharding Created: 29/Feb/12 Updated: 08/Apr/12 Resolved: 03/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Brett Goldstein | Assignee: | Greg Studer |
| 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 |
|
I added sharding to a collection with ~ 3 million documents but as the balancing seemed to have a performance impact, I dropped the collection. I added the shard key and index and as data was fed back in, errors started to appear. This includes from the shell: mongos> db.cta.count() ", From mongos, I have the following: Wed Feb 29 16:58:05 [Balancer] distributed lock 'balancer/my07apl01.cityofchicago.org:27017:1330355727:1804289383' acquired, ts : 4f4ead7d2d46e699744598a6 Wed Feb 29 16:58:21 [conn1869] going to retry checkShardVersion host: mongos3a:27018 { oldVersion: Timestamp 9000|0, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Wed Feb 29 16:58:21 [conn1869] going to retry checkShardVersion host: mongos3a:27018 { oldVersion: Timestamp 9000|0, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Wed Feb 29 16:58:21 [conn1869] going to retry checkShardVersion host: mongos3a:27018 { oldVersion: Timestamp 9000|0, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Wed Feb 29 16:58:21 [conn1869] setShardVersion failed host: mongos3a:27018 { oldVersion: Timestamp 9000|0, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Wed Feb 29 16:58:21 [conn1869] Assertion: 10429:setShardVersion failed host: mongos3a:27018 { oldVersion: Timestamp 9000|0, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }0x535572 0x7f4556 0x7f3d2d 0x7f3d2d 0x7f3d2d 0x7f3d2d 0x7f3d2d 0x7f3d2d 0x5c1e06 0x5bffe7 0x79879b 0x793175 0x76cf2b 0x7b4927 0x7c6cf1 0x5e6a07 0x3144a0673d 0x3143ed44bd Any ideas? thx |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 03/Apr/12 ] |
|
this duplicates |
| Comment by Daniel Pasette (Inactive) [ 03/Apr/12 ] |
|
Root issue is: To workaround, try running on all mongos: db.adminCommand("flushRouterConfig"). |
| Comment by Brett Goldstein [ 01/Mar/12 ] |
|
this showed up in the logs this morning. No known precursing action: Thu Mar 1 08:08:40 [Balancer] distributed lock 'balancer/my07apl01.cityofchicago.org:27017:1330355727:1804289383' acquired, ts : 4f4f82e82d46e6997445b7b2 Thu Mar 1 08:08:55 [conn411] going to retry checkShardVersion host: mongos1a:27018 { oldVersion: Timestamp 272000|1, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Thu Mar 1 08:08:55 [conn411] going to retry checkShardVersion host: mongos1a:27018 { oldVersion: Timestamp 272000|1, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Thu Mar 1 08:08:55 [conn411] going to retry checkShardVersion host: mongos1a:27018 { oldVersion: Timestamp 272000|1, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Thu Mar 1 08:08:55 [conn411] setShardVersion failed host: mongos1a:27018 { oldVersion: Timestamp 272000|1, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 }Thu Mar 1 08:08:55 [conn411] Assertion: 10429:setShardVersion failed host: mongos1a:27018 { oldVersion: Timestamp 272000|1, assertion: "assertion s/d_state.cpp:529", errmsg: "db assertion failure", ok: 0.0 |