zhangyue19921010 edited a comment on pull request #10688: URL: https://github.com/apache/druid/pull/10688#issuecomment-749355475
Hi @kaijianding. This PR is just aiming to let druid regain the ability to check the availability of all segments and reload corrupted segments during historical restart which is broken by lazyOnStart. Is what you proposed that make druid have the ability to find and solve corrupted segments during runtime no matter lazyOnStart or not? It is actually a nice idea which can enhance the robustness of Druid and solve the corrupted segments problems once and for all. I will keep digging maybe make an another PR to make it happen if I understand right. What do you think? :) ---------------------------------------------------------------- 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
