sachidananda007 opened a new issue, #13540: URL: https://github.com/apache/druid/issues/13540
The Druid version where the problem was encountered. 0.22.1 In 0.19.0 , we saw this [issue](https://github.com/apache/druid/issues/13199) After upgrading to 0.22.1 I have a compaction task for few datasource which is failing with `"indexSpec is not ready: [spec]. Trying the next indexSpec."` I checked there is no lock present in mysql for this interval and it is fully available i.e. all segments are loaded after trying some changes in spec when i put this result is success `"forceTimeChunkLock": false` So I thought there is some lock present for this interval in zk. After getting inputs from open source slack channel from Mark Herrera , where it suggested gaps in data can cause this issue. https://apachedruidworkspace.slack.com/archives/C0303FDCZEZ/p1667922829090939 In our case my observations are following - I can see compaction tasks are failing for current running month(i.e. 2022-12-01 to 2023-01-01) we are doing day to day compaction ``` "granularitySpec": { "segmentGranularity": "DAY", "queryGranularity": null }, ``` - compaction tasks that has passed for this interval has continuous data segments for all days(i.e 31 segments) . - whichever has failed has gaps in data (i.e. there are less than 31 segments) but in `wikipedia datasource` i am not able to do reproduce this issue. Any help would be appreciated -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
