[SERVER-9672] indexes not visible while connected to replset Created: 13/May/13 Updated: 13/May/13 Resolved: 13/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Shell |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Critical - P2 |
| Reporter: | Siege Jackson | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS release 6.4 (Final) |
||
| Participants: |
| Description |
|
I'm seeing odd behavior: I have a shard that has a tagged member for ETL work, it's _id:5 in the following rs.conf():
When I connect to this secondary directly with (while logged on to the hosts console):
I get the following:
When in fact, I should see
I'm only able to get the full list of indexes when I restart the member in stand alone mode (not part of replset and on a unique port, as though I'm doing maintenance). Is this because of the tag in place on that member? |
| Comments |
| Comment by Siege Jackson [ 13/May/13 ] |
|
You can resolve this; when this was tested from earlier (4/22) this appeared to work but there was missing info. |
| Comment by Siege Jackson [ 13/May/13 ] |
|
this is user error. |
| Comment by Scott Hernandez (Inactive) [ 13/May/13 ] |
|
You are in the wrong database in the first case you provided; db is "test" (the default) not "blocks" (your user db). You did not change to the blocks db from output posted. Please run db.coll.stats() in both cases if you believe you were in the correct database and simply copied things incorrectly. |