You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying out the middlemanager-less configuration (k8s-jobs) WITH zookeeper (without zookeeper seems to not work reliably).
However when deploying my configuration in the most easy config possible (using overlordSingleContainer as template), it seems to add the original startup probe (no readiness or liveness probe though) with port 8088.
It also seems that i can not change that peon port to 8088, so that the pod would eventually become healthy.
With this in mind, I do wonder how this has ever worked for anyone.
EDIT: I have found that here, the readiness and liveness probes are removed:
The startup probe remains though. Maybe having them removed would already make the overlord templates work for me.
When trying the customTemplateAdapter suddenly my coordinator (asOverlord) can not do leader election anymore, switching only the druid.indexer.runner.k8s.adapter.type property back to overlordSingleContainer will make its leader election work again (though with the before mentioned remaining issue).
Error: listener becomeLeader() failed. Unable to become leader: {exceptionType=java.lang.RuntimeException, exceptionMessage=java.lang.reflect.InvocationTargetException, class=org.apache.druid.curator.discovery.CuratorDruidLeaderSelector}
And: TaskMaster set a new Lifecycle without the old one being cleared! Race condition: {class=org.apache.druid.indexing.overlord.DruidOverlord}
Please include as much detailed information about the problem as possible.
Cluster size: 3 coordinator, 3 broker, 3 router, 1 historical, + 3 zookeeper
Druid resource (without historical, as i've got it separated):
Affected Version
v32.0.0
Description
I am trying out the middlemanager-less configuration (k8s-jobs) WITH zookeeper (without zookeeper seems to not work reliably).
However when deploying my configuration in the most easy config possible (using overlordSingleContainer as template), it seems to add the original startup probe (no readiness or liveness probe though) with port 8088.
It also seems that i can not change that peon port to 8088, so that the pod would eventually become healthy.
With this in mind, I do wonder how this has ever worked for anyone.
EDIT: I have found that here, the readiness and liveness probes are removed:
druid/extensions-contrib/kubernetes-overlord-extensions/src/main/java/org/apache/druid/k8s/overlord/taskadapter/K8sTaskAdapter.java
Line 312 in 5ef94c9
The startup probe remains though. Maybe having them removed would already make the overlord templates work for me.
When trying the customTemplateAdapter suddenly my coordinator (asOverlord) can not do leader election anymore, switching only the
druid.indexer.runner.k8s.adapter.type
property back tooverlordSingleContainer
will make its leader election work again (though with the before mentioned remaining issue).Error:
listener becomeLeader() failed. Unable to become leader: {exceptionType=java.lang.RuntimeException, exceptionMessage=java.lang.reflect.InvocationTargetException, class=org.apache.druid.curator.discovery.CuratorDruidLeaderSelector}
And:
TaskMaster set a new Lifecycle without the old one being cleared! Race condition: {class=org.apache.druid.indexing.overlord.DruidOverlord}
Ideally I want to be able to use different pod templates in the end, like mentioned here: https://druid.apache.org/docs/32.0.0/development/extensions-contrib/k8s-jobs/
Either with or without zookeeper (though without would be preferred).
Please include as much detailed information about the problem as possible.
Cluster size: 3 coordinator, 3 broker, 3 router, 1 historical, + 3 zookeeper
Druid resource (without historical, as i've got it separated):
pod-templates configmap:
The text was updated successfully, but these errors were encountered: