[ 
https://issues.apache.org/jira/browse/HDFS-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887500#comment-13887500
 ] 

Tsz Wo (Nicholas), SZE commented on HDFS-5848:
----------------------------------------------

We also need block pool id in the response.  However, RollingUpgradeInfo may 
contain other information datanode does not need.  Let's add a new class, say 
RollingUpgradeStatus, for the response.  Then, RollingUpgradeInfo could extend 
it.

> Add rolling upgrade infomation to heartbeat response
> ----------------------------------------------------
>
>                 Key: HDFS-5848
>                 URL: https://issues.apache.org/jira/browse/HDFS-5848
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: h5848_20130130.patch, h5848_20130130b.patch
>
>
> When rolling upgrade is in progress, NN should inform datanodes via heartbeat 
> responses so that datanode should create hardlinks when deleting blocks.  We 
> only change heartbeat response here.  The datanode change will be done in a 
> separated JIRA.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to