You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2012/07/16 20:54:35 UTC

[jira] [Updated] (HDFS-3625) Fix TestBackupNode by properly initializing edit log

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

Todd Lipcon updated HDFS-3625:
------------------------------

    Summary: Fix TestBackupNode by properly initializing edit log  (was: FSN#startActiveServices assumes standby services started )

Renaming JIRA to be more specific that this is about the backupnode case.
                
> Fix TestBackupNode by properly initializing edit log
> ----------------------------------------------------
>
>                 Key: HDFS-3625
>                 URL: https://issues.apache.org/jira/browse/HDFS-3625
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Todd Lipcon
>            Priority: Blocker
>         Attachments: HDFS-3625.patch, HDFS-3625.patch
>
>
> TestBackupNode#testCheckpointNode fails because the following code in FSN#startActiveServices NPEs (resulting in a System.exit) because editLogTailer is set when starting standby services and if ha is not enabled we go directly to the active state. Looks like it should be wrapped with an haEnabled check.
> {code}
> LOG.info("Catching up to latest edits from old active before " +
>    "taking over writer role in edits logs.");
> editLogTailer.catchupDuringFailover();
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira