[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=16424969#comment-16424969 ] ASF subversion and git services commented on KYLIN-3311: Commit a6bfc9d019b7df4d96d46db2b8e010323fe4fddf in kylin's branch refs/heads/master from Li Yang [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=a6bfc9d ] KYLIN-3311 refactor Resource.checkAndPutResourceImpl() to throw WriteConflictException > 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 at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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=16423568#comment-16423568 ] ASF subversion and git services commented on KYLIN-3311: Commit 3222de27c508ed3e7576330dc8c40206fe6cd84d in kylin's branch refs/heads/sync from Li Yang [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=3222de2 ] KYLIN-3311 refactor Resource.checkAndPutResourceImpl() to throw WriteConflictException > 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 at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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=16423557#comment-16423557 ] ASF subversion and git services commented on KYLIN-3311: Commit e465a51fab70da301571511adf4ebfb358026aea in kylin's branch refs/heads/sync from Li Yang [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=e465a51 ] KYLIN-3311 refactor Resource.checkAndPutResourceImpl() to throw WriteConflictException > 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 at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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=16423411#comment-16423411 ] ASF subversion and git services commented on KYLIN-3311: Commit 3222de27c508ed3e7576330dc8c40206fe6cd84d in kylin's branch refs/heads/sync from Li Yang [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=3222de2 ] KYLIN-3311 refactor Resource.checkAndPutResourceImpl() to throw WriteConflictException > 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 at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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=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 at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3311) Segments overlap error
[ https://issues.apache.org/jira/browse/KYLIN-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412880#comment-16412880 ] liyang commented on KYLIN-3311: --- Thanks for reporting. I'm not sure of the root cause yet. It seems the first update was actually successfully, but however an IllegalStateException was thrown after that, caused a retry, and caused the same segment being added twice. I guess we need to enhance the code to produce more logs first. Then if the problem re-occurs, we can hunt down the root cause. > Segments overlap error > -- > > 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 at try 0 ,will retry... > while retry "updateCubeWithRetry" start > line newSegs.validate();was not passed . > throw exception > Segments overlap: [2018031800_2018031900] and > sales_order_channel[2018031800_201803 > 1900] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
