[SERVER-8260] Sharded Cluster not working when one of the shard is gone Created: 22/Jan/13 Updated: 24/Jan/13 Resolved: 22/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Joseph Chua | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | replication, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
windows 2008 R2 |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
I setup a testing environment to test the availability of sharded Mongo cluster. Below is my setup: After the above setup is done, a db and a collection of the db are enabled with sharding. Shared collection is then populated with some data. By checking shard status, it is confirmed that both shards carry data in the sharded collection. Then the following steps are taken for the sharded cluster availability test. From the result of this test, it looks like the sharded cluster will stop working once any one of the shard in the cluster is gone. Per Mongo documentation, it is not the expected behavior. Can you point out if there is anything wrong in my setup/steps above? Thanks |
| Comments |
| Comment by Joseph Chua [ 24/Jan/13 ] |
|
I did post the same in the forum but get no answer so far. That is why I post the question here... |
| Comment by Ian Whalen (Inactive) [ 22/Jan/13 ] |
|
HI Joseph, this project is intended for feature requests and bug fixes. For questions like this please create a new discussion in our forum at https://groups.google.com/forum/?fromgroups#!forum/mongodb-user - if the discussion there leads to the conclusion that this should be a feature request or bug ticket, then you should follow up with a ticket here. |