pdeva opened a new issue #10215:
URL: https://github.com/apache/druid/issues/10215


   Please provide a detailed title (e.g. "Broker crashes when using TopN query 
with Bound filter" instead of just "Broker crashes").
   
   ### Affected Version
   
   0.18.1
   
   ### Description
   Indexer nodes had stopped ingesting data. So we restarted them and now we 
see this exception
   
   ```
   o.a.d.i.w.WorkerTaskManager [WorkerTaskManager-CompletedTasksCleaner] 
Exception while getting active tasks from overlord. will retry on next 
scheduled run.
   
   java.lang.IllegalStateException: null
        at 
com.google.common.base.Preconditions.checkState(Preconditions.java:161) 
~[guava-16.0.1.jar:?]
        at 
org.apache.druid.discovery.DruidLeaderClient.makeRequest(DruidLeaderClient.java:131)
 ~[druid-server-0.18.0-iap6.jar:0.18.0-iap6]
        at 
org.apache.druid.discovery.DruidLeaderClient.makeRequest(DruidLeaderClient.java:140)
 ~[druid-server-0.18.0-iap6.jar:0.18.0-iap6]
        at 
org.apache.druid.indexing.worker.WorkerTaskManager.lambda$scheduleCompletedTasksCleanup$4(WorkerTaskManager.java:509)
 ~[druid-indexing-service-0.18.0-iap6.jar:0.18.0-iap6]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[?:1.8.0_252]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[?:1.8.0_252]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [?:1.8.0_252]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [?:1.8.0_252]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_252]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_252]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
   ```


----------------------------------------------------------------
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:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to