zhangyue19921010 edited a comment on pull request #10688: URL: https://github.com/apache/druid/pull/10688#issuecomment-749372089
> @zhangyue19921010 I guess the exception from loadIndex can be a signal of corruption. When you distinguish the corruption exception, it is safe to unload this segment and let the coordinator choose another historical to load(usually, you have replicas). Compare to restart behavior, I think the unloading behavior is more efficient and no human involvement is needed. Also there is no exception in `loadIndex` because of lazy action, and historical will restart successfully. what I am trying to do is that do segments file check and throws IOException in `loadIndex` :) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org