[SERVER-62269] Optimize balancer configuration refresh Created: 24/Dec/21  Updated: 06/Dec/22  Resolved: 30/Dec/21

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

Type: Improvement Priority: Minor - P4
Reporter: Pierlauro Sciarelli Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Participants:

 Description   

TheĀ PeriodicBalancerConfigRefresher is performing 3 reads from the config server in order to refresh the balancer state, the max chunk size and the auto splitter state.

Objective of this ticket is to perform only 1 query instead of sending 3 requests over the network.



 Comments   
Comment by Kaloian Manassiev [ 30/Dec/21 ]

While this is a good performance optimisation, the calls against the config server are happening very rare and they are really cheap. Since we have not heard any complains from customers around that area, I am going to close it as won't do.

Generated at Thu Feb 08 05:54:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.