You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/12/13 10:26:00 UTC
[jira] [Commented] (KYLIN-5308) The old transaction is not interrupted when Epoch renew retry
[ https://issues.apache.org/jira/browse/KYLIN-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646553#comment-17646553 ]
ASF subversion and git services commented on KYLIN-5308:
--------------------------------------------------------
Commit 9ac00fad6c50068c3695ee4cacb39bc3d11f5bc0 in kylin's branch refs/heads/kylin5 from Jiale He
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=9ac00fad6c ]
KYLIN-5308 Add transaction timeout when epoch renew
> 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
> Assignee: Jiale He
> Priority: Critical
> Fix For: 5.0-alpha
>
> Attachments: KYLIN-5308 Epoch Renew 事务超时 Design.pdf, image-2022-11-28-16-32-00-356.png, image-2022-11-29-14-29-31-681.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!
>
> See attachment for RC and Fix Design: `KYLIN-5308 Epoch Renew 事务超时 Design.pdf`
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)