You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhiting Guo (Jira)" <ji...@apache.org> on 2023/07/18 08:03:00 UTC
[jira] [Assigned] (KYLIN-5652) Network anomalies or metabase anomalies cause Project Epoch to change frequently, which may cause the job in pending status for a long time and no longer to be executed
[ https://issues.apache.org/jira/browse/KYLIN-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhiting Guo reassigned KYLIN-5652:
----------------------------------
Assignee: Zhiting Guo
> Network anomalies or metabase anomalies cause Project Epoch to change frequently, which may cause the job in pending status for a long time and no longer to be executed
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-5652
> URL: https://issues.apache.org/jira/browse/KYLIN-5652
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: 5.0-alpha
> Reporter: Zhiting Guo
> Assignee: Zhiting Guo
> Priority: Major
> Fix For: 5.0-alpha
>
> Attachments: Network anomalies or metabase anomalies cause Project Epoch to change frequently, which may cause the job in pending status for a long time and no longer to be executed.pdf
>
>
> The scheduling of the project is not shut down during the shutdown period. At this time, the start operation is triggered. When starting, it is found that the scheduling is still in the start state in the if judgment, and it is returned.
> Then the shutdown operation ends, the task scheduling is turned off, and the task of the project has been in the pending state since then.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)