zhangyue19921010 commented on pull request #10688: URL: https://github.com/apache/druid/pull/10688#issuecomment-754392524
Hi @kaijianding , sorry for late response. I just change the strategy for lazyOnStart action as you suggested. I build a new CallBack action `() -> this.removeSegment(segment, DataSegmentChangeCallback.NOOP, false)`. When query failed caused by lazyOnStart, this action will unload this segment and let the coordinator choose another historical to load. And I have tested it on dev cluster and works fine. Could you please help review the code? Thanks. ---------------------------------------------------------------- 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
