HDFS-8226. Non-HA rollback compatibility broken (Contributed by J.Andreina)
(cherry picked from commite01c1a979c
) Conflicts: hadoop-hdfs-project/hadoop-hdfs/src/main/bin/start-dfs.sh hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsUserGuide.md (cherry picked from commit3a894b4563
)
This commit is contained in:
parent
ada2f74b17
commit
99309a9fec
|
@ -68,6 +68,8 @@ Release 2.7.1 - UNRELEASED
|
|||
HDFS-7980. Incremental BlockReport will dramatically slow down namenode
|
||||
startup. (Walter Su via szetszwo)
|
||||
|
||||
HDFS-8226. Non-HA rollback compatibility broken (J.Andreina via vinayakumarb)
|
||||
|
||||
Release 2.7.0 - 2015-04-20
|
||||
|
||||
INCOMPATIBLE CHANGES
|
||||
|
|
|
@ -30,20 +30,20 @@ HADOOP_LIBEXEC_DIR=${HADOOP_LIBEXEC_DIR:-$DEFAULT_LIBEXEC_DIR}
|
|||
. $HADOOP_LIBEXEC_DIR/hdfs-config.sh
|
||||
|
||||
# get arguments
|
||||
if [ $# -ge 1 ]; then
|
||||
nameStartOpt="$1"
|
||||
shift
|
||||
case "$nameStartOpt" in
|
||||
(-upgrade)
|
||||
;;
|
||||
(-rollback)
|
||||
dataStartOpt="$nameStartOpt"
|
||||
;;
|
||||
(*)
|
||||
echo $usage
|
||||
exit 1
|
||||
;;
|
||||
esac
|
||||
if [[ $# -ge 1 ]]; then
|
||||
startOpt="$1"
|
||||
shift
|
||||
case "$startOpt" in
|
||||
-upgrade)
|
||||
nameStartOpt="$startOpt"
|
||||
;;
|
||||
-rollback)
|
||||
dataStartOpt="$startOpt"
|
||||
;;
|
||||
*)
|
||||
hadoop_exit_with_usage 1
|
||||
;;
|
||||
esac
|
||||
fi
|
||||
|
||||
#Add other possible options
|
||||
|
|
|
@ -319,7 +319,9 @@ When Hadoop is upgraded on an existing cluster, as with any software upgrade, it
|
|||
|
||||
* stop the cluster and distribute earlier version of Hadoop.
|
||||
|
||||
* start the cluster with rollback option. (`bin/start-dfs.sh -rollback`).
|
||||
* run the rollback command on the namenode (`bin/hdfs namenode -rollback`).
|
||||
|
||||
* start the cluster with rollback option. (`sbin/start-dfs.sh -rollback`).
|
||||
|
||||
When upgrading to a new version of HDFS, it is necessary to rename or delete any paths that are reserved in the new version of HDFS. If the NameNode encounters a reserved path during upgrade, it will print an error like the following:
|
||||
|
||||
|
|
Loading…
Reference in New Issue