ivandika3 opened a new pull request, #6772:
URL: https://github.com/apache/ozone/pull/6772

   ## What changes were proposed in this pull request?
   
   Reduce the default duration of Ratis server watch timeout 
hdds.ratis.raft.server.watch.timeout to reduce the amount of time client needs 
to wait during two-way commit (i.e. one DN is not reachable).
   
   The watch timeout configuration sets the upper bound of how long the watch 
request will wait, let's set to to 10s as a good starting point.
   
   See the related tickets for context.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-10972
   
   ## How was this patch tested?
   
   Existing CI (Thanks @smengcl for validating the CI earlier).
   
   Tested with ozone-ha docker-compose environment with one DN down (using 
"docker container pause")
   
   Without watch timeout configuration change -> client needs to wait for 3 
minutes (the default hdds.ratis.raft.server.watch.timeout configuration)
   
   ```
   time ozone sh key put /vol1/bucket1/key1 ~/LICENSE.txt --type RATIS -r THREE
   real 3m3.037s
   user 0m9.957s
   sys 0m1.106s 
   ```
   
   hdds.ratis.raft.server.watch.timeout=30s -> client needs to wait for around 
30s
   
   ```
   time ozone sh key put /vol1/bucket1/key1 ~/LICENSE.txt --type RATIS -r THREE
   real 0m33.897s
   user 0m9.990s
   sys 0m1.346s 
   ```
   
   hdds.ratis.raft.server.watch.timeout=10s -> client needs to wait for around 
10s
   
   ```
   time ozone sh key put /vol1/bucket1/key1 ~/LICENSE.txt --type RATIS -r THREE
   real 0m13.319s
   user 0m9.966s
   sys  0m1.102s
   ```
   
   
   


-- 
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]

Reply via email to