[SERVER-12603] Improve handling of wrong tag ranges Created: 04/Feb/14  Updated: 04/Feb/14  Resolved: 04/Feb/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.9
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andre Spiegel Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6357 Add tag based sharding commands Closed
Participants:

 Description   

A customer defined tag ranges for a collection but used the wrong shard key in sh.addTagRange(). The collection was sharded on (files_id:1,n:1) but the tag ranges defined for _id. (This was a GridFS fs.chunks collection.)

The sh.addTagRange() command worked without error, but the balancer failed as soon as it got to the offending definition (you could see that in the log files). As a result, none of the collections were properly balanced (because it failed before it started doing anything).

I see two desirable improvements:

  • The sh.addTagRange() command should fail if the shard key definition does not match.
  • In the event of a wrong setting for one collection, the balancer should still balance any other collections, rather than failing completely.


 Comments   
Comment by Scott Hernandez (Inactive) [ 04/Feb/14 ]

dup of SERVER-6357

Comment by Scott Hernandez (Inactive) [ 04/Feb/14 ]

Balancing is per collection and should not fail completely if there is a problem with one collection. Please file a bug (not improvement) if you can reproduce that and remove it from here.

Generated at Thu Feb 08 03:29:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.