accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3109) MonitorLoggingIT sometimes fails
Date Thu, 11 Sep 2014 14:29:34 GMT

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

Eric Newton commented on ACCUMULO-3109:
---------------------------------------

MonitorLogginIT has been failing intermittently for me, too.  Thanks for digging into this.

> MonitorLoggingIT sometimes fails
> --------------------------------
>
>                 Key: ACCUMULO-3109
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3109
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>             Fix For: 1.6.1, 1.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> MonitorLoggingIT contains to fail for me on different platforms. It ends up waiting for
the log message to show up until the test eventually times out.
> The code waits for the Monitor to be up, that it placed its location in ZooKeeper. However,
for log-forwarding to be active, any tserver running also has to get the watcher update for
the log4j-forwarding node that the monitor updates.
> My hunch is that we did the scan, caused the error, and then log4j forwarding was enabled.
Should be able to stabilize by waiting before we scan. To definitively know, we'd have to
add something to the RPC for tservers to query what their current log-forwarding "state" is
(which probably isn't worth the hassle).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message