a2l007 commented on pull request #10105: URL: https://github.com/apache/druid/pull/10105#issuecomment-652146731
@gianm Prior to that patch, coordinator could assign segments to historicals even if the balancer couldn't find a valid move for a segment. This means that even if `druid.server.maxSize` isn't optimally configured, the coordinator could still assign segments to it. However, with the patch the coordinator avoids segment assignment if it cannot find valid moves. This means that existing clusters configured with incorrect `druid.server.maxSize` property could see coordinators not assigning segments even though the historicals have enough capacity. So I feel the docs needs to emphasize the importance of this property a bit more given the behavioral change. ---------------------------------------------------------------- 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: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org
