API to disable segments for interval not working

From docs found here: https://druid.apache.org/docs/latest/tutorials/tutorial-delete-data.html

[karthik@localhost ~]$ curl -v -X ‘POST’ -H ‘Content-Type:application/json’ -d ‘{ “interval” : “2002-01-01T00:00:00.000Z/2004-12-31T00:00:00.000Z” }’ http://localhost:8081/druid/coordinator/v1/datasources/test/markUnused

  • About to connect() to localhost port 8081 (#0)

  • Trying ::1…

  • Connected to localhost (::1) port 8081 (#0)

POST /druid/coordinator/v1/datasources/ffs/markUnused HTTP/1.1

User-Agent: curl/7.29.0

Host: localhost:8081

Accept: /


Content-Length: 40

  • upload completely sent off: 40 out of 40 bytes

< HTTP/1.1 404 Not Found

< Date: Tue, 23 Jul 2019 05:24:16 GMT

< Content-Length: 0

< Server: Jetty(9.4.10.v20180503)


  • Connection #0 to host localhost left intact


I get a 404. Please help, this is kinda urgent. (have a workaround but we have a large dataset and cost is taking a hit)

Thats a new API thats added recently. See the below github issue


Please see the tutorial relevant to your version of druid. For e.g. for 0.14.0 please check the below link



As you could see above there is no markUnused API.

Hi Muthu,

Thanks… I was indeed should have been looking at 0.14.2. Apologies… However when I try delete on the below endpoint, I get a 200 response… But the segment is not disabled.



I verified the interval by specifying the below payload to “/druid/coordinator/v1/metadata/datasources/kar/segments” endpoint



However, if I hit the below API by specifying the segment id (I have only one segment in the above interval), it works like a charm.



Any idea what I am missing here?

Any help?

So just so that I understand. You are able to disable the segment using the coordinator delete API. However the question is why the below API is not working

  • /druid/coordinator/v1/datasources/{dataSourceName}/intervals/{interval}


Can you check your overlord logs to see if there are any errors / exception ?

I get a 200 response but I will still check.vi didn’t see any errors with info log level. I will change log level to debug and see if I see anything.

Btw, coordinator logs or overlord?

overlord logs. You should see that the task is looking for segment to disable.

Checked internally and it seems that API should mark segment as unsed but its trying to kill and since its used it fails. Seems to be an issue. Can you create a github issue for the same in the below link?