a2l007 commented on issue #11840: URL: https://github.com/apache/druid/issues/11840#issuecomment-952199446
Yeah I understand that disknormalized has its flaws but wanted to know if this specific issue is reproducible with that strategy as well. When the coordinator complains that there are no servers/node capacity for a segment, it usually means that: - Tier doesn't have any historicals in it or - The target historical is already serving the segment. (It would be worth checking the sys.server_segments table as well as the segment cache to see if `datasource_2020-05-07T17:00:00.000Z_2020-05-07T18:00:00.000Z_2020-05-07T17:00:00.025Z_104` is present for the frozen historical) - The historicals don't have enough space to hold the segment. From your logs, it could be the second case. Unfortunately, we don't have a lot of helpful debug logs around the balancer flow right now, which makes It harder to see what's going on. -- 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]
