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

Yuzhang QIU commented on KYLIN-3562:
------------------------------------

Hi jiatao Tao:
  I meet this exception too, so what operation will make 
`!userService.loadUserByUsername(username).equals(user)` then update user 
during query through JDBC?
 And ManagerUser compare every field in it to judge equality, it's necessary?
  If you find any mistake or misunderstanding, please feel free to correct me.

Best regards
yuzhang

> 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)

Reply via email to