date:20121105

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

Francis Liu updated HBASE-6721:
---

Attachment: HBASE-5498_94_4.patch

Updated patch addressed most of the comments. Mainly:

- moved storage of group information from hdfs to zookeeper
- cleaned up whitespace and removed unnecessary changes into core master classes

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-5498_94_4.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

In multi-tenant deployments of HBase, it is likely that a RegionServer will
be serving out regions from a number of different tables owned by various
client applications. Being able to group a subset of running RegionServers
and assign specific tables to it, provides a client application a level of
isolation and resource allocation.
The proposal essentially is to have an AssignmentManager which is aware of
RegionServer groups and assigns tables to region servers based on groupings.
Load balancing will occur on a per group basis as well.
This is essentially a simplification of the approach taken in HBASE-4120. See
attached document.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490503#comment-13490503
]

Hadoop QA commented on HBASE-6721:
--

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12552071/HBASE-5498_94_4.patch
against trunk revision .

{color:green}+1 @author{color}. The patch does not contain any @author
tags.

{color:green}+1 tests included{color}. The patch appears to include 20 new
or modified tests.

{color:red}-1 patch{color}. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3224//console

This message is automatically generated.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-5498_94_4.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490504#comment-13490504
]

Francis Liu commented on HBASE-6721:

{quote}
This stuff should all be pulled out into a separate package that can be put
into a Maven module like done with security in 0.94.
{quote}
Isn't that a bit too much overhead? Wasn't the reason security was a separate
module was because it had to depend on a secure version of hadoop which the
community didn't want?

{quote}
What changes to core code remain after that?
{quote}
I've updated the patch, there should be minimal and no invasive changes.

{quote}
Right, so you could assign ROOT, META, and the group table randomly at first,
and then calculate placement and moves of the rest and perhaps also META and
group after the group table becomes available, right? Worst case that would
be 3 moves?
{quote}
Since we are not doing any changes to the assignment manager this actually is
complicated since we won't really know what state assignment is in based on
just calls to the load balancer and information we can glean through the master
services.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-5498_94_4.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Created] (HBASE-7097) Log message in SecureServer.class pointing to wrong class path.

Y. SREENIVASULU REDDY created HBASE-7097:


 Summary: Log message in SecureServer.class pointing to wrong class 
path.
 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.94.2, 0.92.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3


log messages are printing wrongly in 
org.apache.hadoop.hbase.ipc.SecureServer.class 
{code}
public static final Log LOG = 
LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
  private static final Log AUDITLOG = 
LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490507#comment-13490507
]

Francis Liu commented on HBASE-6721:

anyone know how to get a git patch onto review board? It seems it only works
for trunk.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Updated] (HBASE-6721) RegionServer Group based Assignment


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

Francis Liu updated HBASE-6721:
---

Attachment: (was: HBASE-5498_94_4.patch)

 RegionServer Group based Assignment
 ---

 Key: HBASE-6721
 URL: https://issues.apache.org/jira/browse/HBASE-6721
 Project: HBase
  Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch, 
 HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf


 In multi-tenant deployments of HBase, it is likely that a RegionServer will 
 be serving out regions from a number of different tables owned by various 
 client applications. Being able to group a subset of running RegionServers 
 and assign specific tables to it, provides a client application a level of 
 isolation and resource allocation.
 The proposal essentially is to have an AssignmentManager which is aware of 
 RegionServer groups and assigns tables to region servers based on groupings. 
 Load balancing will occur on a per group basis as well. 
 This is essentially a simplification of the approach taken in HBASE-4120. See 
 attached document.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6721) RegionServer Group based Assignment


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

Francis Liu updated HBASE-6721:
---

Attachment: HBASE-6721_94_2.patch

 RegionServer Group based Assignment
 ---

 Key: HBASE-6721
 URL: https://issues.apache.org/jira/browse/HBASE-6721
 Project: HBase
  Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch, 
 HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf


 In multi-tenant deployments of HBase, it is likely that a RegionServer will 
 be serving out regions from a number of different tables owned by various 
 client applications. Being able to group a subset of running RegionServers 
 and assign specific tables to it, provides a client application a level of 
 isolation and resource allocation.
 The proposal essentially is to have an AssignmentManager which is aware of 
 RegionServer groups and assigns tables to region servers based on groupings. 
 Load balancing will occur on a per group basis as well. 
 This is essentially a simplification of the approach taken in HBASE-4120. See 
 attached document.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7043) Region Server Group CLI commands


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

Francis Liu updated HBASE-7043:
---

Attachment: HBASE-7043_94_2.patch

incorporated comments. included a backport for setting table properties.

 Region Server Group CLI commands
 

 Key: HBASE-7043
 URL: https://issues.apache.org/jira/browse/HBASE-7043
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: HBASE-7043_94_2.patch, HBASE-7043_94.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7043) Region Server Group CLI commands


[ 
https://issues.apache.org/jira/browse/HBASE-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490509#comment-13490509
 ] 

Hadoop QA commented on HBASE-7043:
--

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12552074/HBASE-7043_94_2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3225//console

This message is automatically generated.

 Region Server Group CLI commands
 

 Key: HBASE-7043
 URL: https://issues.apache.org/jira/browse/HBASE-7043
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: HBASE-7043_94_2.patch, HBASE-7043_94.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490511#comment-13490511
]

Hadoop QA commented on HBASE-6721:
--

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12552073/HBASE-6721_94_2.patch
against trunk revision .

{color:green}+1 @author{color}. The patch does not contain any @author
tags.

{color:green}+1 tests included{color}. The patch appears to include 20 new
or modified tests.

{color:red}-1 patch{color}. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3226//console

This message is automatically generated.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Updated] (HBASE-7043) Region Server Group CLI commands


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

Francis Liu updated HBASE-7043:
---

Attachment: HBASE-6721_94_2.patch

removed master coprocessor changes from patch.

 Region Server Group CLI commands
 

 Key: HBASE-7043
 URL: https://issues.apache.org/jira/browse/HBASE-7043
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-7043_94_2.patch, 
 HBASE-7043_94.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7043) Region Server Group CLI commands


[ 
https://issues.apache.org/jira/browse/HBASE-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490518#comment-13490518
 ] 

Hadoop QA commented on HBASE-7043:
--

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12552075/HBASE-6721_94_2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 14 new 
or modified tests.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/3227//console

This message is automatically generated.

 Region Server Group CLI commands
 

 Key: HBASE-7043
 URL: https://issues.apache.org/jira/browse/HBASE-7043
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-7043_94_2.patch, 
 HBASE-7043_94.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7097) Log message in SecureServer.class pointing to wrong class path.


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

Y. SREENIVASULU REDDY updated HBASE-7097:
-

Status: Patch Available  (was: Open)

 Log message in SecureServer.class pointing to wrong class path.
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.94.2, 0.92.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7097) Log message in SecureServer.class pointing to wrong class path.


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

Y. SREENIVASULU REDDY updated HBASE-7097:
-

Status: Open  (was: Patch Available)

 Log message in SecureServer.class pointing to wrong class path.
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.94.2, 0.92.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6694) Test scanner batching in export job feature HBASE-6372 AND report on improvement HBASE-6372 adds

2012-11-05 Thread Alexander Alten-Lorenz (JIRA)


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

Alexander Alten-Lorenz updated HBASE-6694:
--

Attachment: (was: HBASE-6694.patch)

 Test scanner batching in export job feature HBASE-6372 AND report on 
 improvement HBASE-6372 adds
 

 Key: HBASE-6694
 URL: https://issues.apache.org/jira/browse/HBASE-6694
 Project: HBase
  Issue Type: Task
Reporter: stack
Assignee: Alexander Alten-Lorenz

 From tail of HBASE-6372, Jon had raised issue that test added did not 
 actually test the feature.  This issue is about adding a test of HBASE-6372.  
 We should also have numbers for the improvement that HBASE-6372 brings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6694) Test scanner batching in export job feature HBASE-6372 AND report on improvement HBASE-6372 adds

2012-11-05 Thread Alexander Alten-Lorenz (JIRA)


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

Alexander Alten-Lorenz updated HBASE-6694:
--

Attachment: HBASE-6694.patch

 Test scanner batching in export job feature HBASE-6372 AND report on 
 improvement HBASE-6372 adds
 

 Key: HBASE-6694
 URL: https://issues.apache.org/jira/browse/HBASE-6694
 Project: HBase
  Issue Type: Task
Reporter: stack
Assignee: Alexander Alten-Lorenz
 Attachments: HBASE-6694.patch


 From tail of HBASE-6372, Jon had raised issue that test added did not 
 actually test the feature.  This issue is about adding a test of HBASE-6372.  
 We should also have numbers for the improvement that HBASE-6372 brings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6694) Test scanner batching in export job feature HBASE-6372 AND report on improvement HBASE-6372 adds

2012-11-05 Thread Alexander Alten-Lorenz (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490554#comment-13490554
 ] 

Alexander Alten-Lorenz commented on HBASE-6694:
---

New patch attached, but I get a surefire error from testWithDeletes. 

{code}
testSimpleCase(org.apache.hadoop.hbase.mapreduce.TestImportExport)  Time 
elapsed: 0.029 sec   FAILURE!
java.lang.AssertionError: expected:3 but was:1
at org.junit.Assert.fail(Assert.java:93)

testWithDeletes(org.apache.hadoop.hbase.mapreduce.TestImportExport)  Time 
elapsed: 0.007 sec   ERROR!
java.lang.ArrayIndexOutOfBoundsException: 2
at 
org.apache.hadoop.hbase.mapreduce.TestImportExport.testWithDeletes(TestImportExport.java:277)

{code}

 Test scanner batching in export job feature HBASE-6372 AND report on 
 improvement HBASE-6372 adds
 

 Key: HBASE-6694
 URL: https://issues.apache.org/jira/browse/HBASE-6694
 Project: HBase
  Issue Type: Task
Reporter: stack
Assignee: Alexander Alten-Lorenz
 Attachments: HBASE-6694.patch


 From tail of HBASE-6372, Jon had raised issue that test added did not 
 actually test the feature.  This issue is about adding a test of HBASE-6372.  
 We should also have numbers for the improvement that HBASE-6372 brings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6694) Test scanner batching in export job feature HBASE-6372 AND report on improvement HBASE-6372 adds

[
https://issues.apache.org/jira/browse/HBASE-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490576#comment-13490576
]

Hadoop QA commented on HBASE-6694:
--

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12552084/HBASE-6694.patch
against trunk revision .

{color:green}+1 @author{color}. The patch does not contain any @author
tags.

{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.

{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.

{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
85 warning messages.

{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.

{color:red}-1 findbugs{color}. The patch appears to introduce 4 new
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.

{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestImportExport

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3228//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3228//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3228//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3228//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3228//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3228//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3228//console

This message is automatically generated.

Test scanner batching in export job feature HBASE-6372 AND report on
improvement HBASE-6372 adds

Key: HBASE-6694
URL: https://issues.apache.org/jira/browse/HBASE-6694
Project: HBase
Issue Type: Task
Reporter: stack
Assignee: Alexander Alten-Lorenz
Attachments: HBASE-6694.patch

From tail of HBASE-6372, Jon had raised issue that test added did not
actually test the feature. This issue is about adding a test of HBASE-6372.
We should also have numbers for the improvement that HBASE-6372 brings.

[jira] [Commented] (HBASE-6356) printStackTrace in FSUtils

2012-11-05 Thread nkeywal (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490628#comment-13490628
 ] 

nkeywal commented on HBASE-6356:


Hi Gustavo,

Yes, it would work. It's the simple option. But it's clean. I would add a 
message in the log, especially mentioning that we're ignoring the error and 
returning false.

Do you want to submit a patch?

Thanks,

 printStackTrace in FSUtils
 --

 Key: HBASE-6356
 URL: https://issues.apache.org/jira/browse/HBASE-6356
 Project: HBase
  Issue Type: Bug
  Components: Client, master, regionserver
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Trivial
  Labels: noob

 This is bad...
 {noformat}
 public boolean accept(Path p) {
   boolean isValid = false;
   try {
 if (HConstants.HBASE_NON_USER_TABLE_DIRS.contains(p.toString())) {
   isValid = false;
 } else {
 isValid = this.fs.getFileStatus(p).isDir();
 }
   } catch (IOException e) {
 e.printStackTrace();   
   }
   return isValid;
 }
   }
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7097) Log message in SecureServer.class pointing to wrong class path.


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

Y. SREENIVASULU REDDY updated HBASE-7097:
-

Attachment: HBASE-7097_94.patch

attached patch for 94 branch.

 Log message in SecureServer.class pointing to wrong class path.
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6356) printStackTrace in FSUtils

2012-11-05 Thread Gustavo Anatoly (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490644#comment-13490644
 ] 

Gustavo Anatoly commented on HBASE-6356:


Hi, nkeywal

Thanks for reply firstly. Yes, I would like to work in this task, I will work 
on a patch to submit for review, adding a message on log. 

Thanks again.

 printStackTrace in FSUtils
 --

 Key: HBASE-6356
 URL: https://issues.apache.org/jira/browse/HBASE-6356
 Project: HBase
  Issue Type: Bug
  Components: Client, master, regionserver
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Trivial
  Labels: noob

 This is bad...
 {noformat}
 public boolean accept(Path p) {
   boolean isValid = false;
   try {
 if (HConstants.HBASE_NON_USER_TABLE_DIRS.contains(p.toString())) {
   isValid = false;
 } else {
 isValid = this.fs.getFileStatus(p).isDir();
 }
   } catch (IOException e) {
 e.printStackTrace();   
   }
   return isValid;
 }
   }
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6852) SchemaMetrics.updateOnCacheHit costs too much while full scanning a table with all of its fields

2012-11-05 Thread Cheng Hao (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490649#comment-13490649
 ] 

Cheng Hao commented on HBASE-6852:
--

@Lars, thank you for the committing;
The snapshot of 0.94 branch code improves about 17.7% for scanning in my case, 
and it's sure the HBASE-6032 helps a lot; 
Here is the new hotspots for RegionServer via OProfile:

{code:title=Hotspots|borderStyle=solid}
CPU: Intel Westmere microarchitecture, speed 2.262e+06 MHz (estimated)
Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask 
of 0x00 (No unit mask) count 500
samples  %image name   symbol name
183371   17.1144  4465.jo  int 
org.apache.hadoop.hbase.KeyValue$KeyComparator.compare(byte[], int, int, 
byte[], int, int)
63267 5.9049  4465.jo  
org.apache.hadoop.hbase.regionserver.ScanQueryMatcher$MatchCode 
org.apache.hadoop.hbase.regionserver.ScanQueryMatcher.match(org.apache.hadoop.hbase.KeyValue)
59762 5.5777  4465.jo  byte[] 
org.apache.hadoop.hbase.KeyValue.createByteArray(byte[], int, int, byte[], int, 
int, byte[], int, int, long, org.apache.hadoop.hbase.KeyValue$Type, byte[], 
int, int)
50975 4.7576  4465.jo  int 
org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.blockSeek(byte[], int, 
int, boolean)
50891 4.7498  4465.jo  void 
org.apache.hadoop.hbase.regionserver.StoreFileScanner.enforceSeek()
38257 3.5706  4465.jo  jbyte_disjoint_arraycopy
37973 3.5441  4465.jo  boolean 
org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(boolean, 
org.apache.hadoop.hbase.KeyValue, boolean, boolean)~1
33978 3.1712  4465.jo  void 
org.apache.hadoop.util.PureJavaCrc32C.update(byte[], int, int)
{code}

 SchemaMetrics.updateOnCacheHit costs too much while full scanning a table 
 with all of its fields
 

 Key: HBASE-6852
 URL: https://issues.apache.org/jira/browse/HBASE-6852
 Project: HBase
  Issue Type: Improvement
  Components: metrics
Affects Versions: 0.94.0
Reporter: Cheng Hao
Assignee: Cheng Hao
Priority: Minor
  Labels: performance
 Fix For: 0.94.3

 Attachments: 6852-0.94_2.patch, 6852-0.94_3.patch, 6852-0.94.txt, 
 metrics_hotspots.png, onhitcache-trunk.patch


 The SchemaMetrics.updateOnCacheHit costs too much while I am doing the full 
 table scanning.
 Here is the top 5 hotspots within regionserver while full scanning a table: 
 (Sorry for the less-well-format)
 CPU: Intel Westmere microarchitecture, speed 2.262e+06 MHz (estimated)
 Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit 
 mask of 0x00 (No unit mask) count 500
 samples  %image name   symbol name
 ---
 9844713.4324  14033.jo void 
 org.apache.hadoop.hbase.regionserver.metrics.SchemaMetrics.updateOnCacheHit(org.apache.hadoop.hbase.io.hfile.BlockType$BlockCategory,
  boolean)
   98447100.000  14033.jo void 
 org.apache.hadoop.hbase.regionserver.metrics.SchemaMetrics.updateOnCacheHit(org.apache.hadoop.hbase.io.hfile.BlockType$BlockCategory,
  boolean) [self]
 ---
 45814 6.2510  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compareRows(byte[], int, int, 
 byte[], int, int)
   45814100.000  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compareRows(byte[], int, int, 
 byte[], int, int) [self]
 ---
 43523 5.9384  14033.jo boolean 
 org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(org.apache.hadoop.hbase.KeyValue)
   43523100.000  14033.jo boolean 
 org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(org.apache.hadoop.hbase.KeyValue)
  [self]
 ---
 42548 5.8054  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compare(byte[], int, int, 
 byte[], int, int)
   42548100.000  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compare(byte[], int, int, 
 byte[], int, int) [self]
 ---
 40572 5.5358  14033.jo int 
 org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.binarySearchNonRootIndex(byte[],
  int, int,

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class pointing to wrong class path.


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490714#comment-13490714
 ] 

Andrew Purtell commented on HBASE-7097:
---

+1, looks like a remnant of the port from Hadoop that wasn't caught on code 
review.

 Log message in SecureServer.class pointing to wrong class path.
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490741#comment-13490741
]

Andrew Purtell commented on HBASE-6721:
---

Looks like the HBASE-6721_94_2 patch contains the patch on HBASE-7042 too?

MasterExec and MasterExecResult are still in the HBASE-6721_94_2 patch, please
use Exec and ExecResult and remove MasterExec and MasterExecResult and the
change to HbaseObjectWritable.

bq. moved storage of group information from hdfs to zookeeper

Nice, this moves forward in the right direction IMHO. However, I don't see
where this information is persisted into a table. Did I miss it? Because HBase
state in ZooKeeper can be cleared by administrators in some recovery scenarios,
we can't consider it persistent storage. See how the security coprocessor
handles this.

{quote}
bq. This stuff should all be pulled out into a separate package that can be put
into a Maven module like done with security in 0.94.
Isn't that a bit too much overhead?
{quote}

The patch adds group-based assignment coprocessor specific classes to the main
Master package and the main Client package. I should clarify that I didn't say
your work must be put into a separate Maven module, but rather coprocessors are
mini-applications, and should be organized as such. It is important to keep
this set of changes, distinct optional functionality, grouped together apart
from unrelated core code. Why not {{org.apache.hadoop.hbase.client.group}} and
{{org.apache.hadoop.hbase.master.group}} etc.? I hope this feedback is clearer
now.

{quote}
bq. What changes to core code remain after that?
I've updated the patch, there should be minimal and no invasive changes.
{quote}

Thanks! Much better.

Still some possible whitepsace issues though, the patch may contain mixed tabs
and spaces? Some of the formatting looks off when I view it. If you are using
Eclipse, we have a HBase formatter in dev-support/ now that may be helpful.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490754#comment-13490754
]

Andrew Purtell commented on HBASE-6721:
---

Regarding storing the group assignment information in ZooKeeper, I think this
is a good strategy. You can optimize for the case where HBase (re)starts with
valid group assignment data available in ZK. Therefore you can avoid some
bootstrapping challenges. However, you must persist the group assignment
information into a table, like how security does with __acl__. After starting
up, if in the uncommon case there is group assignment information in the
__group__ (or similar) table that is not in sync with that in ZK (perhaps
because ZK state was cleared), you should update ZK data accordingly. From
there, there are a couple of options:
- WARN the administrator that the table assignments should be updated via
disable and enable.
- Automatically trigger reassignment via disable and enable.
- Region moves (if the assignment information is available - trunk only)

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Comment Edited] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490754#comment-13490754
]

Andrew Purtell edited comment on HBASE-6721 at 11/5/12 5:27 PM:

Regarding storing the group assignment information in ZooKeeper, I think this
is a good strategy. You can optimize for the case where HBase (re)starts with
valid group assignment data available in ZK. Therefore you can avoid some
bootstrapping challenges. However, you must persist the group assignment
information into a table, like how security does with {{_acl_}}. After starting
up, if in the uncommon case there is group assignment information in the
{{_group_}} (or similar) table that is not in sync with that in ZK (perhaps
because ZK state was cleared), you should update ZK data accordingly. From
there, there are a couple of options:
- WARN the administrator that the table assignments should be updated via
disable and enable.
- Automatically trigger reassignment via disable and enable.
- Region moves (if the assignment information is available - trunk only)

Edit: Fix incorrect use of markup.

was (Author: apurtell):
Regarding storing the group assignment information in ZooKeeper, I think
this is a good strategy. You can optimize for the case where HBase (re)starts
with valid group assignment data available in ZK. Therefore you can avoid some
bootstrapping challenges. However, you must persist the group assignment
information into a table, like how security does with __acl__. After starting
up, if in the uncommon case there is group assignment information in the
__group__ (or similar) table that is not in sync with that in ZK (perhaps
because ZK state was cleared), you should update ZK data accordingly. From
there, there are a couple of options:
- WARN the administrator that the table assignments should be updated via
disable and enable.
- Automatically trigger reassignment via disable and enable.
- Region moves (if the assignment information is available - trunk only)

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-7083) SSH#fixupDaughter should force re-assign missing daughter


[ 
https://issues.apache.org/jira/browse/HBASE-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490759#comment-13490759
 ] 

Jimmy Xiang commented on HBASE-7083:


For 0.94, forcing re-assign could cause double-assignment. This patch depends 
on other assignment manager patches, which are radical for 0.94. :)

 SSH#fixupDaughter should force re-assign missing daughter
 -

 Key: HBASE-7083
 URL: https://issues.apache.org/jira/browse/HBASE-7083
 Project: HBase
  Issue Type: Bug
  Components: Region Assignment
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
 Fix For: 0.96.0

 Attachments: trunk-7083.patch, trunk-7083.patch


 In looking into flaky test 
 TestSplitTransactionOnCluster#testShutdownSimpleFixup, I found out that a 
 missing daughter is not assigned by SSH properly.  It could be open on the 
 dead server.  We need to force re-assign it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

2012-11-05 Thread Ted Yu (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490763#comment-13490763
]

Ted Yu commented on HBASE-6721:
---

@Francis:
On https://reviews.apache.org, you can select hbase-git repository and upload
the patch for 0.94
Review board is able to generate proper diff.
{code}
+ * Copyright 2011 The Apache Software Foundation
{code}
The above line is no longer needed.

Thanks

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-7083) SSH#fixupDaughter should force re-assign missing daughter


[ 
https://issues.apache.org/jira/browse/HBASE-7083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490766#comment-13490766
 ] 

Lars Hofhansl commented on HBASE-7083:
--

Thanks Jimmy. Let's not do that for 0.94. :)

 SSH#fixupDaughter should force re-assign missing daughter
 -

 Key: HBASE-7083
 URL: https://issues.apache.org/jira/browse/HBASE-7083
 Project: HBase
  Issue Type: Bug
  Components: Region Assignment
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
 Fix For: 0.96.0

 Attachments: trunk-7083.patch, trunk-7083.patch


 In looking into flaky test 
 TestSplitTransactionOnCluster#testShutdownSimpleFixup, I found out that a 
 missing daughter is not assigned by SSH properly.  It could be open on the 
 dead server.  We need to force re-assign it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490775#comment-13490775
]

Lars Hofhansl commented on HBASE-6721:
--

Can this also colocate regions of different tables, maybe based on a key prefix?
In our case we'd tenants share tables, and each row key would be a prefixed by
a tenant id.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-6852) SchemaMetrics.updateOnCacheHit costs too much while full scanning a table with all of its fields


[ 
https://issues.apache.org/jira/browse/HBASE-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490780#comment-13490780
 ] 

Lars Hofhansl commented on HBASE-6852:
--

Thanks Cheng, this is very helpful!

 SchemaMetrics.updateOnCacheHit costs too much while full scanning a table 
 with all of its fields
 

 Key: HBASE-6852
 URL: https://issues.apache.org/jira/browse/HBASE-6852
 Project: HBase
  Issue Type: Improvement
  Components: metrics
Affects Versions: 0.94.0
Reporter: Cheng Hao
Assignee: Cheng Hao
Priority: Minor
  Labels: performance
 Fix For: 0.94.3

 Attachments: 6852-0.94_2.patch, 6852-0.94_3.patch, 6852-0.94.txt, 
 metrics_hotspots.png, onhitcache-trunk.patch


 The SchemaMetrics.updateOnCacheHit costs too much while I am doing the full 
 table scanning.
 Here is the top 5 hotspots within regionserver while full scanning a table: 
 (Sorry for the less-well-format)
 CPU: Intel Westmere microarchitecture, speed 2.262e+06 MHz (estimated)
 Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit 
 mask of 0x00 (No unit mask) count 500
 samples  %image name   symbol name
 ---
 9844713.4324  14033.jo void 
 org.apache.hadoop.hbase.regionserver.metrics.SchemaMetrics.updateOnCacheHit(org.apache.hadoop.hbase.io.hfile.BlockType$BlockCategory,
  boolean)
   98447100.000  14033.jo void 
 org.apache.hadoop.hbase.regionserver.metrics.SchemaMetrics.updateOnCacheHit(org.apache.hadoop.hbase.io.hfile.BlockType$BlockCategory,
  boolean) [self]
 ---
 45814 6.2510  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compareRows(byte[], int, int, 
 byte[], int, int)
   45814100.000  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compareRows(byte[], int, int, 
 byte[], int, int) [self]
 ---
 43523 5.9384  14033.jo boolean 
 org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(org.apache.hadoop.hbase.KeyValue)
   43523100.000  14033.jo boolean 
 org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(org.apache.hadoop.hbase.KeyValue)
  [self]
 ---
 42548 5.8054  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compare(byte[], int, int, 
 byte[], int, int)
   42548100.000  14033.jo int 
 org.apache.hadoop.hbase.KeyValue$KeyComparator.compare(byte[], int, int, 
 byte[], int, int) [self]
 ---
 40572 5.5358  14033.jo int 
 org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.binarySearchNonRootIndex(byte[],
  int, int, java.nio.ByteBuffer, org.apache.hadoop.io.RawComparator)~1
   40572100.000  14033.jo int 
 org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.binarySearchNonRootIndex(byte[],
  int, int, java.nio.ByteBuffer, org.apache.hadoop.io.RawComparator)~1 [self]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class pointing to wrong class path.


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490782#comment-13490782
 ] 

Lars Hofhansl commented on HBASE-7097:
--

+1

 Log message in SecureServer.class pointing to wrong class path.
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-5898) Consider double-checked locking for block cache lock


[ 
https://issues.apache.org/jira/browse/HBASE-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490784#comment-13490784
 ] 

Lars Hofhansl commented on HBASE-5898:
--

Gentlemen, what should we do with this? :)
I would like the next 0.94RC soon. Do we want this now, or can it wait a few 
weeks for the next RC?

 Consider double-checked locking for block cache lock
 

 Key: HBASE-5898
 URL: https://issues.apache.org/jira/browse/HBASE-5898
 Project: HBase
  Issue Type: Improvement
  Components: Performance
Affects Versions: 0.94.1
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
 Fix For: 0.94.3, 0.96.0

 Attachments: 5898-TestBlocksRead.txt, HBASE-5898-0.patch, 
 HBASE-5898-1.patch, hbase-5898.txt


 Running a workload with a high query rate against a dataset that fits in 
 cache, I saw a lot of CPU being used in IdLock.getLockEntry, being called by 
 HFileReaderV2.readBlock. Even though it was all cache hits, it was wasting a 
 lot of CPU doing lock management here. I wrote a quick patch to switch to a 
 double-checked locking and it improved throughput substantially for this 
 workload.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6317) Master clean start up and Partially enabled tables make region assignment inconsistent.


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

Lars Hofhansl updated HBASE-6317:
-

Fix Version/s: (was: 0.94.3)
   0.94.4

Moving to 0.94.4, we can pull it back if it gets done in time.

 Master clean start up and Partially enabled tables make region assignment 
 inconsistent.
 ---

 Key: HBASE-6317
 URL: https://issues.apache.org/jira/browse/HBASE-6317
 Project: HBase
  Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: rajeshbabu
 Fix For: 0.92.3, 0.96.0, 0.94.4

 Attachments: HBASE-6317_94_3.patch, HBASE-6317_94.patch, 
 HBASE-6317_trunk_2.patch, HBASE-6317_trunk_3.patch, HBASE-6317_trunk_4.patch, 
 HBASE-6317_trunk_5.patch


 If we have a  table in partially enabled state (ENABLING) then on HMaster 
 restart we treat it as a clean cluster start up and do a bulk assign.  
 Currently in 0.94 bulk assign will not handle ALREADY_OPENED scenarios and it 
 leads to region assignment problems.  Analysing more on this we found that we 
 have better way to handle these scenarios.
 {code}
 if (false == checkIfRegionBelongsToDisabled(regionInfo)
  false == checkIfRegionsBelongsToEnabling(regionInfo)) {
   synchronized (this.regions) {
 regions.put(regionInfo, regionLocation);
 addToServers(regionLocation, regionInfo);
   }
 {code}
 We dont add to regions map so that enable table handler can handle it.  But 
 as nothing is added to regions map we think it as a clean cluster start up.
 Will come up with a patch tomorrow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7009) Port HBaseCluster interface/tests to 0.94


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

Lars Hofhansl updated HBASE-7009:
-

Fix Version/s: (was: 0.94.3)
   0.94.4

Moving to 0.94.4 so I get a clean slate for the RC, please pull back if you 
commit this in time for 0.94.3.

 Port HBaseCluster interface/tests to 0.94
 -

 Key: HBASE-7009
 URL: https://issues.apache.org/jira/browse/HBASE-7009
 Project: HBase
  Issue Type: Sub-task
  Components: test
Affects Versions: 0.94.3
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.94.4

 Attachments: HBASE-7009-p1.patch, HBASE-7009.patch, 
 HBASE-7009-v2-squashed.patch


 Need to port. I am porting V5 patch from the original JIRA; I have a 
 partially ported (V3) patch from Enis with protocol buffers being reverted to 
 HRegionInterface/HMasterInterface

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

2012-11-05 Thread Ted Yu (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490800#comment-13490800
 ] 

Ted Yu commented on HBASE-6721:
---

In SecureGroupAdminEndpoint, the following code is called repeatedly:
{code}
+  private AccessController getAccessController() {
+return (AccessController)menv.getMasterServices()
+
.getCoprocessorHost().findCoprocessor(AccessController.class.getName());
+  }
{code}
Should AccessController be stored in a field variable ?
For TestSecureGroupAdminEndpoint:
{code}
+  @Test
+  public void testGetAddRemove() throws Exception {
{code}
Would testGroupGetterAdditionRemoval() be better name for the above method ?
{code}
For GroupAdmin interface:

+   * List servers that are currently being moved to a new group
+   * @return
+   * @throws IOException
+   */
+  MapString, String listServersInTransition() throws IOException;
{code}
Please describe the meaning of key and value in the returned Map.
For GroupAdminClient.java:
{code}
+  for(String server: proxy.listServersInTransition().keySet()) {
+found = found || servers.contains(server);
+  }
+  Thread.sleep(1000);
{code}
We can break out of the for loop once found becomes true, right ?
Would suggest using a shorter sleep interval above.
For DefaultLoadBalancer.java:
{code}
-  public ServerName randomAssignment(ListServerName servers) {
+  public ServerName randomAssignment(HRegionInfo region, ListServerName 
servers) {
{code}
The new parameter region is not used. We don't need to introduce this 
parameter, right ?
BTW StochasticLoadBalancer doesn't have randomAssignment().

Will provide more comments for next patch.

 RegionServer Group based Assignment
 ---

 Key: HBASE-6721
 URL: https://issues.apache.org/jira/browse/HBASE-6721
 Project: HBase
  Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch, 
 HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf


 In multi-tenant deployments of HBase, it is likely that a RegionServer will 
 be serving out regions from a number of different tables owned by various 
 client applications. Being able to group a subset of running RegionServers 
 and assign specific tables to it, provides a client application a level of 
 isolation and resource allocation.
 The proposal essentially is to have an AssignmentManager which is aware of 
 RegionServer groups and assigns tables to region servers based on groupings. 
 Load balancing will occur on a per group basis as well. 
 This is essentially a simplification of the approach taken in HBASE-4120. See 
 attached document.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7097) Log message in SecureServer.class uses wrong class name


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

Andrew Purtell updated HBASE-7097:
--

Summary: Log message in SecureServer.class uses wrong class name  (was: Log 
message in SecureServer.class pointing to wrong class path.)

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-7097) Log message in SecureServer.class uses wrong class name


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

Andrew Purtell resolved HBASE-7097.
---

  Resolution: Fixed
Hadoop Flags: Reviewed

Committed to 0.94 and 0.92 branches. Thanks for the patch. Thanks for the ack 
on 0.94 Lars.

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7092) RegionServer OOM with jdk 1.7 related to ConcurrentHashMap class loader


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

Jimmy Xiang updated HBASE-7092:
---

Attachment: heap-dump.png

 RegionServer OOM with jdk 1.7 related to ConcurrentHashMap class loader
 ---

 Key: HBASE-7092
 URL: https://issues.apache.org/jira/browse/HBASE-7092
 Project: HBase
  Issue Type: Sub-task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0

 Attachments: heap-dump.png


 One instance of java.util.concurrent.ConcurrentHashMap loaded by system 
 class loader occupies 3,972,154,848 (92.88%) bytes. The instance is 
 referenced by org.apache.hadoop.hbase.regionserver.HRegionServer @ 
 0x7038d3798 , loaded by sun.misc.Launcher$AppClassLoader @ 0x703994668. The 
 memory is accumulated in one instance of 
 java.util.concurrent.ConcurrentHashMap$Segment[] loaded by system class 
 loader.
 Keywords
 sun.misc.Launcher$AppClassLoader @ 0x703994668
 java.util.concurrent.ConcurrentHashMap
 java.util.concurrent.ConcurrentHashMap$Segment[]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7092) RegionServer OOM with jdk 1.7 related to ConcurrentHashMap class loader


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

Jimmy Xiang updated HBASE-7092:
---

Issue Type: Bug  (was: Sub-task)
Parent: (was: HBASE-6182)

 RegionServer OOM with jdk 1.7 related to ConcurrentHashMap class loader
 ---

 Key: HBASE-7092
 URL: https://issues.apache.org/jira/browse/HBASE-7092
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0

 Attachments: heap-dump.png


 One instance of java.util.concurrent.ConcurrentHashMap loaded by system 
 class loader occupies 3,972,154,848 (92.88%) bytes. The instance is 
 referenced by org.apache.hadoop.hbase.regionserver.HRegionServer @ 
 0x7038d3798 , loaded by sun.misc.Launcher$AppClassLoader @ 0x703994668. The 
 memory is accumulated in one instance of 
 java.util.concurrent.ConcurrentHashMap$Segment[] loaded by system class 
 loader.
 Keywords
 sun.misc.Launcher$AppClassLoader @ 0x703994668
 java.util.concurrent.ConcurrentHashMap
 java.util.concurrent.ConcurrentHashMap$Segment[]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7092) RegionServer OOM related to onlineregions


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

Jimmy Xiang updated HBASE-7092:
---

Summary: RegionServer OOM related to onlineregions  (was: RegionServer OOM 
with jdk 1.7 related to ConcurrentHashMap class loader)

 RegionServer OOM related to onlineregions
 -

 Key: HBASE-7092
 URL: https://issues.apache.org/jira/browse/HBASE-7092
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0

 Attachments: heap-dump.png


 One instance of java.util.concurrent.ConcurrentHashMap loaded by system 
 class loader occupies 3,972,154,848 (92.88%) bytes. The instance is 
 referenced by org.apache.hadoop.hbase.regionserver.HRegionServer @ 
 0x7038d3798 , loaded by sun.misc.Launcher$AppClassLoader @ 0x703994668. The 
 memory is accumulated in one instance of 
 java.util.concurrent.ConcurrentHashMap$Segment[] loaded by system class 
 loader.
 Keywords
 sun.misc.Launcher$AppClassLoader @ 0x703994668
 java.util.concurrent.ConcurrentHashMap
 java.util.concurrent.ConcurrentHashMap$Segment[]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7092) RegionServer OOM related to onlineregions


[ 
https://issues.apache.org/jira/browse/HBASE-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490810#comment-13490810
 ] 

Jimmy Xiang commented on HBASE-7092:


I got the same issue with jdk 1.6.  So it is not a jdk issue.  Uploaded the 
head-dump image shows it may related to onlineregions.

 RegionServer OOM related to onlineregions
 -

 Key: HBASE-7092
 URL: https://issues.apache.org/jira/browse/HBASE-7092
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.96.0

 Attachments: heap-dump.png


 One instance of java.util.concurrent.ConcurrentHashMap loaded by system 
 class loader occupies 3,972,154,848 (92.88%) bytes. The instance is 
 referenced by org.apache.hadoop.hbase.regionserver.HRegionServer @ 
 0x7038d3798 , loaded by sun.misc.Launcher$AppClassLoader @ 0x703994668. The 
 memory is accumulated in one instance of 
 java.util.concurrent.ConcurrentHashMap$Segment[] loaded by system class 
 loader.
 Keywords
 sun.misc.Launcher$AppClassLoader @ 0x703994668
 java.util.concurrent.ConcurrentHashMap
 java.util.concurrent.ConcurrentHashMap$Segment[]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7031) Support startRow/endRow in TableInputFormat

2012-11-05 Thread Phabricator (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490817#comment-13490817
 ] 

Phabricator commented on HBASE-7031:


Liyin has closed the revision [jira] [HBASE-7031] [89-fb] Add startRow/endRow 
to TableInputFormat.

CHANGED PRIOR TO COMMIT
  https://reviews.facebook.net/D6129?vs=20805id=21129#differential-review-toc

REVISION DETAIL
  https://reviews.facebook.net/D6129

COMMIT
  https://reviews.facebook.net/rHBASEEIGHTNINEFBBRANCH1405915

To: Kannan, Karthik, JIRA, mbautin, aaiyer, Liyin, pritamdamania
Cc: tjackson


 Support startRow/endRow in TableInputFormat
 ---

 Key: HBASE-7031
 URL: https://issues.apache.org/jira/browse/HBASE-7031
 Project: HBase
  Issue Type: Bug
Reporter: Mikhail Bautin
Priority: Minor
 Attachments: D6129.3.patch, D6129.4.patch


 We are still using org.apache.hadoop.hbase.mapred.TableInputFormat (as 
 opposed to org.apache.hadoop.hbase.mapreduce.TableInputFormat) for Hadoop 
 Streaming integration. We need to add startRow/endRow support to 
 TableInputFormat due to a product requirement. However, the two 
 TableInputFormat implementations have diverged over time. We need to make 
 mapred.TableInputFormat reuse some of the newer code in 
 mapreduce.TableInputFormat, and add startRow/endRow support to it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-5898) Consider double-checked locking for block cache lock

2012-11-05 Thread Jean-Daniel Cryans (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490821#comment-13490821
 ] 

Jean-Daniel Cryans commented on HBASE-5898:
---

If we want to get people testing it I say we include it right now else not at 
all for 0.94

 Consider double-checked locking for block cache lock
 

 Key: HBASE-5898
 URL: https://issues.apache.org/jira/browse/HBASE-5898
 Project: HBase
  Issue Type: Improvement
  Components: Performance
Affects Versions: 0.94.1
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
 Fix For: 0.94.3, 0.96.0

 Attachments: 5898-TestBlocksRead.txt, HBASE-5898-0.patch, 
 HBASE-5898-1.patch, hbase-5898.txt


 Running a workload with a high query rate against a dataset that fits in 
 cache, I saw a lot of CPU being used in IdLock.getLockEntry, being called by 
 HFileReaderV2.readBlock. Even though it was all cache hits, it was wasting a 
 lot of CPU doing lock management here. I wrote a quick patch to switch to a 
 double-checked locking and it improved throughput substantially for this 
 workload.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6793) Make hbase-examples module


[ 
https://issues.apache.org/jira/browse/HBASE-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490832#comment-13490832
 ] 

Sergey Shelukhin commented on HBASE-6793:
-

C++ example would require native thrift and boost to make as part of the 
mainline build. 
Rb/pl/py/php examples can be added as a test that is run, however I am not sure 
this is wise (e.g. it would require the corresponding languages w/correct 
modules for perl/correct gems for ruby/... to be installed, as well as thrift).

 Make hbase-examples module
 --

 Key: HBASE-6793
 URL: https://issues.apache.org/jira/browse/HBASE-6793
 Project: HBase
  Issue Type: Improvement
Affects Versions: 0.96.0
Reporter: Enis Soztutar
Assignee: Sergey Shelukhin
  Labels: noob
 Attachments: HBASE-6793.patch, HBASE-6793-v2.patch, 
 HBASE-6793-v3-thrift-0.9.0.patch, HBASE-6793-v4.1-squashed.patch, 
 HBASE-6793-v5-squashed.patch


 There are some examples under /examples/, which are not compiled as a part of 
 the build. We can move them to an hbase-examples module.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7092) RegionServer OOM related to onlineregions


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

Jimmy Xiang updated HBASE-7092:
---

Priority: Blocker  (was: Major)

 RegionServer OOM related to onlineregions
 -

 Key: HBASE-7092
 URL: https://issues.apache.org/jira/browse/HBASE-7092
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Blocker
 Fix For: 0.96.0

 Attachments: heap-dump.png


 One instance of java.util.concurrent.ConcurrentHashMap loaded by system 
 class loader occupies 3,972,154,848 (92.88%) bytes. The instance is 
 referenced by org.apache.hadoop.hbase.regionserver.HRegionServer @ 
 0x7038d3798 , loaded by sun.misc.Launcher$AppClassLoader @ 0x703994668. The 
 memory is accumulated in one instance of 
 java.util.concurrent.ConcurrentHashMap$Segment[] loaded by system class 
 loader.
 Keywords
 sun.misc.Launcher$AppClassLoader @ 0x703994668
 java.util.concurrent.ConcurrentHashMap
 java.util.concurrent.ConcurrentHashMap$Segment[]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4583) Integrate RWCC with Append and Increment operations

2012-11-05 Thread Varun Sharma (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490840#comment-13490840
 ] 

Varun Sharma commented on HBASE-4583:
-

I had a quick follow up question on the less radical patch - particularly when 
we have multi-column increment operation. When we apply an upsert with the 
correct MVCC read point, does upsert override the previous keyvalue ? In that 
case, is the previous keyvalue lost ?

Varun

 Integrate RWCC with Append and Increment operations
 ---

 Key: HBASE-4583
 URL: https://issues.apache.org/jira/browse/HBASE-4583
 Project: HBase
  Issue Type: Bug
Reporter: Lars Hofhansl
Assignee: Lars Hofhansl
 Fix For: 0.96.0

 Attachments: 4583-trunk-less-radical.txt, 
 4583-trunk-less-radical-v2.txt, 4583-trunk-less-radical-v3.txt, 
 4583-trunk-less-radical-v4.txt, 4583-trunk-less-radical-v5.txt, 
 4583-trunk-less-radical-v6.txt, 4583-trunk-radical.txt, 
 4583-trunk-radical_v2.txt, 4583-trunk-v3.txt, 4583.txt, 4583-v2.txt, 
 4583-v3.txt, 4583-v4.txt


 Currently Increment and Append operations do not work with RWCC and hence a 
 client could see the results of multiple such operation mixed in the same 
 Get/Scan.
 The semantics might be a bit more interesting here as upsert adds and removes 
 to and from the memstore.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-7098) Fix minor typos and formatting issues in snapshots code

Aleksandr Shulman created HBASE-7098:


 Summary: Fix minor typos and formatting issues in snapshots code
 Key: HBASE-7098
 URL: https://issues.apache.org/jira/browse/HBASE-7098
 Project: HBase
  Issue Type: Bug
  Components: snapshots
Affects Versions: 0.96.0
Reporter: Aleksandr Shulman
Assignee: Aleksandr Shulman
Priority: Minor
 Fix For: 0.96.0


There are a few minor typographical issues. I have a patch in place for these.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7098) Fix minor typos and formatting issues in snapshots code


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

Aleksandr Shulman updated HBASE-7098:
-

Attachment: HBASE-7098-v1.patch

 Fix minor typos and formatting issues in snapshots code
 ---

 Key: HBASE-7098
 URL: https://issues.apache.org/jira/browse/HBASE-7098
 Project: HBase
  Issue Type: Bug
  Components: snapshots
Affects Versions: 0.96.0
Reporter: Aleksandr Shulman
Assignee: Aleksandr Shulman
Priority: Minor
 Fix For: 0.96.0

 Attachments: HBASE-7098-v1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 There are a few minor typographical issues. I have a patch in place for these.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7098) Fix minor typos and formatting issues in HFileArchiver/HFileLink


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

Aleksandr Shulman updated HBASE-7098:
-

Summary: Fix minor typos and formatting issues in HFileArchiver/HFileLink  
(was: Fix minor typos and formatting issues in snapshots code)

 Fix minor typos and formatting issues in HFileArchiver/HFileLink
 

 Key: HBASE-7098
 URL: https://issues.apache.org/jira/browse/HBASE-7098
 Project: HBase
  Issue Type: Bug
  Components: snapshots
Affects Versions: 0.96.0
Reporter: Aleksandr Shulman
Assignee: Aleksandr Shulman
Priority: Minor
 Fix For: 0.96.0

 Attachments: HBASE-7098-v1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 There are a few minor typographical issues. I have a patch in place for these.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7098) Fix minor typos and formatting issues in HFileArchiver/HFileLink


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

Aleksandr Shulman updated HBASE-7098:
-

Status: Patch Available  (was: Open)

 Fix minor typos and formatting issues in HFileArchiver/HFileLink
 

 Key: HBASE-7098
 URL: https://issues.apache.org/jira/browse/HBASE-7098
 Project: HBase
  Issue Type: Bug
  Components: snapshots
Affects Versions: 0.96.0
Reporter: Aleksandr Shulman
Assignee: Aleksandr Shulman
Priority: Minor
 Fix For: 0.96.0

 Attachments: HBASE-7098-v1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 There are a few minor typographical issues. I have a patch in place for these.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-7092) RegionServer OOM related to onlineregions


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

Jimmy Xiang resolved HBASE-7092.


Resolution: Invalid

Found out the root cause: I have too many regions in each region server.  Each 
region allocates too much block cache.

So it is a configuration issue.  Closed as Invalid.

 RegionServer OOM related to onlineregions
 -

 Key: HBASE-7092
 URL: https://issues.apache.org/jira/browse/HBASE-7092
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Blocker
 Fix For: 0.96.0

 Attachments: heap-dump.png


 One instance of java.util.concurrent.ConcurrentHashMap loaded by system 
 class loader occupies 3,972,154,848 (92.88%) bytes. The instance is 
 referenced by org.apache.hadoop.hbase.regionserver.HRegionServer @ 
 0x7038d3798 , loaded by sun.misc.Launcher$AppClassLoader @ 0x703994668. The 
 memory is accumulated in one instance of 
 java.util.concurrent.ConcurrentHashMap$Segment[] loaded by system class 
 loader.
 Keywords
 sun.misc.Launcher$AppClassLoader @ 0x703994668
 java.util.concurrent.ConcurrentHashMap
 java.util.concurrent.ConcurrentHashMap$Segment[]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-4583) Integrate RWCC with Append and Increment operations


[ 
https://issues.apache.org/jira/browse/HBASE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490877#comment-13490877
 ] 

Lars Hofhansl commented on HBASE-4583:
--

It only replaces (it actually add a KV and then removes the old one), if it 
can prove that no scanner can (or will) see the old KV. The previous KV is lost 
(that is also what currently happens), only the radical patch will fix that.


 Integrate RWCC with Append and Increment operations
 ---

 Key: HBASE-4583
 URL: https://issues.apache.org/jira/browse/HBASE-4583
 Project: HBase
  Issue Type: Bug
Reporter: Lars Hofhansl
Assignee: Lars Hofhansl
 Fix For: 0.96.0

 Attachments: 4583-trunk-less-radical.txt, 
 4583-trunk-less-radical-v2.txt, 4583-trunk-less-radical-v3.txt, 
 4583-trunk-less-radical-v4.txt, 4583-trunk-less-radical-v5.txt, 
 4583-trunk-less-radical-v6.txt, 4583-trunk-radical.txt, 
 4583-trunk-radical_v2.txt, 4583-trunk-v3.txt, 4583.txt, 4583-v2.txt, 
 4583-v3.txt, 4583-v4.txt


 Currently Increment and Append operations do not work with RWCC and hence a 
 client could see the results of multiple such operation mixed in the same 
 Get/Scan.
 The semantics might be a bit more interesting here as upsert adds and removes 
 to and from the memstore.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-5898) Consider double-checked locking for block cache lock


[ 
https://issues.apache.org/jira/browse/HBASE-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490880#comment-13490880
 ] 

Lars Hofhansl commented on HBASE-5898:
--

Let's commit it, and add to the release notes that this potentially breaks 
off-heap caching.

 Consider double-checked locking for block cache lock
 

 Key: HBASE-5898
 URL: https://issues.apache.org/jira/browse/HBASE-5898
 Project: HBase
  Issue Type: Improvement
  Components: Performance
Affects Versions: 0.94.1
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
 Fix For: 0.94.3, 0.96.0

 Attachments: 5898-TestBlocksRead.txt, HBASE-5898-0.patch, 
 HBASE-5898-1.patch, hbase-5898.txt


 Running a workload with a high query rate against a dataset that fits in 
 cache, I saw a lot of CPU being used in IdLock.getLockEntry, being called by 
 HFileReaderV2.readBlock. Even though it was all cache hits, it was wasting a 
 lot of CPU doing lock management here. I wrote a quick patch to switch to a 
 double-checked locking and it improved throughput substantially for this 
 workload.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

2012-11-05 Thread Vandana Ayyalasomayajula (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490885#comment-13490885
]

Vandana Ayyalasomayajula commented on HBASE-6721:
-

[~ted_yu] In your previous comment, the extra parameter (HRegionInfo) is used
by the GroupBasedLoadBalancer class to determine the group information.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name

2012-11-05 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490888#comment-13490888
 ] 

Hudson commented on HBASE-7097:
---

Integrated in HBase-0.94 #574 (See 
[https://builds.apache.org/job/HBase-0.94/574/])
HBASE-7097. Log message in SecureServer.class uses wrong class name (Y. 
Sreenivasulu Reddy) (Revision 1405906)

 Result = FAILURE
apurtell : 
Files : 
* 
/hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java


 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6874) Implement prefetching for scanners

2012-11-05 Thread Karthik Ranganathan (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490898#comment-13490898
 ] 

Karthik Ranganathan commented on HBASE-6874:


Awesome, then layering in multi-pre-fetch should be very easy!

 Implement prefetching for scanners
 --

 Key: HBASE-6874
 URL: https://issues.apache.org/jira/browse/HBASE-6874
 Project: HBase
  Issue Type: Sub-task
Reporter: Karthik Ranganathan
Assignee: Karthik Ranganathan

 I did some quick experiments by scanning data that should be completely in 
 memory and found that adding pre-fetching increases the throughput by about 
 50% from 26MB/s to 39MB/s.
 The idea is to perform the next in a background thread, and keep the result 
 ready. When the scanner's next comes in, return the pre-computed result and 
 issue another background read.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7098) Fix minor typos and formatting issues in HFileArchiver/HFileLink

[
https://issues.apache.org/jira/browse/HBASE-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490908#comment-13490908
]

Hadoop QA commented on HBASE-7098:
--

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12552146/HBASE-7098-v1.patch
against trunk revision .

{color:green}+1 @author{color}. The patch does not contain any @author
tags.

{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.

{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.

{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
85 warning messages.

{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.

{color:red}-1 findbugs{color}. The patch appears to introduce 4 new
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.

{color:red}-1 core tests{color}. The patch failed these unit tests:

org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3229//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3229//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3229//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3229//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3229//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3229//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3229//console

This message is automatically generated.

Fix minor typos and formatting issues in HFileArchiver/HFileLink

Key: HBASE-7098
URL: https://issues.apache.org/jira/browse/HBASE-7098
Project: HBase
Issue Type: Bug
Components: snapshots
Affects Versions: 0.96.0
Reporter: Aleksandr Shulman
Assignee: Aleksandr Shulman
Priority: Minor
Fix For: 0.96.0

Attachments: HBASE-7098-v1.patch

Original Estimate: 1h
Remaining Estimate: 1h

There are a few minor typographical issues. I have a patch in place for these.

[jira] [Commented] (HBASE-7092) RegionServer OOM related to onlineregions


[ 
https://issues.apache.org/jira/browse/HBASE-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490915#comment-13490915
 ] 

Jimmy Xiang commented on HBASE-7092:


Actually, it is not block cache.  It is memstore buffer.

 RegionServer OOM related to onlineregions
 -

 Key: HBASE-7092
 URL: https://issues.apache.org/jira/browse/HBASE-7092
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Blocker
 Fix For: 0.96.0

 Attachments: heap-dump.png


 One instance of java.util.concurrent.ConcurrentHashMap loaded by system 
 class loader occupies 3,972,154,848 (92.88%) bytes. The instance is 
 referenced by org.apache.hadoop.hbase.regionserver.HRegionServer @ 
 0x7038d3798 , loaded by sun.misc.Launcher$AppClassLoader @ 0x703994668. The 
 memory is accumulated in one instance of 
 java.util.concurrent.ConcurrentHashMap$Segment[] loaded by system class 
 loader.
 Keywords
 sun.misc.Launcher$AppClassLoader @ 0x703994668
 java.util.concurrent.ConcurrentHashMap
 java.util.concurrent.ConcurrentHashMap$Segment[]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7009) Port HBaseCluster interface/tests to 0.94

2012-11-05 Thread Enis Soztutar (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490922#comment-13490922
 ] 

Enis Soztutar commented on HBASE-7009:
--

Let me commit this one for 0.94.3. I am testing it on an actual cluster now. 

 Port HBaseCluster interface/tests to 0.94
 -

 Key: HBASE-7009
 URL: https://issues.apache.org/jira/browse/HBASE-7009
 Project: HBase
  Issue Type: Sub-task
  Components: test
Affects Versions: 0.94.3
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.94.4

 Attachments: HBASE-7009-p1.patch, HBASE-7009.patch, 
 HBASE-7009-v2-squashed.patch


 Need to port. I am porting V5 patch from the original JIRA; I have a 
 partially ported (V3) patch from Enis with protocol buffers being reverted to 
 HRegionInterface/HMasterInterface

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6874) Implement prefetching for scanners

2012-11-05 Thread Matt Corgan (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490940#comment-13490940
 ] 

Matt Corgan commented on HBASE-6874:


Have you guys considered the possibility fetching multiple blocks in a single 
call to HDFS?  If compressed block size is 10KB, then maybe large scans should 
be requesting 100+ blocks (1MB) at a time given that rotational drives can read 
several MB in the same time they can do a seek.  The prefetch thread could chop 
the 1MB result into the individual blocks before putting them into the block 
cache.

 Implement prefetching for scanners
 --

 Key: HBASE-6874
 URL: https://issues.apache.org/jira/browse/HBASE-6874
 Project: HBase
  Issue Type: Sub-task
Reporter: Karthik Ranganathan
Assignee: Karthik Ranganathan

 I did some quick experiments by scanning data that should be completely in 
 memory and found that adding pre-fetching increases the throughput by about 
 50% from 26MB/s to 39MB/s.
 The idea is to perform the next in a background thread, and keep the result 
 ready. When the scanner's next comes in, return the pre-computed result and 
 issue another background read.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7009) Port HBaseCluster interface/tests to 0.94


[ 
https://issues.apache.org/jira/browse/HBASE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490942#comment-13490942
 ] 

Jimmy Xiang commented on HBASE-7009:


Is the patch backward compatible?  Function getClientProtocol seems to be new.

 Port HBaseCluster interface/tests to 0.94
 -

 Key: HBASE-7009
 URL: https://issues.apache.org/jira/browse/HBASE-7009
 Project: HBase
  Issue Type: Sub-task
  Components: test
Affects Versions: 0.94.3
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.94.4

 Attachments: HBASE-7009-p1.patch, HBASE-7009.patch, 
 HBASE-7009-v2-squashed.patch


 Need to port. I am porting V5 patch from the original JIRA; I have a 
 partially ported (V3) patch from Enis with protocol buffers being reverted to 
 HRegionInterface/HMasterInterface

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name

2012-11-05 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490964#comment-13490964
 ] 

Hudson commented on HBASE-7097:
---

Integrated in HBase-0.92 #604 (See 
[https://builds.apache.org/job/HBase-0.92/604/])
HBASE-7097. Log message in SecureServer.class uses wrong class name (Y. 
Sreenivasulu Reddy) (Revision 1405909)

 Result = SUCCESS
apurtell : 
Files : 
* /hbase/branches/0.92/CHANGES.txt
* 
/hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java


 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name

2012-11-05 Thread Gary Helmling (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490975#comment-13490975
 ] 

Gary Helmling commented on HBASE-7097:
--

This was unfortunately intentional, at least in the {{LOG}} instance, in order 
to provide an admittedly cludgey way to enable debug logging for the entire 
org.apache.hadoop.hbase logger without spamming region server logs with 
per-request messages -- per request metrics only get logged if you enable debug 
logging for org.apache.hadoop.ipc. It preserves the same technique that is used 
in HBaseServer.

No argument from me that the technique is ugly.  But if we actually fix the 
logger to use the correct class name, we should also change per-request logging 
to only happen at trace level instead of debug, so that existing HBase setups 
with debug level enabled for the org.apache.hadoop.hbase parent don't start 
getting noisy per-request messages.

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-6182) Make HBase works with jdk1.7


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

Jimmy Xiang resolved HBASE-6182.


Resolution: Fixed
  Assignee: Jimmy Xiang

I built a tarball with jdk1.7, deployed it to a cluster, ran ycsb.
HBase works as expected and things look good. 

 Make HBase works with jdk1.7
 

 Key: HBASE-6182
 URL: https://issues.apache.org/jira/browse/HBASE-6182
 Project: HBase
  Issue Type: Task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Critical
 Fix For: 0.96.0

 Attachments: large-tests.log, medium-tests.log


 jdk1.7 is out for a while. HBase should support it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6410) Move RegionServer Metrics to metrics2

2012-11-05 Thread Elliott Clark (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490979#comment-13490979
 ] 

Elliott Clark commented on HBASE-6410:
--

Ok, so I got a plus one from stack on the review board that I posted.  Anyone 
else have any last minute comments before I commit this?

 Move RegionServer Metrics to metrics2
 -

 Key: HBASE-6410
 URL: https://issues.apache.org/jira/browse/HBASE-6410
 Project: HBase
  Issue Type: Sub-task
  Components: metrics
Affects Versions: 0.96.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Priority: Blocker
 Attachments: HBASE-6410-13.patch, HBASE-6410-15.patch, 
 HBASE-6410-16.patch, HBASE-6410-1.patch, HBASE-6410-2.patch, 
 HBASE-6410-3.patch, HBASE-6410-4.patch, HBASE-6410-5.patch, 
 HBASE-6410-6.patch, HBASE-6410.patch


 Move RegionServer Metrics to metrics2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-7099) create compaction hooks

Adela Maznikar created HBASE-7099:
-

 Summary: create compaction hooks 
 Key: HBASE-7099
 URL: https://issues.apache.org/jira/browse/HBASE-7099
 Project: HBase
  Issue Type: New Feature
Reporter: Adela Maznikar
Assignee: Adela Maznikar


Create compaction hooks which should be used to modify the value of the KV 
during compaction. The possible modifications would include: skipping the KV, 
modifying the value of the KV in the desired format, leaving the value as it 
was.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6356) printStackTrace in FSUtils

2012-11-05 Thread Gustavo Anatoly (JIRA)


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

Gustavo Anatoly updated HBASE-6356:
---

Attachment: HBASE-6356.patch

printStackTrace refactored

 printStackTrace in FSUtils
 --

 Key: HBASE-6356
 URL: https://issues.apache.org/jira/browse/HBASE-6356
 Project: HBase
  Issue Type: Bug
  Components: Client, master, regionserver
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Trivial
  Labels: noob
 Attachments: HBASE-6356.patch


 This is bad...
 {noformat}
 public boolean accept(Path p) {
   boolean isValid = false;
   try {
 if (HConstants.HBASE_NON_USER_TABLE_DIRS.contains(p.toString())) {
   isValid = false;
 } else {
 isValid = this.fs.getFileStatus(p).isDir();
 }
   } catch (IOException e) {
 e.printStackTrace();   
   }
   return isValid;
 }
   }
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6356) printStackTrace in FSUtils

2012-11-05 Thread Gustavo Anatoly (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490996#comment-13490996
 ] 

Gustavo Anatoly commented on HBASE-6356:


Hi, nkeywal.

A patch has been uploaded to review, could verify if were that you had thought?

Thanks.

 printStackTrace in FSUtils
 --

 Key: HBASE-6356
 URL: https://issues.apache.org/jira/browse/HBASE-6356
 Project: HBase
  Issue Type: Bug
  Components: Client, master, regionserver
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Trivial
  Labels: noob
 Attachments: HBASE-6356.patch


 This is bad...
 {noformat}
 public boolean accept(Path p) {
   boolean isValid = false;
   try {
 if (HConstants.HBASE_NON_USER_TABLE_DIRS.contains(p.toString())) {
   isValid = false;
 } else {
 isValid = this.fs.getFileStatus(p).isDir();
 }
   } catch (IOException e) {
 e.printStackTrace();   
   }
   return isValid;
 }
   }
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6356) printStackTrace in FSUtils

2012-11-05 Thread nkeywal (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491008#comment-13491008
 ] 

nkeywal commented on HBASE-6356:


Hum, if I'm not wrong the exception will come only from 
this.fs.getFileStatus(p).isDir();?
So it's not in the HConstants.HBASE_NON_USER_TABLE_DIRS list?

 printStackTrace in FSUtils
 --

 Key: HBASE-6356
 URL: https://issues.apache.org/jira/browse/HBASE-6356
 Project: HBase
  Issue Type: Bug
  Components: Client, master, regionserver
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Trivial
  Labels: noob
 Attachments: HBASE-6356.patch


 This is bad...
 {noformat}
 public boolean accept(Path p) {
   boolean isValid = false;
   try {
 if (HConstants.HBASE_NON_USER_TABLE_DIRS.contains(p.toString())) {
   isValid = false;
 } else {
 isValid = this.fs.getFileStatus(p).isDir();
 }
   } catch (IOException e) {
 e.printStackTrace();   
   }
   return isValid;
 }
   }
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6894) Adding metadata to a table in the shell is both arcane and painful

[
https://issues.apache.org/jira/browse/HBASE-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491015#comment-13491015
]

Sergey Shelukhin commented on HBASE-6894:
-

Did you try v4 patch? That was the latest one and has no feedback.

Adding metadata to a table in the shell is both arcane and painful
--

Key: HBASE-6894
URL: https://issues.apache.org/jira/browse/HBASE-6894
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.96.0
Reporter: stack
Assignee: Sergey Shelukhin
Labels: noob
Attachments: HBASE-6894.patch, HBASE-6894.patch, HBASE-6894.patch,
HBASE-6894-v2.patch, HBASE-6894-v3.1-squashed.patch,
HBASE-6894-v3-squashed.patch, HBASE-6894-v4-squashed.patch

In production we have hundreds of tables w/ whack names like 'aliaserv',
'ashish_bulk', 'age_gender_topics', etc. It be grand if you could look in
master UI and see stuff like owner, eng group responsible, miscellaneous
description, etc.
Now, HTD has support for this; each carries a dictionary. Whats a PITA
though is adding attributes to the dictionary. Here is what seems to work on
trunk (though I do not trust it is doing the right thing):
{code}
hbase create 'SOME_TABLENAME', {NAME = 'd', VERSION = 1, COMPRESSION =
'LZO'}
hbase # Here is how I added metadata
hbase disable 'SOME_TABLENAME'
hbase alter 'SOME_TABLENAME', METHOD = 'table_att', OWNER = 'SOMEON',
CONFIG = {'ENVIRONMENT' = 'BLAH BLAH', 'SIZING' = 'The size should be
between 0-10K most of the time with new URLs coming in and getting removed as
they are processed unless the pipeline has fallen behind', 'MISCELLANEOUS' =
'Holds the list of URLs waiting to be processed in the parked page detection
analyzer in ingestion pipeline.'}
...
describe...
enable...
{code}
The above doesn't work in 0.94. Complains about the CONFIG, the keyword we
are using for the HTD dictionary.
It works in 0.96 though I'd have to poke around some more to ensure it is
doing the right thing.
But this METHOD = 'table_att' stuff is really ugly can we fix it?
And I can't add table attributes on table create seemingly.
A little bit of thought and a bit of ruby could clean this all up.

[jira] [Commented] (HBASE-7043) Region Server Group CLI commands


[ 
https://issues.apache.org/jira/browse/HBASE-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491018#comment-13491018
 ] 

Sergey Shelukhin commented on HBASE-7043:
-

Which is the correct v2 patch? 7043 or 6721?

 Region Server Group CLI commands
 

 Key: HBASE-7043
 URL: https://issues.apache.org/jira/browse/HBASE-7043
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-7043_94_2.patch, 
 HBASE-7043_94.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491028#comment-13491028
 ] 

Andrew Purtell commented on HBASE-7097:
---

bq. But if we actually fix the logger to use the correct class name, we should 
also change per-request logging to only happen at trace level instead of debug, 
so that existing HBase setups with debug level enabled for the 
org.apache.hadoop.hbase parent don't start getting noisy per-request messages.

+1 here, can do an addendum

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-7099) create compaction hooks


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

Andrew Purtell resolved HBASE-7099.
---

Resolution: Invalid

The existing preCompact hook allows skipping KVs and modifying the values of 
KVs.

Do this:

{code}
public preCompact(final ObserverContextRegionCoprocessorEnvironment c,
  final Store store, 
  final InternalScanner scanner)
{
  return new MyCustomInternalScanner(scanner);
}
{code}

Your custom InternalScanner therefore gets to inspect, drop, or change KVs from 
the wrapped scanner. It is your custom scanner that will be used during 
compaction.

 create compaction hooks 
 

 Key: HBASE-7099
 URL: https://issues.apache.org/jira/browse/HBASE-7099
 Project: HBase
  Issue Type: New Feature
Reporter: Adela Maznikar
Assignee: Adela Maznikar

 Create compaction hooks which should be used to modify the value of the KV 
 during compaction. The possible modifications would include: skipping the KV, 
 modifying the value of the KV in the desired format, leaving the value as it 
 was.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7099) create compaction hooks


[ 
https://issues.apache.org/jira/browse/HBASE-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491042#comment-13491042
 ] 

Adela Maznikar commented on HBASE-7099:
---

Andrew, I am working on the 89-fb branch. Sorry for the confusion, will modify 
the summary now. Thanks

 create compaction hooks 
 

 Key: HBASE-7099
 URL: https://issues.apache.org/jira/browse/HBASE-7099
 Project: HBase
  Issue Type: New Feature
Reporter: Adela Maznikar
Assignee: Adela Maznikar

 Create compaction hooks which should be used to modify the value of the KV 
 during compaction. The possible modifications would include: skipping the KV, 
 modifying the value of the KV in the desired format, leaving the value as it 
 was.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7099) [89-fb] Create compaction hooks


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

Adela Maznikar updated HBASE-7099:
--

Summary: [89-fb] Create compaction hooks   (was: create compaction hooks )

 [89-fb] Create compaction hooks 
 

 Key: HBASE-7099
 URL: https://issues.apache.org/jira/browse/HBASE-7099
 Project: HBase
  Issue Type: New Feature
Reporter: Adela Maznikar
Assignee: Adela Maznikar

 Create compaction hooks which should be used to modify the value of the KV 
 during compaction. The possible modifications would include: skipping the KV, 
 modifying the value of the KV in the desired format, leaving the value as it 
 was.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-6967) [89-fb] Introduce a hook in StoreScanner to allow aggregation of KeyValues in a single row.


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

Adela Maznikar updated HBASE-6967:
--

Summary: [89-fb] Introduce a hook in StoreScanner to allow aggregation of 
KeyValues in a single row.  (was: Introduce a hook in StoreScanner to allow 
aggregation of KeyValues in a single row.)

 [89-fb] Introduce a hook in StoreScanner to allow aggregation of KeyValues in 
 a single row.
 ---

 Key: HBASE-6967
 URL: https://issues.apache.org/jira/browse/HBASE-6967
 Project: HBase
  Issue Type: New Feature
Reporter: Adela Maznikar
Assignee: Adela Maznikar
Priority: Minor

 Introduce an interface for enabling hooks in StoreScanner

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (HBASE-7099) [89-fb] Create compaction hooks


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

Andrew Purtell reopened HBASE-7099:
---


 [89-fb] Create compaction hooks 
 

 Key: HBASE-7099
 URL: https://issues.apache.org/jira/browse/HBASE-7099
 Project: HBase
  Issue Type: New Feature
Reporter: Adela Maznikar
Assignee: Adela Maznikar

 Create compaction hooks which should be used to modify the value of the KV 
 during compaction. The possible modifications would include: skipping the KV, 
 modifying the value of the KV in the desired format, leaving the value as it 
 was.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7099) [89-fb] Create compaction hooks


[ 
https://issues.apache.org/jira/browse/HBASE-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491045#comment-13491045
 ] 

Andrew Purtell commented on HBASE-7099:
---

My apologies Adela. 

 [89-fb] Create compaction hooks 
 

 Key: HBASE-7099
 URL: https://issues.apache.org/jira/browse/HBASE-7099
 Project: HBase
  Issue Type: New Feature
Reporter: Adela Maznikar
Assignee: Adela Maznikar

 Create compaction hooks which should be used to modify the value of the KV 
 during compaction. The possible modifications would include: skipping the KV, 
 modifying the value of the KV in the desired format, leaving the value as it 
 was.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-7100) Allow multiple connections from HBaseClient to each remote endpoint

2012-11-05 Thread Karthik Ranganathan (JIRA)

Karthik Ranganathan created HBASE-7100:
--

 Summary: Allow multiple connections from HBaseClient to each 
remote endpoint
 Key: HBASE-7100
 URL: https://issues.apache.org/jira/browse/HBASE-7100
 Project: HBase
  Issue Type: Sub-task
  Components: Client
Reporter: Karthik Ranganathan
Assignee: Karthik Ranganathan


Allowing multiple connections gives a *huge* boost while benchmarking 
performance. In a production setup, many nodes query a single regionserver. But 
one connection is not enough for a single HBase client to push a single 
regionserver.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491051#comment-13491051
 ] 

Lars Hofhansl commented on HBASE-7097:
--

Maybe we should roll this back, at least for 0.94?

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491053#comment-13491053
 ] 

Andrew Purtell commented on HBASE-7097:
---

bq. Maybe we should roll this back, at least for 0.94?

And we will do it again in 6 months when it gets pointed out again and this 
detail has slipped cache again of the first wanderers by? Better to finish with 
the proposed addendum I think.

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7009) Port HBaseCluster interface/tests to 0.94


[ 
https://issues.apache.org/jira/browse/HBASE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491055#comment-13491055
 ] 

Sergey Shelukhin commented on HBASE-7009:
-

I checked, it looks like it can be removed

 Port HBaseCluster interface/tests to 0.94
 -

 Key: HBASE-7009
 URL: https://issues.apache.org/jira/browse/HBASE-7009
 Project: HBase
  Issue Type: Sub-task
  Components: test
Affects Versions: 0.94.3
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.94.4

 Attachments: HBASE-7009-p1.patch, HBASE-7009.patch, 
 HBASE-7009-v2-squashed.patch


 Need to port. I am porting V5 patch from the original JIRA; I have a 
 partially ported (V3) patch from Enis with protocol buffers being reverted to 
 HRegionInterface/HMasterInterface

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7055) port HBASE-6371 tier-based compaction from 0.89-fb to trunk


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

Sergey Shelukhin updated HBASE-7055:


Attachment: HBASE-6371-v5-refactor-only-squashed.patch

 port HBASE-6371 tier-based compaction from 0.89-fb to trunk
 ---

 Key: HBASE-7055
 URL: https://issues.apache.org/jira/browse/HBASE-7055
 Project: HBase
  Issue Type: Task
  Components: Compaction
Affects Versions: 0.96.0
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.96.0

 Attachments: HBASE-6371-squashed.patch, HBASE-6371-v2-squashed.patch, 
 HBASE-6371-v3-refactor-only-squashed.patch, 
 HBASE-6371-v4-refactor-only-squashed.patch, 
 HBASE-6371-v5-refactor-only-squashed.patch


 There's divergence in the code :(
 See HBASE-6371 for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7055) port HBASE-6371 tier-based compaction from 0.89-fb to trunk


[ 
https://issues.apache.org/jira/browse/HBASE-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491056#comment-13491056
 ] 

Sergey Shelukhin commented on HBASE-7055:
-

Added patch with rename, package move, corresponding visibility changes an a 
bit more refactoring to facilitate the latter

 port HBASE-6371 tier-based compaction from 0.89-fb to trunk
 ---

 Key: HBASE-7055
 URL: https://issues.apache.org/jira/browse/HBASE-7055
 Project: HBase
  Issue Type: Task
  Components: Compaction
Affects Versions: 0.96.0
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.96.0

 Attachments: HBASE-6371-squashed.patch, HBASE-6371-v2-squashed.patch, 
 HBASE-6371-v3-refactor-only-squashed.patch, 
 HBASE-6371-v4-refactor-only-squashed.patch, 
 HBASE-6371-v5-refactor-only-squashed.patch


 There's divergence in the code :(
 See HBASE-6371 for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (HBASE-7097) Log message in SecureServer.class uses wrong class name


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491053#comment-13491053
 ] 

Andrew Purtell edited comment on HBASE-7097 at 11/5/12 11:59 PM:
-

bq. Maybe we should roll this back, at least for 0.94?

And we will do it again in 6 months when it gets pointed out again and this 
detail has slipped cache again of the first wanderers by? Better to finish with 
the proposed addendum I think.

Edit: Either way we need an addendum, if rolling back we need a comment added 
as explanation.

  was (Author: apurtell):
bq. Maybe we should roll this back, at least for 0.94?

And we will do it again in 6 months when it gets pointed out again and this 
detail has slipped cache again of the first wanderers by? Better to finish with 
the proposed addendum I think.
  
 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (HBASE-7097) Log message in SecureServer.class uses wrong class name


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

Lars Hofhansl reopened HBASE-7097:
--


Sure... We can change the per request logging to TRACE too.

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491064#comment-13491064
 ] 

Andrew Purtell commented on HBASE-7097:
---

bq. Sure... We can change the per request logging to TRACE too.

I'll wait for a bit to see if there's more opinion, otherwise will do so.

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment


[ 
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491075#comment-13491075
 ] 

Francis Liu commented on HBASE-6721:


{quote}
Still some possible whitepsace issues though, the patch may contain mixed tabs 
and spaces? Some of the formatting looks off when I view it. If you are using 
Eclipse, we have a HBase formatter in dev-support/ now that may be helpful. 
{quote}
I'm using intellij and it doesn't seem to like the trailing whitespaces in the 
original file. I couldn't figure out a way to turn it off.

re: moving into another package - I see that sounds reasonable. Will do that 
but I will have to make some package private methods in assignment manager 
public.


 RegionServer Group based Assignment
 ---

 Key: HBASE-6721
 URL: https://issues.apache.org/jira/browse/HBASE-6721
 Project: HBase
  Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch, 
 HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf


 In multi-tenant deployments of HBase, it is likely that a RegionServer will 
 be serving out regions from a number of different tables owned by various 
 client applications. Being able to group a subset of running RegionServers 
 and assign specific tables to it, provides a client application a level of 
 isolation and resource allocation.
 The proposal essentially is to have an AssignmentManager which is aware of 
 RegionServer groups and assigns tables to region servers based on groupings. 
 Load balancing will occur on a per group basis as well. 
 This is essentially a simplification of the approach taken in HBASE-4120. See 
 attached document.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7097) Log message in SecureServer.class uses wrong class name

2012-11-05 Thread Gary Helmling (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491079#comment-13491079
 ] 

Gary Helmling commented on HBASE-7097:
--

+1 to an addendum to change the per-request logging to trace level.  Works for 
me.

 Log message in SecureServer.class uses wrong class name
 ---

 Key: HBASE-7097
 URL: https://issues.apache.org/jira/browse/HBASE-7097
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.92.2, 0.94.2
Reporter: Y. SREENIVASULU REDDY
Priority: Minor
 Fix For: 0.92.3, 0.94.3

 Attachments: HBASE-7097_94.patch


 log messages are printing wrongly in 
 org.apache.hadoop.hbase.ipc.SecureServer.class 
 {code}
 public static final Log LOG = 
 LogFactory.getLog(org.apache.hadoop.ipc.SecureServer); 
   private static final Log AUDITLOG = 
 LogFactory.getLog(SecurityLogger.org.apache.hadoop.ipc.SecureServer); 
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491081#comment-13491081
]

Francis Liu commented on HBASE-6721:

{quote}
BTW StochasticLoadBalancer doesn't have randomAssignment().
{quote}
randomAssignment is part of the original interface StochasticLoadBalancer
should have it. Also I don't see it that balancer in 0.94?

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491084#comment-13491084
]

Francis Liu commented on HBASE-6721:

{quote}
Can this also colocate regions of different tables, maybe based on a key prefix?
In our case we'd tenants share tables, and each row key would be a prefixed by
a tenant id.
{quote}
Currently it determines group membership based on a table property. We can make
things more generic and have membership determined from region metadata (ie
startKey). Would that work for you? Would each tenant become a group? Or can
multiple tenants be part of the same group?

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment


[ 
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491085#comment-13491085
 ] 

Andrew Purtell commented on HBASE-6721:
---

bq. re: moving into another package - I see that sounds reasonable. Will do 
that but I will have to make some package private methods in assignment manager 
public.

I don't see that as a problem if you could also kindly tag them with private 
interface annotations.

 RegionServer Group based Assignment
 ---

 Key: HBASE-6721
 URL: https://issues.apache.org/jira/browse/HBASE-6721
 Project: HBase
  Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
 Fix For: 0.96.0

 Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch, 
 HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf


 In multi-tenant deployments of HBase, it is likely that a RegionServer will 
 be serving out regions from a number of different tables owned by various 
 client applications. Being able to group a subset of running RegionServers 
 and assign specific tables to it, provides a client application a level of 
 isolation and resource allocation.
 The proposal essentially is to have an AssignmentManager which is aware of 
 RegionServer groups and assigns tables to region servers based on groupings. 
 Load balancing will occur on a per group basis as well. 
 This is essentially a simplification of the approach taken in HBASE-4120. See 
 attached document.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment

[
https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491093#comment-13491093
]

Lars Hofhansl commented on HBASE-6721:
--

bq. Currently it determines group membership based on a table property. We can
make things more generic and have membership determined from region metadata
(ie startKey). Would that work for you? Would each tenant become a group? Or
can multiple tenants be part of the same group?

That should work. I would need to think this through in a bit more detail.
Might be a bit tricky, since many small tenants could be in the same region, in
which case colocation might not be possible at all.

RegionServer Group based Assignment
---

Key: HBASE-6721
URL: https://issues.apache.org/jira/browse/HBASE-6721
Project: HBase
Issue Type: New Feature
Reporter: Francis Liu
Assignee: Vandana Ayyalasomayajula
Fix For: 0.96.0

Attachments: HBASE-6721_94_2.patch, HBASE-6721_94.patch,
HBASE-6721_94.patch, HBASE-6721-DesigDoc.pdf

[jira] [Commented] (HBASE-7009) Port HBaseCluster interface/tests to 0.94

2012-11-05 Thread Enis Soztutar (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491099#comment-13491099
 ] 

Enis Soztutar commented on HBASE-7009:
--

@Jimmy, are you referring to MiniHBaseCluster.getClientProtocol(). Is there any 
reason, why adding this would break BC? 

Tested the patch: 
{code}
[root@ip-10-191-190-58 hbase]# bin/hbase 
org.apache.hadoop.hbase.util.ChaosMonkey 
12/11/05 19:13:37 INFO util.ChaosMonkey: Sleeping for 17573 to add jitter
12/11/05 19:13:55 INFO util.ChaosMonkey: Performing action: Restart random 
region server
12/11/05 19:13:55 INFO util.ChaosMonkey: Killing region 
server:ip-10-72-242-62.ec2.internal,60020,1352160397949
12/11/05 19:13:55 INFO hbase.HBaseCluster: Aborting RS: 
ip-10-72-242-62.ec2.internal,60020,1352160397949
12/11/05 19:13:55 INFO hbase.ClusterManager: Executing remote command: ps aux | 
grep regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 | xargs kill -s 
SIGKILL , hostname:ip-10-72-242-62.ec2.internal
12/11/05 19:13:55 INFO hbase.ClusterManager: Executed remote command, exit 
code:0 , output:
12/11/05 19:13:55 INFO hbase.HBaseCluster: Waiting service:regionserver to 
stop: ip-10-72-242-62.ec2.internal,60020,1352160397949
12/11/05 19:13:55 INFO hbase.ClusterManager: Executing remote command: ps aux | 
grep regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 , 
hostname:ip-10-72-242-62.ec2.internal
12/11/05 19:13:55 INFO hbase.ClusterManager: Executed remote command, exit 
code:0 , output:
12/11/05 19:13:55 INFO util.ChaosMonkey: Killed region 
server:ip-10-72-242-62.ec2.internal,60020,1352160397949. Reported num of rs:2
12/11/05 19:13:55 INFO util.ChaosMonkey: Sleeping for:5000
12/11/05 19:14:00 INFO util.ChaosMonkey: Starting region 
server:ip-10-72-242-62.ec2.internal
12/11/05 19:14:00 INFO hbase.HBaseCluster: Starting RS on: 
ip-10-72-242-62.ec2.internal
12/11/05 19:14:00 INFO hbase.ClusterManager: Executing remote command: 
/root/hbase/bin/../bin/hbase-daemon.sh --config /root/hbase/bin/../conf start 
regionserver , hostname:ip-10-72-242-62.ec2.internal
12/11/05 19:14:02 INFO hbase.ClusterManager: Executed remote command, exit 
code:0 , output:starting regionserver, logging to 
/var/log/hbase/hbase-root-regionserver-ip-10-72-242-62.out

12/11/05 19:14:02 INFO util.ChaosMonkey: Started region 
server:ip-10-72-242-62.ec2.internal,60020,1352160397949. Reported num of rs:2

{code}

The only problem is when master is restarted, HConnection does not seem to pick 
up the new master:
{code}
12/11/05 19:26:00 INFO util.ChaosMonkey: Killed master 
server:ip-10-191-190-58.ec2.internal,6,1352160574752
12/11/05 19:26:00 INFO util.ChaosMonkey: Sleeping for:5000
12/11/05 19:26:05 INFO util.ChaosMonkey: Starting 
master:ip-10-191-190-58.ec2.internal
12/11/05 19:26:05 INFO hbase.HBaseCluster: Starting Master on: 
ip-10-191-190-58.ec2.internal
12/11/05 19:26:05 INFO hbase.ClusterManager: Executing remote command: 
/root/hbase/bin/../bin/hbase-daemon.sh --config /root/hbase/bin/../conf start 
master , hostname:ip-10-191-190-58.ec2.internal
12/11/05 19:26:06 INFO hbase.ClusterManager: Executed remote command, exit 
code:0 , output:starting master, logging to 
/var/log/hbase/hbase-root-master-ip-10-191-190-58.out

12/11/05 19:26:06 INFO client.HConnectionManager$HConnectionImplementation: 
Exception contacting master. Retrying...
java.io.IOException: Call to ip-10-191-190-58.ec2.internal/10.191.190.58:6 
failed on local exception: java.io.EOFException
12/11/05 19:27:06 WARN hbase.HBaseCluster: Master not started yet 
org.apache.hadoop.hbase.MasterNotRunningException
12/11/05 19:27:07 INFO util.ChaosMonkey: Started master: 
ip-10-191-190-58.ec2.internal,6,1352160574752
12/11/05 19:27:07 INFO util.ChaosMonkey: Performing action: Batch restarting 
50% of region servers
12/11/05 19:27:07 WARN util.ChaosMonkey: Exception occured during performing 
action: org.apache.hadoop.hbase.MasterNotRunningException
at 
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getMaster(HConnectionManager.java:713)
at 
org.apache.hadoop.hbase.client.HBaseAdmin.getMaster(HBaseAdmin.java:213)
at 
org.apache.hadoop.hbase.client.HBaseAdmin.getClusterStatus(HBaseAdmin.java:1632)
at 
org.apache.hadoop.hbase.DistributedHBaseCluster.getClusterStatus(DistributedHBaseCluster.java:68)
at 
org.apache.hadoop.hbase.util.ChaosMonkey$Action.getCurrentServers(ChaosMonkey.java:141)
at 
org.apache.hadoop.hbase.util.ChaosMonkey$BatchRestartRs.perform(ChaosMonkey.java:277)
at 
org.apache.hadoop.hbase.util.ChaosMonkey$PeriodicRandomActionPolicy.run(ChaosMonkey.java:393)
at java.lang.Thread.run(Thread.java:662)
{code}

Not sure whether there is a problem in the backported patch, or in 0.94.3 
itself. Investigating now. 

 Port HBaseCluster interface/tests to 0.94

[jira] [Commented] (HBASE-7009) Port HBaseCluster interface/tests to 0.94

2012-11-05 Thread Enis Soztutar (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491100#comment-13491100
 ] 

Enis Soztutar commented on HBASE-7009:
--

@Sergey, can you please make HBaseClusterManager.getExecString() public. We 
have to backport HBASE-6834 as well. 



 Port HBaseCluster interface/tests to 0.94
 -

 Key: HBASE-7009
 URL: https://issues.apache.org/jira/browse/HBASE-7009
 Project: HBase
  Issue Type: Sub-task
  Components: test
Affects Versions: 0.94.3
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.94.4

 Attachments: HBASE-7009-p1.patch, HBASE-7009.patch, 
 HBASE-7009-v2-squashed.patch


 Need to port. I am porting V5 patch from the original JIRA; I have a 
 partially ported (V3) patch from Enis with protocol buffers being reverted to 
 HRegionInterface/HMasterInterface

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7009) Port HBaseCluster interface/tests to 0.94


[ 
https://issues.apache.org/jira/browse/HBASE-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491103#comment-13491103
 ] 

Jimmy Xiang commented on HBASE-7009:


@Enis, I was just wondering if it breaks the backward compatibility. I have not 
read the patch in detail.  It sounds to me to be some new feature.  Function 
DistributedHBaseCluster#getClientProtocol and getMasterAdmin are used for 
testing only, seems to be fine?

If you are sure it's compatible with previous 0.94 release (for example 
0.94.2), old client new server, new client old server, old server and new 
server, it is fine with me.

 Port HBaseCluster interface/tests to 0.94
 -

 Key: HBASE-7009
 URL: https://issues.apache.org/jira/browse/HBASE-7009
 Project: HBase
  Issue Type: Sub-task
  Components: test
Affects Versions: 0.94.3
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.94.4

 Attachments: HBASE-7009-p1.patch, HBASE-7009.patch, 
 HBASE-7009-v2-squashed.patch


 Need to port. I am porting V5 patch from the original JIRA; I have a 
 partially ported (V3) patch from Enis with protocol buffers being reverted to 
 HRegionInterface/HMasterInterface

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HBASE-7042) Master Coprocessor Endpoint


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

Francis Liu updated HBASE-7042:
---

Attachment: HBASE-7042_94_2.patch

 Master Coprocessor Endpoint
 ---

 Key: HBASE-7042
 URL: https://issues.apache.org/jira/browse/HBASE-7042
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: HBASE-7042_94_2.patch, HBASE-7042_94.patch


 Having support for a master coprocessor endpoint would enable developers to 
 easily extended HMaster functionality/features. As is the case for region 
 server grouping.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7042) Master Coprocessor Endpoint


[ 
https://issues.apache.org/jira/browse/HBASE-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491106#comment-13491106
 ] 

Francis Liu commented on HBASE-7042:


Patch reusing Exec and ExecResult

 Master Coprocessor Endpoint
 ---

 Key: HBASE-7042
 URL: https://issues.apache.org/jira/browse/HBASE-7042
 Project: HBase
  Issue Type: Sub-task
Reporter: Francis Liu
Assignee: Francis Liu
 Fix For: 0.96.0

 Attachments: HBASE-7042_94_2.patch, HBASE-7042_94.patch


 Having support for a master coprocessor endpoint would enable developers to 
 easily extended HMaster functionality/features. As is the case for region 
 server grouping.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HBASE-7042) Master Coprocessor Endpoint