storepool can panic if relocation happens before gossip update. #96654
Labels
A-kv-distribution
Relating to rebalancing and leasing.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-kv
KV Team
When restarting node in an active cluster sometime it fails with:
Panic is not persistent and starting node again helps.
It seem to be caused by:
StorePool update in allocator:
cockroach/pkg/kv/kvserver/allocator/storepool/store_pool.go
Lines 621 to 627 in 5cf0823
For store which received no gossip info yet.
Existing null check is pointless as
GetStoreDetailLocked
always returns info, but it could be unpopulated.Jira issue: CRDB-24266
The text was updated successfully, but these errors were encountered: