@Karan Kumar There was no lock on the time interval. I confirmed that. If there was a lock, then it would go into "WAITING" state for the lock to be released, correct?
Just to be sure, I tried running the same REPLACE INTO OVERWRITE query from the console into a new Druid table. Same result, the query controller goes into RUNNING state and just waits. It doesn't launch any workers or tasks.
@Laksh Singla I checked the log file of the controller. There were no exceptions in it. It didn't seem to be any resource related issue since it continued in "RUNNING" state for several hours and shut down promptly when I "killed" it manually from the console - no errors in the log file. There was no resource issue on the host as other tasks were running fine on it. I will see if I can get the jstack of the query controller.
Thanks,
AR.