Apache Druid

task-log-coordinator-issued_kill_pmdata_kejdhffb_2022-09-13T04_00_00.000Z_2022-09-13T18_00_00.000Z_2022-09-14T03_12_36.229Z.log

[2022-09-13T04:00:00.000Z/2022-09-13T18:00:00.000Z] was revoked.","message":"Lock for interval [2022-09-13T04:00:00.000Z/2022-09-13T18:00:00.000Z] was revoked.
Are you running streaming ingestion/batch ingestion in that period on the data source ?

usually late date can come in streaming ingestion which creates older segments

is there any way forward to overcome this, it is piling up in deep storage and unused entries are not removed from the Postgres metadata store.

`druid.coordinator.kill.durationToRetain` is set to 60min. We can increase it so that the Kill tasks when started does not have the lock revoked because of late data arriving in your Kafka stream.

Another option is to set `lateMessageRejectionPeriod` in your Kafka stream which might drop the late data arriving. But this is not recommended as it will drop the events completely.

Also I think the Kill Tasks configs are too aggressive,
Whats the issue you are facing on the the postgress metadata store.

Please share your load rules as well.