leventov opened a new issue #7201: Coordinator documentation is stale URL: https://github.com/apache/incubator-druid/issues/7201 Coordinator documentation has the following paragraph: > Before any unassigned segments are serviced by historical nodes, the available historical nodes for each tier are first sorted in terms of capacity, with least capacity servers having the highest priority. Unassigned segments are always assigned to the nodes with least capacity to maintain a level of balance between nodes. The coordinator does not directly communicate with a historical node when assigning it a new segment; instead the coordinator creates some temporary information about the new segment under load queue path of the historical node. Once this request is seen, the historical node will load the segment and begin servicing it. As far as I can tell, both key pieces of information that are communicated in this paragraph are wrong: - "Unassigned segments are always assigned to the nodes with least capacity" - no, actually regular balancing rules are in play during loading. (see `DruidCoordinatorRuleRunner`). - "The coordinator does not directly communicate with a historical node when assigning it a new segment" - actually it does, if HTTP announcing (should we better call it "HTTP segment info communication"?) is used. Could somebody please verify my conclusions? Suggestions about how this paragraph should be rephrased are also welcome (or you could go ahead with a PR yourself). @clintropolis @egor-ryashin @gianm
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
