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

Vinayakumar B commented on HDFS-7849:
-------------------------------------

Thanks [~andreina] for the patch.
It would looks better if the clarification looks same as in description instead 
of another note.
I think following changes would do that.
{code}index 28649a8..aabf170 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/src/site/xdoc/HdfsRollingUpgrade.xml
+++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/xdoc/HdfsRollingUpgrade.xml
@@ -48,6 +48,15 @@
     In order to upgrade a HDFS cluster without downtime, the cluster must be 
setup with HA.
   </p>
   <p>
+    If there is new feature which is enabled in new software release may not 
work with old software release after upgrade.
+    In such cases upgrade should be done by following steps.
+  </p>
+  <ol>
+    <li>Disable new feature</li>
+    <li>upgrade the cluster</li>
+    <li>enable the new feature</li>
+  </ol>
+  <p>
     Note that rolling upgrade is supported only from Hadoop-2.4.0 onwards.
   </p>
   <subsection name="Upgrade without Downtime" id="UpgradeWithoutDowntime">
{code}

Agree?

> Update documentation for enabling a new feature in rolling upgrade
> ------------------------------------------------------------------
>
>                 Key: HDFS-7849
>                 URL: https://issues.apache.org/jira/browse/HDFS-7849
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: J.Andreina
>            Priority: Minor
>         Attachments: HDFS-7849.1.patch
>
>
> When there is a new feature in a new software, the new feature may not work 
> correctly with the old software.  In such case, rolling upgrade should be 
> done by the following steps:
> # disable the new feature,
> # upgrade the cluster, and
> # enable the new feature.
> We should clarify it in the documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to