But, current codebase in this repository don't use both PrestoQueueLengthRoutingTable and PrestoQueueLengthChecker. And besides, there is no option to activate those useful features without code modification.
I think, there is no reason to maintain HaRoutingManager as default, because PrestoQueueLengthRoutingTable is derived from it. So, it makes sense to activate PrestoQueueLengthRoutingTable and PrestoQueueLengthChecker by default.
Plus, I add minor logic to consider cluster with no worker as unhealthy.
There were valuable updates on routing logic with
PrestoQueueLengthRoutingTable
routing manager andPrestoQueueLengthChecker
observer, like below.But, current codebase in this repository don't use both
PrestoQueueLengthRoutingTable
andPrestoQueueLengthChecker
. And besides, there is no option to activate those useful features without code modification.I think, there is no reason to maintain
HaRoutingManager
as default, becausePrestoQueueLengthRoutingTable
is derived from it. So, it makes sense to activatePrestoQueueLengthRoutingTable
andPrestoQueueLengthChecker
by default.Plus, I add minor logic to consider cluster with no worker as unhealthy.