You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Dionysios Logothetis (Jira)" <ji...@apache.org> on 2020/05/08 01:14:00 UTC
[jira] [Resolved] (GIRAPH-1205) Separate Giraph counters for
different causes of network request resends
[ https://issues.apache.org/jira/browse/GIRAPH-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dionysios Logothetis resolved GIRAPH-1205.
------------------------------------------
Resolution: Fixed
> Separate Giraph counters for different causes of network request resends
> ------------------------------------------------------------------------
>
> Key: GIRAPH-1205
> URL: https://issues.apache.org/jira/browse/GIRAPH-1205
> Project: Giraph
> Issue Type: Improvement
> Reporter: Atanu Ghosh
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In [https://issues.apache.org/jira/browse/GIRAPH-1200|https://l.facebook.com/l.php?u=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGIRAPH-1200&h=AT0QcRraYr63snHpZlSQ0PxkTc7wY3aucSzdquAnmVSBxVA5AsPAK5m3YEzR7CndOtcjRhHC0vJc8z1ZFmCnJCnH5vyyboH5_zu_pWfC_BxBji3f6JwogLv7xX4tIXQ166Tzise5MUcFYPkP6Jsj7VZV] we added counters for network requests resends, but "network resends for timeout" actually cover various reasons for why request can get resent. We suspect that resending requests after maxRequestMilliseconds timeout is what is always fatal, so separating this counter from the other causes will help us verify that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)