[
https://issues.apache.org/jira/browse/PHOENIX-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117167#comment-17117167
]
Andrew Kyle Purtell commented on PHOENIX-4216:
----------------------------------------------
bq. 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.
This is a bug. There should be no direct calls to System.currentTimeMillis,
they should all go through EnvironmentEdgeManager.currentTime.
bq. Ideally, even the EnvironmentEdgeManager should give the same as
System.currenttimemillis() here unless we use some other delegate
That's probably what is happening
> Figure out why tests randomly fail with master not able to initialize in 200
> seconds
> ------------------------------------------------------------------------------------
>
> Key: PHOENIX-4216
> URL: https://issues.apache.org/jira/browse/PHOENIX-4216
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.15.0, 4.14.3
> Reporter: Samarth Jain
> Priority: Major
> Labels: phoenix-hardening, precommit, quality-improvement
> Fix For: 5.1.0, 4.16.0
>
> Attachments: Precommit-3849.log
>
>
> Sample failure:
> https://builds.apache.org/job/PreCommit-PHOENIX-Build/1450//testReport/
> [~apurtell] - Looking at the thread dump in the above link, do you see why
> master startup failed? I couldn't see any obvious deadlocks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
