8000
MAPREDUCE-6495. Docs for archive-logs tool (rkanter) (cherry picked from commit 0c4af0f) (cherry picked from commit 4921420) Conflicts: hadoop-mapreduce-project/CHANGES.txt hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/site/markdown/MapredCommands.md hadoop-project/src/site/site.xml Change-Id: I21393412890069f5e9e6b4d0aca5857b164465d7 (cherry picked from commit 1c280ef)
HADOOP-12017. Hadoop archives command should use configurable replica… …tion factor when closing (Contributed by Bibin A Chundatt) Conflicts: hadoop-common-project/hadoop-common/CHANGES.txt hadoop-tools/hadoop-archives/src/test/java/org/apache/hadoop/tools/TestHadoopArchives.java
HADOOP-12017. Hadoop archives command should use configurable replica… …tion factor when closing (Contributed by Bibin A Chundatt) Conflicts: hadoop-common-project/hadoop-common/CHANGES.txt hadoop-tools/hadoop-archives/src/test/java/org/apache/hadoop/tools/TestHadoopArchives.java
CLOUDERA-BUILD. Fix rolling upgrades from CDH5.3.x to CDH5.4.x. Chang… …es to 5.4.x. Reason: CDH5.3.x uses int for id in JVMId, while CDH5.4.x uses long. This incompatibility leads to job failures on rolling upgrade. Ref: CDH-28622 Commit details: - CDH5.4.3+ supports reading both int and long for is in JVMId. - CDH5.4.3+ uses 32-bit version of container-id when creating a JVMId. - Rolling upgrades within the 5.4.x line continue to work. - Among rolling upgrades from 5.3.x to 5.4.x, only 5.3.6 to 5.4.3+ work. Change-Id: Ic18d5553d8f6aebc179d0b6d003b3e1fead69998 (cherry picked from commit b8ccf9c)