aruraghuwanshi opened a new issue, #16433:
URL: https://github.com/apache/druid/issues/16433

   Please provide a detailed title (e.g. "Broker crashes when using TopN query 
with Bound filter" instead of just "Broker crashes").
   
   ### Affected Version
   
   Version 28.0.1
   (Unsure if it exists in earlier versions)
   
   ### Description
   
   Coordinator leader does not assign new Segment Load Queues until all 
historicals have finished ingesting the segments from their previous 
assignments. 
   
   Scenario:
   
   - In a cluster size of **M** historicals, a large volume of segments 
(upwards of 8Tb) need to be decommissioned off of **n** historicals.
   - The coordinator then assigns load queues to all the other remaining 
**M-n** historicals. 
   - The first historical finishes loading its segment queue in time **t**,  
while the historical that finishes last finishes loading in time **T**.
   - All historicals (_including the ones that have already finished their 
segment loading_) do not get new segment load queue assignments until the last 
historical has finished loading the segments in its queue. 
   - The issue comes up when the segment load queues are so large on the 
pending historicals that the historicals that have completed their segment 
loading will have to wait for a considerably long time ( **T-t** ), before 
getting new segment load queues.
   
   In the following example, this time exceeded 2+ hours, even when there were 
more segments left to be decommissioned after the seen load queue had finished 
execution.
   
   Services tab:
   
![Services_tab](https://github.com/apache/druid/assets/35107623/4aef0acf-de6d-4a53-a64f-1590592ef6bd)
   
   decommission list:
   
![decomm_list](https://github.com/apache/druid/assets/35107623/15dc6456-5ffe-4963-867a-fde33225e9d8)
   
   Coordinator dynamic config:
   <img width="492" alt="coordinator_dynamic_config" 
src="https://github.com/apache/druid/assets/35107623/9af4ebfe-3ae7-4591-a821-9230e15c6914";>
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to