capistrant commented on issue #12999: URL: https://github.com/apache/druid/issues/12999#issuecomment-1232114601
Upon reviewing the code further, I'm struggling to identify how we even get into a case where we need to reset because the counters match for both counter number and hash. @clintropolis You mention investigating those warning logs in your patch, #12209, do you remember if those full syncs were getting caused by this same counter reset due to the counter from the client being `>=` to the latest counter when the change future is being processed on the data server? -- 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]
