[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread Matteo Bertozzi (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matteo Bertozzi updated HBASE-16794:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch, HBASE-16794.v1.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Status: Patch Available  (was: Open)

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch, HBASE-16794.v1.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Attachment: HBASE-16794.v1.patch

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch, HBASE-16794.v1.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Status: Open  (was: Patch Available)

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Status: Patch Available  (was: Open)

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Attachment: HBASE-16794.v0.patch

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Status: Open  (was: Patch Available)

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Attachment: (was: HBASE-16794.v0.patch)

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Assignee: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Status: Patch Available  (was: Open)

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Attachment: HBASE-16794.v0.patch

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16794.v0.patch
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Description: 
The default count of merge thread is 1, so the merge requests submitted by 
TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
too early to check the region states, it will introduce the error.
This patch checks the number of running merge task instead of the regions state.

  was:
The default count of merge thread is 1, so the merge requests submitted by 
TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
too early to check the region states, it will introduce the error.
This patch checks the number of running merge task instead of the regions 
states.


> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Component/s: test

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> states.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

2016-10-09 Thread ChiaPing Tsai (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ChiaPing Tsai updated HBASE-16794:
--
Fix Version/s: 2.0.0

> TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
> -
>
> Key: HBASE-16794
> URL: https://issues.apache.org/jira/browse/HBASE-16794
> Project: HBase
>  Issue Type: Test
>  Components: test
>Reporter: ChiaPing Tsai
>Priority: Minor
> Fix For: 2.0.0
>
>
> The default count of merge thread is 1, so the merge requests submitted by 
> TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
> too early to check the region states, it will introduce the error.
> This patch checks the number of running merge task instead of the regions 
> states.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)