Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
Changelog entries for split and merge now have a new field called "owningShard" under the "details" section of the entry. This refers to the shardId of the shard that owns the chunk(s) that were split or merged.
A changelog entry for a chunk split will now look something like:
{
|
"_id" : "CSRS_primary_host:CSRS_primary_port-XXX-YYY",
|
"server" : "CSRS_primary_host:CSRS_primary_port",
|
"shard" : "config",
|
"time" : ISODate("2020-23-07T00:00:00.00"),
|
"what" : "split",
|
"ns" : "db.collection",
|
"details" : {
|
"before" : {
|
...
|
},
|
"left" : {
|
...
|
},
|
"right" : {
|
...
|
},
|
"owningShard": shardId
|
}
|
}
|
Description of Linked Ticket
After a chunk is split, a split event will be recorded in the config.changelog collection. Currently the shard name & server name recorded in this changelog is the replica set of CSRS and host:port of the CSRS primary.
"_id" : "CSRS_primary_host:CSRS_primary_port-XXX-YYY",
|
"server" : "CSRS_primary_host:CSRS_primary_port",
|
"shard" : "config",
|
It would be nice if the shard name & server could be the shard that owns the chunk. This would help to check the split activities on the shards and might help to identify hot shards etc.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-49307 In changelog, report the shard name (& server host:port) for the shard that owns the chunk, instead of CSRS replica set name (& CSRS primary host:port)
-
- Closed
-