kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yichen Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (KYLIN-3562) TS conflict when kylin update metadata in HBase
Date Mon, 17 Sep 2018 03:44:00 GMT

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

Yichen Zhou edited comment on KYLIN-3562 at 9/17/18 3:43 AM:
-------------------------------------------------------------

[~chitin], I am working on KYLIN-3531 and maybe they have the same root cause. 

I‘ll let you know if there is any progress.


was (Author: yichen.zhou):
[~chitin], I am working on KYLIN-3531 and maybe they have the same root cause. 

Please refer to this: https://issues.apache.org/jira/browse/KYLIN-3531

I‘ll let you know if there is any progress.

> TS conflict when kylin update metadata in HBase
> -----------------------------------------------
>
>                 Key: KYLIN-3562
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3562
>             Project: Kylin
>          Issue Type: Bug
>    Affects Versions: v2.4.0
>            Reporter: Lingang Deng
>            Priority: Major
>
> Error log was as follows,
> {code:java}
> org.apache.kylin.common.persistence.WriteConflictException: Overwriting conflict /user/admin,
expect old TS 1536928877043, but it is 1536928907207
>          at org.apache.kylin.storage.hbase.HBaseResourceStore.checkAndPutResourceImpl(HBaseResourceStore.java:325)
>          at org.apache.kylin.common.persistence.ResourceStore.checkAndPutResourceCheckpoint(ResourceStore.java:318)
>          at org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:303)
>          at org.apache.kylin.common.persistence.ResourceStore.putResource(ResourceStore.java:282)
>          at org.apache.kylin.metadata.cachesync.CachedCrudAssist.save(CachedCrudAssist.java:192){code}
>  
> what disturbs me the most was that the error was happened several hours,  then my all
build job and query job failed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message