hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1261) Restart of the same data-node should not generate edits log records.
Date Thu, 31 May 2007 01:51:15 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500269
] 

Hadoop QA commented on HADOOP-1261:
-----------------------------------

+1

http://issues.apache.org/jira/secure/attachment/12358585/HADOOP-1261-2.patch applied and successfully
tested against trunk revision r542595.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/220/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/220/console

> Restart of the same data-node should not generate edits log records.
> --------------------------------------------------------------------
>
>                 Key: HADOOP-1261
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1261
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.12.0
>            Reporter: Konstantin Shvachko
>            Assignee: Raghu Angadi
>            Priority: Minor
>             Fix For: 0.14.0
>
>         Attachments: HADOOP-1261-1.patch, HADOOP-1261-2.patch
>
>
> Currently during registration of a data-node with the storage id that has already been
registered
> the name-node logs 2 records: <add node1> <remove node2>.
> If the same node has been restarted these two records are redundant, lead to unnecessary
> increase of the edits file and result in a slow-down of the name-node startup.

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


Mime
View raw message