You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2025/01/22 16:33:00 UTC

[jira] [Resolved] (IMPALA-13678) Validate remote_submit_time against coordinator time

     [ https://issues.apache.org/jira/browse/IMPALA-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Riza Suminto resolved IMPALA-13678.
-----------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> 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
>             Fix For: Impala 4.5.0
>
>
> 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: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org