You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@giraph.apache.org by "Avery Ching (JIRA)" <ji...@apache.org> on 2012/10/20 02:22:11 UTC

[jira] [Updated] (GIRAPH-382) ZooKeeperExt should handle ConnectionLossException by retrying

     [ https://issues.apache.org/jira/browse/GIRAPH-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Avery Ching updated GIRAPH-382:
-------------------------------

    Attachment: GIRAPH-382.patch

Here is the fix, passed unittests.  More details on reviewboard.

https://reviews.apache.org/r/7674/
                
> ZooKeeperExt should handle ConnectionLossException by retrying
> --------------------------------------------------------------
>
>                 Key: GIRAPH-382
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-382
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>         Attachments: GIRAPH-382.patch
>
>
> Sometimes we get a connection loss to ZooKeeper.  The client will automatically retry, but we shouldn't die in the meantime due to the connection loss exception.  This patch ensures that all ZooKeeperExt operations catch the connection loss exception, sleep (default 5 seconds), and retry (default 3).  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira