|
There are multiple small reasons for this, none of them is absolute must but all together seems beneficial:
1. Uniformity, there should be an easy way to just tell this shard is special
2. Eventually will be needed for discovery, even if we don't do it now
3. Make ShardRegistry tight, right now it stores 2 shards - one with config name and another with custom name, and no way to tell this is the same shard
4. The 'isConfig()' on catalog shard with custom name currently returns false, however it is config
5. Fix that 'reconfig' problem, while the right fix with making the shard to update CSRS will be done later
|