[GitHub] [druid] capistrant commented on issue #12999: I don't think that ChangeRequestHistory should force a Counter reset if the Counter matches the latest Counter when waiting futures are resolved

[GitBox <gi...@apache.org>]

capistrant commented on issue #12999:
URL: https://github.com/apache/druid/issues/12999#issuecomment-1240859129

   I think #13010 is a safe way to solve this. There is some unnecessary no-op network traffic, but it should put a stop to wasteful counter resets


-- 
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-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org