ChenSammi commented on PR #699:
URL: https://github.com/apache/ratis/pull/699#issuecomment-1204865305
IMHO, the current updateIncreasingly is less strict than updateToMax.
updateToMax will atomically check if the new value is greater than the old
value before update the index while updateIncreasingly doesn the check after
the value change in a way which has no atomic guarantee.
This async flush just put the flush aside, the number of flush is not
reduced. In a heavy workload cluster, every flush took up to seconds to
finish. My goal is first make it async, then reduce the actual flush count by
reverse order executing, flush tasks with high commitIndex got executed first.
--
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]
