[jira] [Updated] (HBASE-14259) Backport Namespace quota support to 98 branch
[ https://issues.apache.org/jira/browse/HBASE-14259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-14259: - Attachment: HBASE-14259_v1_0.98.patch Backport Namespace quota support to 98 branch -- Key: HBASE-14259 URL: https://issues.apache.org/jira/browse/HBASE-14259 Project: HBase Issue Type: New Feature Affects Versions: 0.98.14 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-14259_v1_0.98.patch Namespace quota support (HBASE-8410) has been backported to branch-1 (HBASE-13438). This jira would backport the same to 98 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14259) Backport Namespace quota support to 98 branch
[ https://issues.apache.org/jira/browse/HBASE-14259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-14259: - Status: Patch Available (was: Open) Backport Namespace quota support to 98 branch -- Key: HBASE-14259 URL: https://issues.apache.org/jira/browse/HBASE-14259 Project: HBase Issue Type: New Feature Affects Versions: 0.98.14 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-14259_v1_0.98.patch Namespace quota support (HBASE-8410) has been backported to branch-1 (HBASE-13438). This jira would backport the same to 98 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14259) Backport Namespace quota support to 98 branch
Vandana Ayyalasomayajula created HBASE-14259: Summary: Backport Namespace quota support to 98 branch Key: HBASE-14259 URL: https://issues.apache.org/jira/browse/HBASE-14259 Project: HBase Issue Type: New Feature Affects Versions: 0.98.14 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Namespace quota support (HBASE-8410) has been backported to branch-1 (HBASE-13438). This jira would backport the same to 98 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14259) Backport Namespace quota support to 98 branch
[ https://issues.apache.org/jira/browse/HBASE-14259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14703661#comment-14703661 ] Vandana Ayyalasomayajula commented on HBASE-14259: -- [~apurtell] --Can you take a look at the patch ? Also, please point me to the compatibility checker tool that I need to run against the patch. Backport Namespace quota support to 98 branch -- Key: HBASE-14259 URL: https://issues.apache.org/jira/browse/HBASE-14259 Project: HBase Issue Type: New Feature Affects Versions: 0.98.14 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-14259_v1_0.98.patch Namespace quota support (HBASE-8410) has been backported to branch-1 (HBASE-13438). This jira would backport the same to 98 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14259) Backport Namespace quota support to 98 branch
[ https://issues.apache.org/jira/browse/HBASE-14259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-14259: - Attachment: HBASE-14259_v2_0.98.patch Backport Namespace quota support to 98 branch -- Key: HBASE-14259 URL: https://issues.apache.org/jira/browse/HBASE-14259 Project: HBase Issue Type: New Feature Affects Versions: 0.98.14 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-14259_v1_0.98.patch, HBASE-14259_v2_0.98.patch Namespace quota support (HBASE-8410) has been backported to branch-1 (HBASE-13438). This jira would backport the same to 98 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14259) Backport Namespace quota support to 98 branch
[ https://issues.apache.org/jira/browse/HBASE-14259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-14259: - Attachment: HBASE-14259_v3_0.98.patch Backport Namespace quota support to 98 branch -- Key: HBASE-14259 URL: https://issues.apache.org/jira/browse/HBASE-14259 Project: HBase Issue Type: New Feature Affects Versions: 0.98.14 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-14259_v1_0.98.patch, HBASE-14259_v2_0.98.patch, HBASE-14259_v3_0.98.patch Namespace quota support (HBASE-8410) has been backported to branch-1 (HBASE-13438). This jira would backport the same to 98 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_v4_0.98.patch Changed the wording and method names. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 1.3.0 Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.98_v2.patch, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch, HBASE-13376_6_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch, HBASE-13376_v3_0.98.patch, HBASE-13376_v4_0.98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_v3_0.98.patch Patch with review comments addressed. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 1.3.0 Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.98_v2.patch, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch, HBASE-13376_6_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch, HBASE-13376_v3_0.98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_0.98_v2.patch Could this patch be committed to 0.98 branch ? This patch is slightly different that branch-1 and master. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 1.3.0 Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.98_v2.patch, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch, HBASE-13376_6_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697575#comment-14697575 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- Let me check. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 1.3.0 Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.98_v2.patch, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch, HBASE-13376_6_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[
https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697584#comment-14697584
]
Vandana Ayyalasomayajula commented on HBASE-13376:
--
I ran that specific test on my machine and test finished:
{quote}
testcase name=testJmxMetrics_EnsembleMode
classname=org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics
time=0.236/
testcase name=testJmxMetrics_PerTableMode
classname=org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics
time=0.138/
{quote}
Improvements to Stochastic load balancer
Key: HBASE-13376
URL: https://issues.apache.org/jira/browse/HBASE-13376
Project: HBase
Issue Type: Improvement
Components: Balancer
Affects Versions: 1.0.0, 0.98.12
Reporter: Vandana Ayyalasomayajula
Assignee: Vandana Ayyalasomayajula
Priority: Minor
Fix For: 2.0.0, 1.3.0
Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch,
HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.98_v2.patch,
HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt,
HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch,
HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch,
HBASE-13376_6_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch
There are two things this jira tries to address:
1. The locality picker in the stochastic balancer does not pick regions with
least locality as candidates for swap/move. So when any user configures
locality cost in the configs, the balancer does not always seems to move
regions with bad locality.
2. When a cluster has equal number of loaded regions, it always picks the
first one. It should pick a random region on one of the equally loaded
servers. This improves a chance of finding a good candidate, when load picker
is invoked several times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[
https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694831#comment-14694831
]
Vandana Ayyalasomayajula commented on HBASE-13376:
--
The last build seems to finally have the tests run:
{quote}
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 506.45 sec - in
org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 359.237 sec -
in org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer
{quote}
I cannot seem to find the javadoc warning, that I have introduced :(.
Improvements to Stochastic load balancer
Key: HBASE-13376
URL: https://issues.apache.org/jira/browse/HBASE-13376
Project: HBase
Issue Type: Improvement
Components: Balancer
Affects Versions: 1.0.0, 0.98.12
Reporter: Vandana Ayyalasomayajula
Assignee: Vandana Ayyalasomayajula
Priority: Minor
Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt,
HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt,
HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch,
HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_98.patch,
HBASE-13376_branch-1.patch
There are two things this jira tries to address:
1. The locality picker in the stochastic balancer does not pick regions with
least locality as candidates for swap/move. So when any user configures
locality cost in the configs, the balancer does not always seems to move
regions with bad locality.
2. When a cluster has equal number of loaded regions, it always picks the
first one. It should pick a random region on one of the equally loaded
servers. This improves a chance of finding a good candidate, when load picker
is invoked several times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_5_branch-1.patch Patch for branch-1 Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0 Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_6_branch-1.patch Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0 Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch, HBASE-13376_6_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695842#comment-14695842 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- I made the change based on your comment. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0 Attachments: 13376-v2.txt, 13376-v5.patch, 13376_4.patch, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_5_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_4.patch Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_4.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[
https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693911#comment-14693911
]
Vandana Ayyalasomayajula commented on HBASE-13376:
--
In the last build, the balancer tests passed.
https://builds.apache.org/job/PreCommit-HBASE-Build/15053//consoleFull
{quote}
Running org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.982 sec - in
org.apache.hadoop.hbase.master.TestAssignmentListener
Running org.apache.hadoop.hbase.master.TestMasterMetricsWrapper
Running org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.229 sec - in
org.apache.hadoop.hbase.master.TestMasterMetricsWrapper
Running org.apache.hadoop.hbase.master.balancer.TestBaseLoadBalancer
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.58 sec - in
org.apache.hadoop.hbase.master.balancer.TestBaseLoadBalancer
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.025 sec - in
org.apache.hadoop.hbase.master.handler.TestTableDescriptorModification
Running org.apache.hadoop.hbase.master.balancer.TestDefaultLoadBalancer
{quote}
The one that failed was :
{quote}
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 22.187 sec
FAILURE! - in
org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS
testWalRollOnLowReplication(org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS)
Time elapsed: 11.906 sec ERROR!
java.lang.RuntimeException: sync aborted
at
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.pushData(WALProcedureStore.java:491)
at
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.insert(WALProcedureStore.java:334)
at
org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS.testWalRollOnLowReplication(TestWALProcedureStoreOnHDFS.java:190)
Caused by: org.apache.hadoop.ipc.RemoteException: File
/test-logs/state-0008.log could only be replicated to 2 nodes
instead of minReplication (=3). There are 3 datanode(s) running and 3 node(s)
are excluded in this operation.
at
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1471)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2791)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:606)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:455)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007)
at org.apache.hadoop.ipc.Client.call(Client.java:1411)
at org.apache.hadoop.ipc.Client.call(Client.java:1364)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206)
at com.sun.proxy.$Proxy20.addBlock(Unknown Source)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
at com.sun.proxy.$Proxy20.addBlock(Unknown Source)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:368)
at
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1449)
at
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1270)
at
org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:526)
{quote}
Improvements to Stochastic load balancer
Key: HBASE-13376
URL:
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693990#comment-14693990 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- Okay. Let me see why that test does not finish. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14190) Assign system tables ahead of user region assignment
[
https://issues.apache.org/jira/browse/HBASE-14190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14687390#comment-14687390
]
Vandana Ayyalasomayajula commented on HBASE-14190:
--
In the MetaTableAccessor class, getSystemTableRegionsAndLocations() method,
since we know that we need system table region information and they start with
NamespaceDescriptor.SYSTEM_NAMESPACE_NAME_STR string, can we optimize this :
{quote}
+scanMeta(connection, HConstants.EMPTY_START_ROW, HConstants.EMPTY_END_ROW,
+ QueryType.REGION, visitor);
{quote}
In this way we will avoid scanning the entire meta table.
Assign system tables ahead of user region assignment
Key: HBASE-14190
URL: https://issues.apache.org/jira/browse/HBASE-14190
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Critical
Attachments: 14190-v6.txt, 14190-v7.txt
Currently the namespace table region is assigned like user regions.
I spent several hours working with a customer where master couldn't finish
initialization.
Even though master was restarted quite a few times, it went down with the
following:
{code}
2015-08-05 17:16:57,530 FATAL [hdpmaster1:6.activeMasterManager]
master.HMaster: Master server abort: loaded coprocessors are: []
2015-08-05 17:16:57,530 FATAL [hdpmaster1:6.activeMasterManager]
master.HMaster: Unhandled exception. Starting shutdown.
java.io.IOException: Timedout 30ms waiting for namespace table to be
assigned
at
org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:104)
at org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:985)
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:779)
at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:182)
at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1646)
at java.lang.Thread.run(Thread.java:744)
{code}
During previous run(s), namespace table was created, hence leaving an entry
in hbase:meta.
The following if block in TableNamespaceManager#start() was skipped:
{code}
if (!MetaTableAccessor.tableExists(masterServices.getConnection(),
TableName.NAMESPACE_TABLE_NAME)) {
{code}
TableNamespaceManager#start() spins, waiting for namespace region to be
assigned.
There was issue in master assigning user regions.
We tried issuing 'assign' command from hbase shell which didn't work because
of the following check in MasterRpcServices#assignRegion():
{code}
master.checkInitialized();
{code}
This scenario can be avoided if we assign hbase:namespace table after
hbase:meta is assigned but before user table region assignment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682035#comment-14682035 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- [~tedyu] The balancer related tests seem to have passed. https://builds.apache.org/job/PreCommit-HBASE-Build/15036//testReport/org.apache.hadoop.hbase.master.balancer/ Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682206#comment-14682206 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- How can I trigger the jenkins run again ? Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682133#comment-14682133 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- Hmm.. its actually 14 mins, https://builds.apache.org/job/HBase-TRUNK/6713/testReport/org.apache.hadoop.hbase.master.balancer/ So ideally the test should pass on jenkins also. How can I trigger another run ? Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[
https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682128#comment-14682128
]
Vandana Ayyalasomayajula commented on HBASE-13376:
--
On my machine, the test passes,
{quote}
---
T E S T S
---
Running org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2
Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 755.196 sec -
in org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2
{quote}
Let me quickly check from the previous builds, the running time of this test.
Improvements to Stochastic load balancer
Key: HBASE-13376
URL: https://issues.apache.org/jira/browse/HBASE-13376
Project: HBase
Issue Type: Improvement
Components: Balancer
Affects Versions: 1.0.0, 0.98.12
Reporter: Vandana Ayyalasomayajula
Assignee: Vandana Ayyalasomayajula
Priority: Minor
Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt,
HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt,
HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch,
HBASE-13376_98.patch, HBASE-13376_branch-1.patch
There are two things this jira tries to address:
1. The locality picker in the stochastic balancer does not pick regions with
least locality as candidates for swap/move. So when any user configures
locality cost in the configs, the balancer does not always seems to move
regions with bad locality.
2. When a cluster has equal number of loaded regions, it always picks the
first one. It should pick a random region on one of the equally loaded
servers. This improves a chance of finding a good candidate, when load picker
is invoked several times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_3.patch Attaching again to trigger a new jenkins job. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_3.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_2.patch Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: (was: HBASE-13376_2.patch) Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_3.patch Renamed the patch to avoid confusion. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_3.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_2.patch Removed the code where I was using Rand() to randomly pick one server above average load. That was causing the long time, hence less number of steps were executed in the balancer. So for a given time, the regions were never balanced. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2.patch, HBASE-13376_2_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_branch-1.patch renamed the patch file. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_2_branch-1.patch Fixed failing test. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376.patch patch for master Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: 13376-v2.txt, HBASE-13376.patch, HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_2_branch-1.patch, HBASE-13376_98.patch, HBASE-13376_branch-1.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_1_1.txt Updated patch for branch-1 with review comments addressed. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_1_1.txt, HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_1.txt changes to fix the NPE. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_1.txt, HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550483#comment-14550483 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- [~tedyu] -- Let me take a look at the test failure. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523473#comment-14523473 ] Vandana Ayyalasomayajula commented on HBASE-13438: -- Thanks [~apurtell] for the reply. I am thinking the patch will not be very difficult as branch-1 and 98 code are not too diverged. Since now the branch-1 has the quota framework back ported, it should be easy to back port the same to 98. I will ping you for help with compatibility checked tool. [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1-v2.patch, HBASE-13438-branch-1-v3.patch, HBASE-13438-branch-1.patch, HBASE-13438_withzk.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14522147#comment-14522147 ] Vandana Ayyalasomayajula commented on HBASE-13438: -- [~apurtell] -- can this JIRA be back ported to 98 branch ? If its possible, I will create another JIRA for back port into 98. Thanks !! [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1-v2.patch, HBASE-13438-branch-1-v3.patch, HBASE-13438-branch-1.patch, HBASE-13438_withzk.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13463) Quota needs to be updated only in case of successful region merge
[ https://issues.apache.org/jira/browse/HBASE-13463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14498363#comment-14498363 ] Vandana Ayyalasomayajula commented on HBASE-13463: -- +1 for v2 patch, given the unit tests pass. Quota needs to be updated only in case of successful region merge - Key: HBASE-13463 URL: https://issues.apache.org/jira/browse/HBASE-13463 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 1.1.0 Attachments: 13463-v1.txt, 13463-v2-branch-1.txt During review of HBASE-13438, Vandana pointed out the following: in the case of MERGE_REVERTED, the assignment manager is not updating the quota. You need to add another hook in RegionStateListener class just like split. This issue is to fix the above case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493650#comment-14493650 ] Vandana Ayyalasomayajula commented on HBASE-13438: -- [~ashish singhi] -- yes that could be done, as that case is not handled in the master branch too. Please open a JIRA. Otherwise the latest patch looks good to me +1. [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1-v2.patch, HBASE-13438-branch-1-v3.patch, HBASE-13438-branch-1.patch, HBASE-13438_withzk.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13463) Quota needs to be updated only in case of successful region merge
[
https://issues.apache.org/jira/browse/HBASE-13463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14495204#comment-14495204
]
Vandana Ayyalasomayajula commented on HBASE-13463:
--
[~tedyu] -- The idea of updating quota only on successful merge sounds good, as
I think concurrent merge operations would be rare unlike splits.
looking at the v2 patch,
{quote}
if (code == TransitionCode.MERGED
org.apache.commons.lang.StringUtils.isEmpty(errorMsg)) {
+try {
+ regionStateListener.onRegionMerged(hri);
+} catch (IOException exp) {
+ errorMsg = StringUtils.stringifyException(exp);
+}
+ }
{quote}
shouldn't that be under MERGED case rather than MERGE_REVERTED ?
Quota needs to be updated only in case of successful region merge
-
Key: HBASE-13463
URL: https://issues.apache.org/jira/browse/HBASE-13463
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 1.1.0
Attachments: 13463-v1.txt, 13463-v2-branch-1.txt
During review of HBASE-13438, Vandana pointed out the following:
in the case of MERGE_REVERTED, the assignment manager is not updating the
quota. You need to add another hook in RegionStateListener class just like
split.
This issue is to fix the above case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492725#comment-14492725 ] Vandana Ayyalasomayajula commented on HBASE-13438: -- @ashish -- In the latest patch, I realized that in the case of MERGE_REVERTED, the assignment manager is not updating the quota. You need to add another hook in RegionStateListener class just like split. [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1-v2.patch, HBASE-13438-branch-1-v3.patch, HBASE-13438-branch-1.patch, HBASE-13438_withzk.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14490490#comment-14490490 ] Vandana Ayyalasomayajula commented on HBASE-13438: -- For me when I execute: mvn clean package -Dtest=TestNamespaceAuditor I get the following: --- T E S T S --- Running org.apache.hadoop.hbase.namespace.TestNamespaceAuditor Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 26.52 sec FAILURE! - in org.apache.hadoop.hbase.namespace.TestNamespaceAuditor testRegionOperations(org.apache.hadoop.hbase.namespace.TestNamespaceAuditor) Time elapsed: 6.222 sec FAILURE! java.lang.AssertionError: expected:2 but was:3 at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.junit.Assert.assertEquals(Assert.java:542) at org.apache.hadoop.hbase.namespace.TestNamespaceAuditor.testRegionOperations(TestNamespaceAuditor.java:473) Results : Failed tests: TestNamespaceAuditor.testRegionOperations:473 expected:2 but was:3 which I expect. The namespace state manager needs to listen to the zk events ( split/merge) and then update quota. [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1-v2.patch, HBASE-13438-branch-1.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13438: - Attachment: HBASE-13438_withzk.patch The above patch actually makes the test pass. We can keep this jira for zk less assignment and the for zk assignment I will open another jira and attach the above addendum patch. @ashish -- could you please remove the test which uses the zk assignment, then I can +1 the final patch. [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1-v2.patch, HBASE-13438-branch-1.patch, HBASE-13438_withzk.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14490504#comment-14490504 ] Vandana Ayyalasomayajula commented on HBASE-13376: -- [~stack] -- Do you have some time to review the patch ? I will look at the cause of test failures. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14490633#comment-14490633 ] Vandana Ayyalasomayajula commented on HBASE-13438: -- @ashish -- you can actually combine my addendum patch on top of your latest patch. That will makes things simple. I can review then the latest patch. Thanks!! [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1-v2.patch, HBASE-13438-branch-1.patch, HBASE-13438_withzk.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13438) [branch-1] Backport Basic quota support for namespaces
[ https://issues.apache.org/jira/browse/HBASE-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487886#comment-14487886 ] Vandana Ayyalasomayajula commented on HBASE-13438: -- @ashish -- The patch looks good for zkless assignment, but branch-1 has both zkless and zk assignment. So I think you need to handle split/merge regions for zk assignment too. [branch-1] Backport Basic quota support for namespaces -- Key: HBASE-13438 URL: https://issues.apache.org/jira/browse/HBASE-13438 Project: HBase Issue Type: Task Affects Versions: 1.1.0 Reporter: Ashish Singhi Assignee: Ashish Singhi Labels: quota Fix For: 1.1.0 Attachments: HBASE-13438-branch-1-v1.patch, HBASE-13438-branch-1.patch This task for backporting HBASE-8410, HBASE-12936 and HBASE-13357 to branch-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_0.txt patch for master branch. All the unit tests related to the changes are passing. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_0.txt, HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_0.98.txt Renamed the patch file. [~stack] I will try to provide a patch for the master branch today. Sorry for the late replies, I was out of office last week. Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_0.98.txt, HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-13376) Improvements to Stochastic load balancer
Vandana Ayyalasomayajula created HBASE-13376: Summary: Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 0.98.12, 1.0.0 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Status: Patch Available (was: Open) Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 0.98.12, 1.0.0 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13376) Improvements to Stochastic load balancer
[ https://issues.apache.org/jira/browse/HBASE-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-13376: - Attachment: HBASE-13376_98.patch Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 1.0.0, 0.98.12 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-13376_98.patch There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12936) Quota support for namespace should take region merge into account
[ https://issues.apache.org/jira/browse/HBASE-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295720#comment-14295720 ] Vandana Ayyalasomayajula commented on HBASE-12936: -- The test case for merge should have a scenario when merge operation fails. Other than that the patch looks good. Thanks [~tedyu] Quota support for namespace should take region merge into account - Key: HBASE-12936 URL: https://issues.apache.org/jira/browse/HBASE-12936 Project: HBase Issue Type: Sub-task Reporter: Ted Yu Assignee: Ted Yu Attachments: 12936-002.txt, 12936-003.txt HBASE-8410 added basic quota support for namespaces. However, region merge operation was not taken into account. This means, once region count limit is reached, user table cannot be split even after some regions are successfully merged. This issue fixes the bug by adding hook in RegionStateListener for region merged event. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292186#comment-14292186
]
Vandana Ayyalasomayajula commented on HBASE-8410:
-
I have added release notes to this jira. Please let me know if I need to modify
something. Also should I be creating a backport jira for branch-1 and 98 ? The
code base seems quite different and some work needs to be done for the
backport.
Thanks Ted for committing the patch.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 2.0.0
Attachments: 8410-master.9.patch, HBASE-8410-master.1.patch,
HBASE-8410-master.4.patch, HBASE-8410-master.5.patch,
HBASE-8410-master.6.patch, HBASE-8410-master.7.patch,
HBASE-8410-master.9.patch, HBASE-8410-master.patch, HBASE-8410.docx,
HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Release Note:
Namespace auditor provides basic quota support for namespaces in terms of
number of tables and number of regions. In order to use namespace quotas, quota
support must be enabled by setting
hbase.quota.enabled property to true in hbase-site.xml file.
The users can add quota information to namespace, while creating new namespaces
or by altering existing ones.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregions'='10'}
2. namespace_create 'ns2',
{'hbase.namespace.quota.maxtables'='2','hbase.namespace.quota.maxregion'='5'}
3. alter_namespace 'ns3', {METHOD = 'set',
'hbase.namespace.quota.maxtables'='5','hbase.namespace.quota.maxregion'='25'}
The quotas can be modified/added to namespace at any point of time.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 2.0.0
Attachments: 8410-master.9.patch, HBASE-8410-master.1.patch,
HBASE-8410-master.4.patch, HBASE-8410-master.5.patch,
HBASE-8410-master.6.patch, HBASE-8410-master.7.patch,
HBASE-8410-master.9.patch, HBASE-8410-master.patch, HBASE-8410.docx,
HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289723#comment-14289723
]
Vandana Ayyalasomayajula commented on HBASE-8410:
-
The latest patch HBASE-8410-master.9.patch is the one in RB. So the last
hadoopqa test results should be good.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.1.patch, HBASE-8410-master.4.patch,
HBASE-8410-master.5.patch, HBASE-8410-master.6.patch,
HBASE-8410-master.7.patch, HBASE-8410-master.9.patch,
HBASE-8410-master.patch, HBASE-8410.docx, HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: HBASE-8410-master.9.patch
Latest patch in review board.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.1.patch, HBASE-8410-master.4.patch,
HBASE-8410-master.5.patch, HBASE-8410-master.6.patch,
HBASE-8410-master.7.patch, HBASE-8410-master.9.patch,
HBASE-8410-master.patch, HBASE-8410.docx, HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: HBASE-8410-master.7.patch
Patch to fix unit tests.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.1.patch, HBASE-8410-master.4.patch,
HBASE-8410-master.5.patch, HBASE-8410-master.6.patch,
HBASE-8410-master.7.patch, HBASE-8410-master.patch, HBASE-8410.docx,
HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: HBASE-8410-master.6.patch
Patch for fixing javadoc and find bugs warnings.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.1.patch, HBASE-8410-master.4.patch,
HBASE-8410-master.5.patch, HBASE-8410-master.6.patch,
HBASE-8410-master.patch, HBASE-8410.docx, HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: HBASE-12694-branch-1.2.patch Patch for branch-1 which makes split transaction unit test to pass with and without zk assignment. testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 0.98.10, 1.1.0 Attachments: HBASE-12694-98.1.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.2.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: HBASE-12694-master.2.patch Rebased patch for master. No code changes. testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 0.98.10, 1.1.0 Attachments: HBASE-12694-98.1.patch, HBASE-12694-98.2.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.2.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.2.patch, HBASE-12694-master.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Status: Patch Available (was: Reopened) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 0.98.9, 1.0.0 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 0.98.10, 1.1.0 Attachments: HBASE-12694-98.1.patch, HBASE-12694-98.2.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.2.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.2.patch, HBASE-12694-master.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: HBASE-8410-master.5.patch
Patch for fixing unit tests.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.1.patch, HBASE-8410-master.4.patch,
HBASE-8410-master.5.patch, HBASE-8410-master.patch, HBASE-8410.docx,
HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: HBASE-12694-98.2.patch Patch for 98 branch. testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 0.98.10, 1.1.0 Attachments: HBASE-12694-98.1.patch, HBASE-12694-98.2.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.2.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: HBASE-8410-master.4.patch
Latest patch from review board after addressing comments.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.1.patch, HBASE-8410-master.4.patch,
HBASE-8410-master.patch, HBASE-8410.docx, HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: HBASE-8410-master.1.patch
Updated patch for master. Removed .backup file. The inclusion was
unintentional.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.1.patch, HBASE-8410-master.patch,
HBASE-8410.docx, HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE_8410_1_trunk.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_10.patch,
HBASE-8410_trunk_11.patch, HBASE-8410_trunk_12.patch,
HBASE-8410_trunk_13.patch, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_15.patch, HBASE-8410_trunk_2.patch,
HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch, HBASE-8410_trunk_7.patch,
HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE_8410_98_16.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_10.patch,
HBASE-8410_trunk_11.patch, HBASE-8410_trunk_12.patch,
HBASE-8410_trunk_13.patch, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_15.patch, HBASE-8410_trunk_2.patch,
HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch, HBASE-8410_trunk_7.patch,
HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_10.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_10.patch,
HBASE-8410_trunk_11.patch, HBASE-8410_trunk_12.patch,
HBASE-8410_trunk_13.patch, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_15.patch, HBASE-8410_trunk_2.patch,
HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch, HBASE-8410_trunk_7.patch,
HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE_8410.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_10.patch,
HBASE-8410_trunk_11.patch, HBASE-8410_trunk_12.patch,
HBASE-8410_trunk_13.patch, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_15.patch, HBASE-8410_trunk_2.patch,
HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch, HBASE-8410_trunk_7.patch,
HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_11.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_2.patch, HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch,
HBASE-8410_trunk_7.patch, HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_13.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_2.patch, HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch,
HBASE-8410_trunk_7.patch, HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_12.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_2.patch, HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch,
HBASE-8410_trunk_7.patch, HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_10.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_2.patch, HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch,
HBASE-8410_trunk_7.patch, HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_2.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch, HBASE-8410_trunk_7.patch,
HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_15.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_2.patch, HBASE-8410_trunk_3.patch, HBASE-8410_trunk_4.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch, HBASE-8410_trunk_6.patch,
HBASE-8410_trunk_7.patch, HBASE-8410_trunk_8.patch, HBASE-8410_trunk_9.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_9.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_3.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_7.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_4.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_8.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_6.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_4.patch, HBASE-8410_trunk_5.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_5.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch,
HBASE-8410_trunk_4.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: (was: HBASE-8410_trunk_4.patch)
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410.docx, HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-8410) Basic quota support for namespaces
[
https://issues.apache.org/jira/browse/HBASE-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vandana Ayyalasomayajula updated HBASE-8410:
Attachment: HBASE-8410-master.patch
Updated patch for master.
Basic quota support for namespaces
--
Key: HBASE-8410
URL: https://issues.apache.org/jira/browse/HBASE-8410
Project: HBase
Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Attachments: HBASE-8410-master.patch, HBASE-8410.docx,
HBASE-8410_trunk_14.patch
This task involves creating an observer which provides basic quota support to
namespaces in terms of (1) number of tables and (2) number of regions. The
quota support can be enabled by setting:
property
namehbase.coprocessor.region.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
property
namehbase.coprocessor.master.classes/name
valueorg.apache.hadoop.hbase.namespace.NamespaceController/value
/property
in the hbase-site.xml.
To add quotas to namespace, while creating namespace properties need to be
added.
Examples:
1. namespace_create 'ns1', {'hbase.namespace.quota.maxregion'='10'}
2. 1. namespace_create 'ns2', {'hbase.namespace.quota.maxtables'='2'},
{'hbase.namespace.quota.maxregion'='5'}
The quotas can be modified/added to namespace at any point of time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: HBASE-12694-master.patch Patch for master. testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-12694-branch-1.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: HBASE-12694-branch-1.1.patch HBASE-12694-98.1.patch Patch for 98 and branch-1 after recent merges. testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-12694-98.1.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: HBASE-12694-98.1.patch HBASE-12694-branch-1.1.patch testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-12694-98.1.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: (was: HBASE-12694-98.1.patch) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-12694-98.1.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: (was: HBASE-12694-branch-1.1.patch) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-12694-98.1.patch, HBASE-12694-branch-1.1.patch, HBASE-12694-branch-1.patch, HBASE-12694-master.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula reassigned HBASE-12694: Assignee: Vandana Ayyalasomayajula testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
[ https://issues.apache.org/jira/browse/HBASE-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12694: - Attachment: HBASE-12694-branch-1.patch Patch for branch-1. testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition - Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 1.0.0, 0.98.9 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Attachments: HBASE-12694-branch-1.patch There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[ https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12686: - Attachment: HBASE-12686-98.patch Patch for 98 branch Failures in split before PONR not clearing the daughter regions from regions in transition during rollback -- Key: HBASE-12686 URL: https://issues.apache.org/jira/browse/HBASE-12686 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 0.98.9 Reporter: Rajeshbabu Chintaguntla Assignee: Vandana Ayyalasomayajula Priority: Blocker Fix For: 1.0.0, 2.0.0, 0.98.9 Attachments: HBASE-12686-98.patch, HBASE-12686-branch-1.patch If there are any split failures then the both daughter regions left in SPLITTING_NEW transition even after rollback, which will block balancing to happen forever until unless master is restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[
https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247040#comment-14247040
]
Vandana Ayyalasomayajula commented on HBASE-12686:
--
[~apurtell] The balancing is blocked as the daughter regions remain in
transition forever. So if we make sure that after as failed split, the daughter
regions are cleared from regions in transition, it must be good enough. But as
a precaution, I will add a check that balance method returns true.
{quote}
Any chance the daughters may no longer be in transition at this point?:
1322 if
(regionStates.isRegionInTransition(hri_a.getEncodedName())) {
1323regionOffline(hri_a);
1324 }
1325 if
(regionStates.isRegionInTransition(hri_b.getEncodedName())) {
1326regionOffline(hri_b);
1327 }
Just wondering why this change should not always offline the daughters.
{quote}
The daughters must be be transition state when a split operation fails. I am
making sure the checks are tighter and making the daughter offline.
Failures in split before PONR not clearing the daughter regions from regions
in transition during rollback
--
Key: HBASE-12686
URL: https://issues.apache.org/jira/browse/HBASE-12686
Project: HBase
Issue Type: Bug
Components: Region Assignment
Affects Versions: 0.98.9
Reporter: Rajeshbabu Chintaguntla
Assignee: Vandana Ayyalasomayajula
Priority: Blocker
Fix For: 1.0.0, 0.98.9
Attachments: HBASE-12686-98.patch, HBASE-12686-branch-1.patch
If there are any split failures then the both daughter regions left in
SPLITTING_NEW transition even after rollback, which will block balancing to
happen forever until unless master is restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[
https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247059#comment-14247059
]
Vandana Ayyalasomayajula commented on HBASE-12686:
--
[~rajeshbabu] Could you elaborate on what you meant by
{quote}
2) Can we just use locking so that we can wait from failure happened instead of
waiting from when split requested?
{quote}
I will add a test in the TestSplitTransactionOnCluster class and reuse
FailingSplitRegionObserver as per your suggestion.
Failures in split before PONR not clearing the daughter regions from regions
in transition during rollback
--
Key: HBASE-12686
URL: https://issues.apache.org/jira/browse/HBASE-12686
Project: HBase
Issue Type: Bug
Components: Region Assignment
Affects Versions: 0.98.9
Reporter: Rajeshbabu Chintaguntla
Assignee: Vandana Ayyalasomayajula
Priority: Blocker
Fix For: 1.0.0, 0.98.9
Attachments: HBASE-12686-98.patch, HBASE-12686-branch-1.patch
If there are any split failures then the both daughter regions left in
SPLITTING_NEW transition even after rollback, which will block balancing to
happen forever until unless master is restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[ https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12686: - Attachment: HBASE-12686-branch-1.1.patch Updated patch to branch-1 addressing comments. Please review this patch so that I can create a patch for 98 branch. Thanks !! Failures in split before PONR not clearing the daughter regions from regions in transition during rollback -- Key: HBASE-12686 URL: https://issues.apache.org/jira/browse/HBASE-12686 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 0.98.9 Reporter: Rajeshbabu Chintaguntla Assignee: Vandana Ayyalasomayajula Priority: Blocker Fix For: 1.0.0, 0.98.9 Attachments: HBASE-12686-98.patch, HBASE-12686-branch-1.1.patch, HBASE-12686-branch-1.patch If there are any split failures then the both daughter regions left in SPLITTING_NEW transition even after rollback, which will block balancing to happen forever until unless master is restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[ https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247156#comment-14247156 ] Vandana Ayyalasomayajula commented on HBASE-12686: -- [~apurtell] There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. That is the reason that I have not added an assert for balance method in the unit test of this JIRA. Can we address this issue in a separate JIRA ? Failures in split before PONR not clearing the daughter regions from regions in transition during rollback -- Key: HBASE-12686 URL: https://issues.apache.org/jira/browse/HBASE-12686 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 0.98.9 Reporter: Rajeshbabu Chintaguntla Assignee: Vandana Ayyalasomayajula Priority: Blocker Fix For: 1.0.0, 0.98.9 Attachments: HBASE-12686-98.patch, HBASE-12686-branch-1.1.patch, HBASE-12686-branch-1.patch If there are any split failures then the both daughter regions left in SPLITTING_NEW transition even after rollback, which will block balancing to happen forever until unless master is restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[ https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12686: - Attachment: HBASE-12686-branch-1.2.patch Addressed comment. Failures in split before PONR not clearing the daughter regions from regions in transition during rollback -- Key: HBASE-12686 URL: https://issues.apache.org/jira/browse/HBASE-12686 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 0.98.9 Reporter: Rajeshbabu Chintaguntla Assignee: Vandana Ayyalasomayajula Priority: Blocker Fix For: 1.0.0, 0.98.9 Attachments: HBASE-12686-98.patch, HBASE-12686-branch-1.1.patch, HBASE-12686-branch-1.2.patch, HBASE-12686-branch-1.patch If there are any split failures then the both daughter regions left in SPLITTING_NEW transition even after rollback, which will block balancing to happen forever until unless master is restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12694) testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition
Vandana Ayyalasomayajula created HBASE-12694: Summary: testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class leaves regions in transition Key: HBASE-12694 URL: https://issues.apache.org/jira/browse/HBASE-12694 Project: HBase Issue Type: Bug Affects Versions: 0.98.9, 1.0.0 Reporter: Vandana Ayyalasomayajula Priority: Minor There seems to a clean up issue with the unit test testTableExistsIfTheSpecifiedTableRegionIsSplitParent in TestSplitTransactionOnCluster class. It always has a region in transition. So any unit test that executes after that test, will cause balance method to return false. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[ https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12686: - Attachment: HBASE-12686-98.1.patch Patch for 98 branch. Failures in split before PONR not clearing the daughter regions from regions in transition during rollback -- Key: HBASE-12686 URL: https://issues.apache.org/jira/browse/HBASE-12686 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 0.98.9 Reporter: Rajeshbabu Chintaguntla Assignee: Vandana Ayyalasomayajula Priority: Blocker Fix For: 1.0.0, 0.98.9 Attachments: HBASE-12686-98.1.patch, HBASE-12686-98.patch, HBASE-12686-branch-1.1.patch, HBASE-12686-branch-1.2.patch, HBASE-12686-branch-1.patch If there are any split failures then the both daughter regions left in SPLITTING_NEW transition even after rollback, which will block balancing to happen forever until unless master is restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[ https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12686: - Attachment: HBASE-12686-98.2.patch Added additional check to avoid any NPE which fetching daughter regions. Failures in split before PONR not clearing the daughter regions from regions in transition during rollback -- Key: HBASE-12686 URL: https://issues.apache.org/jira/browse/HBASE-12686 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 0.98.9 Reporter: Rajeshbabu Chintaguntla Assignee: Vandana Ayyalasomayajula Priority: Blocker Fix For: 1.0.0, 0.98.9 Attachments: HBASE-12686-98.1.patch, HBASE-12686-98.2.patch, HBASE-12686-98.patch, HBASE-12686-branch-1.1.patch, HBASE-12686-branch-1.2.patch, HBASE-12686-branch-1.patch If there are any split failures then the both daughter regions left in SPLITTING_NEW transition even after rollback, which will block balancing to happen forever until unless master is restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12686) Failures in split before PONR not clearing the daughter regions from regions in transition during rollback
[ https://issues.apache.org/jira/browse/HBASE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12686: - Attachment: HBASE-12686-branch-1.3.patch Failures in split before PONR not clearing the daughter regions from regions in transition during rollback -- Key: HBASE-12686 URL: https://issues.apache.org/jira/browse/HBASE-12686 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 0.98.9 Reporter: Rajeshbabu Chintaguntla Assignee: Vandana Ayyalasomayajula Priority: Blocker Fix For: 1.0.0, 0.98.9 Attachments: HBASE-12686-98.1.patch, HBASE-12686-98.2.patch, HBASE-12686-98.patch, HBASE-12686-branch-1.1.patch, HBASE-12686-branch-1.2.patch, HBASE-12686-branch-1.3.patch, HBASE-12686-branch-1.patch If there are any split failures then the both daughter regions left in SPLITTING_NEW transition even after rollback, which will block balancing to happen forever until unless master is restarted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
