[DOCS-7112] Add a warning that movePrimary may build indexes in the foreground Created: 08/Feb/16 Updated: 30/Oct/23 Resolved: 12/Aug/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Steve Renaker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 26 weeks, 5 days ago | ||||||||
| Description |
|
When running the movePrimary command, if the recipient shard doesn't have any of the indexes that the source shard has, it will build those indexes on the destination shard in the foreground, potentially blocking the shard for a long time. |
| Comments |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Githook User [ 12/Aug/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message:
Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by Spencer Brody (Inactive) [ 09/Feb/16 ] |
|
Ugh, yeah you're right, building the index on the destination shard won't work as a workaround because it will cause the movePrimary to fail because the collection already exists on the destination shard. |