[
https://issues.apache.org/jira/browse/KYLIN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814524#comment-16814524
]
Iñigo Martinez commented on KYLIN-3562:
---------------------------------------
For now, only once. But we upgraded to 2.6.1 from 2.4.1 yesterday and we also
added the second kylin node after upgrade to 2.6.1.
So, at this moment, once a day.
In order to avoid major problems, we have split users. So, we have created
another admin for certain critics API operations and also another analyst user
for querying. Both are users for specific applications. So, just in case this
happen again, it won't have effect on online web reports that we have published
in our intranet.
This problem affected only to admin user.
> 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
> Assignee: Jiatao Tao
> Priority: Major
> Fix For: v2.4.2, v2.5.1
>
> Attachments: image-2018-09-17-16-40-56-212.png,
> image-2018-09-25-15-03-51-009.png, image-2018-09-25-16-43-50-277.png
>
>
> 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)