[
https://issues.apache.org/jira/browse/HBASE-24446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134850#comment-17134850
]
Hudson commented on HBASE-24446:
--------------------------------
Results for branch master
[build #1756 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1756/]: (/)
*{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1756/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1663//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1756/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1756/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Use EnvironmentEdgeManager to compute clock skew in Master
> ----------------------------------------------------------
>
> Key: HBASE-24446
> URL: https://issues.apache.org/jira/browse/HBASE-24446
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Sandeep Guggilam
> Assignee: Sandeep Guggilam
> Priority: Minor
> Fix For: 3.0.0-alpha-1, 1.7.0, 2.4.0
>
>
> There are few cases where the Master is not able to complete the
> initialization as it waiting for the region server to report to it. The
> region server actually reported to the master but the master rejected the
> request because of clock skew issue though both of them are on same JVM
> The Region server uses EnvironmentEdgeManager.currentTime to report the
> current time and HMaster uses System.currentTimeMillis() to get the current
> time for computation against the reported time by RS. We should also just
> use EnvironmentEdgeManager even in Master as we are expected not to use
> System.currentTime directly and instead go through EnvironmentEdgeManager
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
