hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1261) Restart of the same data-node should not generate edits log records.
Date Mon, 16 Apr 2007 18:31:15 GMT

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

Raghu Angadi updated HADOOP-1261:
---------------------------------

    Attachment: HADOOP-1261-1.patch

We avoid writing the log entry when "nodeS == nodeN"  (i.e. node existed before and was serving
the same storage id ).

Konstantin, could you take a quick look at the patch?

> 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
>         Assigned To: Raghu Angadi
>            Priority: Minor
>             Fix For: 0.13.0
>
>         Attachments: HADOOP-1261-1.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