[SERVER-21552] Ismaster on mongos fails if no shard exists Created: 19/Nov/15 Updated: 19/Nov/15 Resolved: 19/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christian Amor Kvalheim | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | 1. bring up 1 shard |
| Participants: |
| Description |
|
When calling ismaster on the mongos proxy the command will fail if there is no shard with the following error. This is confirmed to happen on 3.0.x and earlier but not on 3.2.x.
|
| Comments |
| Comment by Andy Schwerin [ 19/Nov/15 ] |
|
I'm assuming, of course, that ismaster against the admin database is working. Otherwise, the shell and drivers would never be able to set up new sharded clusters. |
| Comment by Andy Schwerin [ 19/Nov/15 ] |
|
The improved behavior in 3.2 is the result of work we did during the refactor to enable config server replica sets. Since the workaround of running ismaster against the admin database is easy, I think we'll leave the old behavior alone on 3.0 and before. |
| Comment by Christian Amor Kvalheim [ 19/Nov/15 ] |
|
I take it back. Ismaster is in fact causing an issue. Execute ismaster against system.$cmd and it fails with the above message if there are no shards. Works perfectly on 3.2 |
| Comment by Christian Amor Kvalheim [ 19/Nov/15 ] |
|
Actually never mind there seems to be a bug in the driver. you can close this ticket. |
| Comment by Christian Amor Kvalheim [ 19/Nov/15 ] |
|
system.$cmd |
| Comment by Andy Schwerin [ 19/Nov/15 ] |
|
What's the database? Admin? |