You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by "Jiale He (Jira)" <ji...@apache.org> on 2022/11/28 08:45:00 UTC
[jira] [Created] (KYLIN-5308) The old transaction is not interrupted when Epoch renew retry
Jiale He created KYLIN-5308:
-------------------------------
Summary: The old transaction is not interrupted when Epoch renew retry
Key: KYLIN-5308
URL: https://issues.apache.org/jira/browse/KYLIN-5308
Project: Kylin
Issue Type: Bug
Reporter: Jiale He
Attachments: image-2022-11-28-16-32-00-356.png
kylin fails to write data to the new transaction because the old transaction is not interrupted during the Renew Epoch Retry. As a result, Kylin loses the epoch.
When Epoch Renew occurs, the write to the database times out and tries again. As the old transaction is not rolled back during the retry, the old transaction is successfully written to the database and MVCC+1 occurs. When a new transaction writes to the database, it will check the MVCC. If the detection fails, kylin will think that the Epoch is lost.
!image-2022-11-28-16-32-00-356.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)