<div dir="ltr">This is no longer happening.<br><div><br>I started to prep for the downtime this morning and in the process realized I didn't actually need such a large downtime. I brought down the server for 2 minutes at 8 am this morning and got the data out.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 23, 2016 at 11:37 AM, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>I was trying to clone gluster this morning and noticed that it was awfully slow and then completely stopped responding. I've restarted gerrit and it seems to work much better.<br><br></div>This has proven that my monitoring of gerrit works though, so we can, in the future, know of these outages before someone reports them.<br><br></div>For future reference<br>1) A HTTP call to the gerrit API will fail if gerrit is unhappy.<br></div>2) We're limited by CPU rather than RAM when gerrit doesn't respond. This may help us debug what we're doing wrong with our setup.<span class="HOEnZb"><font color="#888888"><br clear="all"><div><div><div><div><div><br>-- <br><div><div dir="ltr">nigelb<br></div></div>
</div></div></div></div></div></font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div>