curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-71) Error message in StandardLockInternalsDriver for retryable lock acquire error
Date Mon, 04 Aug 2014 00:34:11 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084181#comment-14084181
] 

ASF GitHub Bot commented on CURATOR-71:
---------------------------------------

Github user cammckenzie commented on the pull request:

    https://github.com/apache/curator/pull/31#issuecomment-51008324
  
    Thanks, looks good. I just had a quick look through the code for any other cases, and
there are a couple in ConnectionStateListener. Lines 80 and 201. I think that at least the
one at line 80 should also be removed. The line 201 one can be suppressed via a property,
so maybe that one is not so important. What do you think?


> Error message in StandardLockInternalsDriver for retryable lock acquire error
> -----------------------------------------------------------------------------
>
>                 Key: CURATOR-71
>                 URL: https://issues.apache.org/jira/browse/CURATOR-71
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.1.0-incubating
>            Reporter: Vegard B. Havdal
>
> We occasionally get the error message "Sequential path not found..." from StandardLockInternalDriver,
but the subsequent NoNode exception is caught and treated as normal in some cases in LockInternals.
Ie. bogus error message in our log.
> Consider removing the error log msg from StandardLockInternalDriver, not log and throw.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message