<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi all,
<div class=""><br class="">
</div>
<div class="">We have a 4 node distributed/replicated setup (2 x 2) with gluster version 3.6.4.</div>
<div class=""><br class="">
</div>
<div class="">Yesterday one node went down due to a power failure, as expected everything kept working well. But after we brought up the failed node again gluster started, also as expected, its self-healing process. The moment that happens all our client connections
to the gluster cluster start freezing one by one till the moment the healing process finishes.</div>
<div class=""><br class="">
</div>
<div class="">After some research we found this page <a href="http://www.gluster.org/community/documentation/index.php/Documenting_the_undocumented" class="">http://www.gluster.org/community/documentation/index.php/Documenting_the_undocumented</a> with some
possible performance options to tweak, performance.least-prio-threads and performance.least-rate-limit. Does anybody has experience with tweaking these options? What are there default settings? Are these the right options to tweak or do we needs another approach
regarding our problem?</div>
<div class=""><br class="">
</div>
<div class="">Thanks in advance.</div>
<div class=""><br class="">
</div>
<div class="">Kind regards</div>
<div class="">Davy</div>
<div class=""> </div>
</body>
</html>