[ 
https://issues.apache.org/jira/browse/IMPALA-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17915962#comment-17915962
 ] 

ASF subversion and git services commented on IMPALA-13678:
----------------------------------------------------------

Commit c936f95af2b3efef685aee095e4ecfd550472f3c in impala's branch 
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=c936f95af ]

IMPALA-13678: Validate remote_submit_time against coordinator time

Impala with External frontend hit a DCHECK in
RuntimeProfile::EventSequence::Start(int64_t start_time_ns) because
frontend report remote_submit_time that is more than 3ns ahead of
Coordinator time. This can happen if there is a clock skew between
Frontend node and Impala Coordinator node.

This patch fix the issue by taking the minimum between given
remote_submit_time vs Coordinator's MonotonicStopWatch::Now().

Change-Id: If6e04219c515fddff07bfbee43bb93babb3d307b
Reviewed-on: http://gerrit.cloudera.org:8080/22360
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Validate remote_submit_time against coordinator time
> ----------------------------------------------------
>
>                 Key: IMPALA-13678
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13678
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 4.5.0
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Minor
>
> Impala with External frontend hit a DCHECK in 
> RuntimeProfile::EventSequence::Start(int64_t start_time_ns) because frontend 
> report remote_submit_time that is more than 3ns ahead of Coordinator time. 
> This can happen if there is a clock skew between Frontend node and Impala 
> Coordinator node.
> Impala Coordinator should validate remote_submit_time against its own clock.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to