mcvsubbu opened a new issue, #10973: URL: https://github.com/apache/pinot/issues/10973
This is a race condition that we have observed during the following sequence of events. - Minion purge task downloads a segment and purges some records - The task tries to upload the segment back to the controller via controller API - The controller happens to field a restart while moving the file to deepstore (we use LocalFS, but this may happen in other FS as well, not sure). In this case, it is possible that the deep store does not have a copy of the segment, but the segment exists in idealstate, and the segment metadata exists as well. We have not worked out the details of the exact sub-steps during the upload process that lets the segment reach this state. It could be because LocalFS first deletes the segment in deep store, and then copies the new segment from local file over to deep store, and the restart happens between these two operations. Also, not sure if minion retries the push, but even if it does so, it probably fails because the segment is in inconsistent state (or because concurrent push is enabled). We will be digging more into this, and proposing fixes. -- 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: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
