From e0febce0e74ec69597376774f771da46834c42b1 Mon Sep 17 00:00:00 2001 From: Vinayakumar B Date: Tue, 7 Jul 2015 18:13:35 +0530 Subject: [PATCH] HADOOP-12186. ActiveStandbyElector shouldn't call monitorLockNodeAsync multiple times (Contributed by zhihai xu) Moved CHANGES.txt entry to 2.7.2 --- hadoop-common-project/hadoop-common/CHANGES.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/hadoop-common-project/hadoop-common/CHANGES.txt b/hadoop-common-project/hadoop-common/CHANGES.txt index 5d11db9c82b..ee96eee26be 100644 --- a/hadoop-common-project/hadoop-common/CHANGES.txt +++ b/hadoop-common-project/hadoop-common/CHANGES.txt @@ -930,9 +930,6 @@ Release 2.8.0 - UNRELEASED HADOOP-12164. Fix TestMove and TestFsShellReturnCode failed to get command name using reflection. (Lei (Eddy) Xu) - HADOOP-12186. ActiveStandbyElector shouldn't call monitorLockNodeAsync - multiple times (zhihai xu via vinayakumarb) - HADOOP-12117. Potential NPE from Configuration#loadProperty with allowNullValueProperties set. (zhihai xu via vinayakumarb) @@ -948,6 +945,9 @@ Release 2.7.2 - UNRELEASED BUG FIXES + HADOOP-12186. ActiveStandbyElector shouldn't call monitorLockNodeAsync + multiple times (zhihai xu via vinayakumarb) + Release 2.7.1 - 2015-07-06 INCOMPATIBLE CHANGES