[HBASE-24446] Use EnvironmentEdgeManager to compute clock skew in Master

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.6.0
• Fix Version/s: 3.0.0-alpha-1, 2.3.0, 1.7.0, 2.2.6
• Hadoop Flags: Reviewed
• Assignee: Sandeep Guggilam
• Reporter: Sandeep Guggilam
• Created: 27/May/20 16:29
• Updated: 23/Jun/20 22:40
• Resolved: 23/Jun/20 16:23

Description

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

 

Issue Links

• links to: GitHub Pull Request #1828
• links to: GitHub Pull Request #1835
• links to: GitHub Pull Request #1885
• links to: GitHub Pull Request #1886