You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2006/06/29 08:28:29 UTC

[jira] Created: (HADOOP-332) Implement remote replication of dfs namespace images and transaction logs

Implement remote replication of dfs namespace images and transaction logs
-------------------------------------------------------------------------

         Key: HADOOP-332
         URL: http://issues.apache.org/jira/browse/HADOOP-332
     Project: Hadoop
        Type: Improvement

  Components: dfs  
    Versions: 0.4.0    
    Reporter: Owen O'Malley
 Assigned to: Owen O'Malley 
     Fix For: 0.5.0


The namespace information (image and transaction logs) needs to be replicated on hosts other than the namenode to prevent data loss if a namenode crashes. In the short term we will add a new protocol to the datanodes to receive and store the namespace information.

In the long term, it would be nice to have read-only namenodes that could receive the information and serve it up for users that want to read data, but do not need to write to the namespace.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (HADOOP-332) Implement remote replication of dfs namespace images and transaction logs

Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-332?page=all ]

Sameer Paranjpye resolved HADOOP-332.
-------------------------------------

    Resolution: Duplicate

Duplicate of HADOOP-90

> Implement remote replication of dfs namespace images and transaction logs
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-332
>                 URL: http://issues.apache.org/jira/browse/HADOOP-332
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.4.0
>            Reporter: Owen O'Malley
>         Assigned To: Konstantin Shvachko
>
> The namespace information (image and transaction logs) needs to be replicated on hosts other than the namenode to prevent data loss if a namenode crashes. In the short term we will add a new protocol to the datanodes to receive and store the namespace information.
> In the long term, it would be nice to have read-only namenodes that could receive the information and serve it up for users that want to read data, but do not need to write to the namespace.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Assigned: (HADOOP-332) Implement remote replication of dfs namespace images and transaction logs

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/HADOOP-332?page=all ]

Owen O'Malley reassigned HADOOP-332:
------------------------------------

    Assignee: Konstantin Shvachko  (was: Owen O'Malley)

> Implement remote replication of dfs namespace images and transaction logs
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-332
>                 URL: http://issues.apache.org/jira/browse/HADOOP-332
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.4.0
>            Reporter: Owen O'Malley
>         Assigned To: Konstantin Shvachko
>             Fix For: 0.5.0
>
>
> The namespace information (image and transaction logs) needs to be replicated on hosts other than the namenode to prevent data loss if a namenode crashes. In the short term we will add a new protocol to the datanodes to receive and store the namespace information.
> In the long term, it would be nice to have read-only namenodes that could receive the information and serve it up for users that want to read data, but do not need to write to the namespace.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (HADOOP-332) Implement remote replication of dfs namespace images and transaction logs

Posted by "Milind Bhandarkar (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/HADOOP-332?page=comments#action_12451455 ] 
            
Milind Bhandarkar commented on HADOOP-332:
------------------------------------------

should this issue be closed now that we have a patch committed for HADOOP-90 ?

> Implement remote replication of dfs namespace images and transaction logs
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-332
>                 URL: http://issues.apache.org/jira/browse/HADOOP-332
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.4.0
>            Reporter: Owen O'Malley
>         Assigned To: Konstantin Shvachko
>
> The namespace information (image and transaction logs) needs to be replicated on hosts other than the namenode to prevent data loss if a namenode crashes. In the short term we will add a new protocol to the datanodes to receive and store the namespace information.
> In the long term, it would be nice to have read-only namenodes that could receive the information and serve it up for users that want to read data, but do not need to write to the namespace.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira