[SERVER-6352] Add sh.removeTagRange(ns, min, max, tag) Created: 08/Jul/12 Updated: 27/Oct/15 Resolved: 09/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | 2.1.2 |
| Fix Version/s: | 2.7.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Adam Comerford |
| Resolution: | Done | Votes: | 6 |
| Labels: | cap-ticket-needed, pull-request, sharding, tags | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Add new helper to remove a tag'd chunk range. This is important when removing tags from shards (where the tag no longer exists), as well as for testing. This should verify that the ns is aharded, and the shards contain the tag (but shouldn't stop the op) |
| Comments |
| Comment by Githook User [ 09/Jul/14 ] |
|
Author: {u'username': u'comerford', u'name': u'Adam Comerford', u'email': u'adam@comerford.cc'}Message: Adding the removeTagRange helper to match addTagRange with some informational warnings that do not stop the operation from happening. Note: does not address the fact that no feedback is given to indicate work done, or lack of work done (must check config.tags manually for results). Closes #709 Signed-off-by: Benety Goh <benety@mongodb.com> |