linehrr
We haven’t tested it against the newest Kafka version. But the old version 1.1 it is still happening.
when can we merge this? we are having this same problem in prod. just wondering when this can be merged and released ?
or you can use the docker image which has everything packed in and ready to go: https://hub.docker.com/r/kafkamanager/kafka-manager
exactly the same and also on the same version of druid: 0.22.1.
 it basically looks like this, and it's just stuck there forever. coordinator logs look fine. to me this looks like the segment compaction calculation/planning thread stuck.
``` 2022-11-10T18:51:32,702 ERROR [Coordinator-Exec--0] org.apache.druid.server.coordinator.DruidCoordinator - Caught exception, ignoring so that schedule keeps going.: {class=org.apache.druid.server.coordinator.DruidCoordinator, exceptionType=class java.lang.RuntimeException, exceptionMessage=org.apache.druid.java.util.common.ISE: Error while killing pendingSegments of dataSource[Forecasting_geo] created until [2022-11-09T18:10:12.359Z]} java.lang.RuntimeException: org.apache.druid.java.util.common.ISE: Error...
ok after we cleaned up the pendingsegment basically by removing the broken records in the table, coordinator is now functioning ok and scheduling the auto-compaction now. so I do think...
same issue encountered also in server version 1.3.0.
@imbajin ok I found the root cause and some workaround: root cause is that I called clearGraph() function in the code, so that I can clean up the graph and...
@erhhung added this plugin PR, this works for both pods and containers. https://github.com/derailed/k9s/pull/2002/files