[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-20024: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Hurray. It dropped from the flakey charts! > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-20024.branch-2.001.patch, > hbase-20024.master.001.patch, hbase-20024.master.002.patch, > hbase-20024.master.003.patch, hbase-20024.master.004.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-20024: - Attachment: hbase-20024.master.004.patch > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-20024.branch-2.001.patch, > hbase-20024.master.001.patch, hbase-20024.master.002.patch, > hbase-20024.master.003.patch, hbase-20024.master.004.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-20024: -- Fix Version/s: 2.0.0 > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-20024.branch-2.001.patch, > hbase-20024.master.001.patch, hbase-20024.master.002.patch, > hbase-20024.master.003.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-20024: -- Issue Type: Bug (was: Sub-task) Parent: (was: HBASE-19147) > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-20024.branch-2.001.patch, > hbase-20024.master.001.patch, hbase-20024.master.002.patch, > hbase-20024.master.003.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-20024: - Attachment: hbase-20024.master.003.patch > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: Umesh Agashe >Priority: Major > Attachments: HBASE-20024.branch-2.001.patch, > hbase-20024.master.001.patch, hbase-20024.master.002.patch, > hbase-20024.master.003.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-20024: - Attachment: hbase-20024.master.002.patch > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: Umesh Agashe >Priority: Major > Attachments: HBASE-20024.branch-2.001.patch, > hbase-20024.master.001.patch, hbase-20024.master.002.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-20024: - Attachment: hbase-20024.master.001.patch > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: Umesh Agashe >Priority: Major > Attachments: HBASE-20024.branch-2.001.patch, > hbase-20024.master.001.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-20024: -- Assignee: stack Status: Patch Available (was: Open) > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Major > Attachments: HBASE-20024.branch-2.001.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
[ https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-20024: -- Attachment: HBASE-20024.branch-2.001.patch > TestMergeTableRegionsProcedure is STILL flakey > -- > > Key: HBASE-20024 > URL: https://issues.apache.org/jira/browse/HBASE-20024 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Priority: Major > Attachments: HBASE-20024.branch-2.001.patch > > > This is a follow-on from HBASE-20015. Root issue is that merge does not > support rollback once it has hit the point-of-no-return; it can only > roll-forward at this point. > HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort > to the truncate procedure to get around flakeyness. HBASE-20022 is a new > issue to figure what to do w/ unabortable procedures. > Meantime, merge and split have PONR and the procedure executor test harness > does abort regardless making these tests flakies. Adding an ignore of the > abort once into the PONR makes sense (Always? HBASE-20022 is for those as yet > unknown cases where it does not). Let me ignore to merge and split in this > issue to address flakeyness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
