This message was deleted.

You could try changing the replica count for just that one time chunk to see if it cleans it up ...

It does seem strange that if the historical server encounters an issue when trying to publish the segment then the coordinator is not informed of this… perhaps the coordinator should not mark the segment as ‘available’ until the historical confirms a successful load of the segment?

Litttle work to find out where the datasource is distributed , but if u can remove it from segment-cache then it will be forced to load form deep storage