<div dir="ltr">Thanks for the details</div><div class="gmail_extra"><br><div class="gmail_quote">2016-10-26 15:01 GMT+02:00 John Sanda <span dir="ltr"><<a href="mailto:jsanda@redhat.com" target="_blank">jsanda@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span class=""><br><div><blockquote type="cite"><div>On Oct 26, 2016, at 6:14 AM, Thomas Segismont <<a href="mailto:tsegismo@redhat.com" target="_blank">tsegismo@redhat.com</a>> wrote:</div><br class="m_-7791419043147738441Apple-interchange-newline"><div><div dir="ltr">Congrats to the team!<div><br></div><div>With respect to <a href="https://issues.jboss.org/browse/HWKMETRICS-510" style="font-size:12.8px" target="_blank">HWKMETRICS-510</a>, how do you make sure that the server is not overwhelmed with retries stored in memory? Is the client response sent after the retry?</div></div></div></blockquote><div><br></div></div></span>The number of retries and the delay between retries is configurable. It defaults to 5 retries with a max delay of 30 seconds. The response won’t be sent until after the retries. We need to figure out how best to handle scenarios in which the server gets overwhelmed. It is not addressed in HWKMETRICS-510.</div><br>______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/hawkular-dev</a><br>
<br></blockquote></div><br></div>