ivandika3 commented on PR #6772: URL: https://github.com/apache/ozone/pull/6772#issuecomment-2148909737
@ChenSammi Thanks for the review. > But this 10s seems too aggressive. 10s is too easy to timeout in a write heavy environment, with all three healthy DN, which makes most of write requests watch will fall back to MAJORITY_COMMITTED watch I see, we can increase it to higher value (e.g. 30s). Currently I don't think our cluster has encountered a situation where a single block write can last more than 10s. Could you help let me know what is a reasonable value based on the write-heavy workload? Thank you. -- 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]
