hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Chansler (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-3631) Transfer of image from secondary name node should not interrupt service
Date Tue, 24 Jun 2008 19:44:44 GMT
Transfer of image from secondary name node should not interrupt service
-----------------------------------------------------------------------

                 Key: HADOOP-3631
                 URL: https://issues.apache.org/jira/browse/HADOOP-3631
             Project: Hadoop Core
          Issue Type: Improvement
          Components: dfs
    Affects Versions: 0.17.0
            Reporter: Robert Chansler
            Priority: Critical
             Fix For: 0.19.0


The transfer of the new image prepared by the secondary name node can interfere with client
services. Clients observe delays in completing RPCs. In general, administrative activities
should not be observed by the clients. For large clusters, administrators are reluctant to
run the secondary name node leading to excessive edit logs. (Excessive in the sense that if
the cluster must be restarted, a long time is required to process the log.)

Maybe the new image does not have to be transfered; it could be fetched when needed.

Maybe the priority of the transfer task can be reduced so that the transfer is not observed.

Maybe a different transfer protocol is more appropriate.


-- 
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