You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "xujing (JIRA)" <ji...@apache.org> on 2018/03/27 02:46:00 UTC
[jira] [Commented] (KYLIN-3311) Segments overlap error (refactor
write conflict exception)
[ https://issues.apache.org/jira/browse/KYLIN-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414928#comment-16414928 ]
xujing commented on KYLIN-3311:
-------------------------------
Thanks for your answer .And I will continue to pay attention on this issue,because if the "segments overlap" occured will lead to some following questions:
1.new segment's status will be "NEW",but could not find corresponding Htable in Hbase
2.new segment could not be refresh or delete.
When this error happened I can only clone a new cube and build all history data or restore the metadata.I think these two ways are not good.Do you have some good suggestions? Thank you!
> Segments overlap error (refactor write conflict exception)
> ----------------------------------------------------------
>
> Key: KYLIN-3311
> URL: https://issues.apache.org/jira/browse/KYLIN-3311
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: v2.3.0
> Reporter: xujing
> Priority: Major
> Labels: build
> Attachments: Segments_Overlap_ErrorLog.txt
>
>
> when "updateCubeWithRetry" method be called at first time ,
> line newSegs.validate();was passed .
> then
> cube = crud.save(cube);seem with error throw exception
> write conflict to update cube xxxx at try 0 ,will retry...
> while retry "updateCubeWithRetry" start
> line newSegs.validate();was not passed .
> throw exception
> Segments overlap: xxxx[20180318000000_20180319000000] and sales_order_channel[20180318000000_201803
> 19000000]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)