You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/01/24 01:45:59 UTC

[jira] Updated: (ZOOKEEPER-269) connectionloss - add more documentation to detail

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

Patrick Hunt updated ZOOKEEPER-269:
-----------------------------------

    Attachment: ZOOKEEPER-269.patch

Added doc details per the bug desc/comments. Kept things fairly high level - don't want to talk about api details in forrest, really need those in doxy/javadoc.


> connectionloss - add more documentation to detail 
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-269
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-269
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-269.patch
>
>
> discussion with user, this should be better documented:
> --------------
> There are basically 2 cases where you can see connectionloss:
> 1) you call an operation on a session that is no longer alive
> 2) you are disconnected from a server when there are pending async operations to that server (you made an async request which has not yet completed)
> Patrick
> Kevin Burton wrote:
> > Can this be thrown when using multiple servers as long as > 1 of them is
> > online?
> > Trying to figure out of I should try some type of reconnect if a single
> > machine fails instead of failing altogether.
> >
> > Kevin
> >

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.