[SERVER-23025] Add logging to inform where split points are chosen in shardCollection with hashed key Created: 09/Mar/16  Updated: 05/Apr/17  Resolved: 11/Jan/17

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

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-01-02
Participants:
Linked BF Score: 0

 Description   

BF-1916 is an instance where shardCollection with a hashed key fails to split any chunks. There isn't enough logging to make it clear where in the logic it decided there should be no split points, and the failure has not been reproducible.

The logs do say "going to create 1 chunk(s) for", which indicates that no split points were provided by the time ChunkManager::createFirstChunks starts its for-loop to perform splits.

Add some logging to pinpoint where between the shardCollection command and the createFirstChunks call the split points can fail to be created, so that if the BF ever happens again it can be fixed.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 11/Jan/17 ]

The BF has been resolved, closing as won't fix.

Comment by Kaloian Manassiev [ 10/Jan/17 ]

dianna.hohensee, can you add the appropriate logging here or close if the linked BF has been fixed?

Generated at Thu Feb 08 04:02:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.