[jira] [Updated] (HBASE-9232) Fix javadoc warning and a few findbugs items.
[ https://issues.apache.org/jira/browse/HBASE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9232: - Attachment: 9232v2.txt > Fix javadoc warning and a few findbugs items. > - > > Key: HBASE-9232 > URL: https://issues.apache.org/jira/browse/HBASE-9232 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Attachments: 9232.txt, 9232v2.txt > > > Findbugs and javadoc are complaining in hadoopqa builds. Try and fix. -- 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-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Shulman resolved HBASE-9223.
--
Resolution: Cannot Reproduce
> HBase ZKCli gives error because it is looking for class removed in 0.95:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> -
>
> Key: HBASE-9223
> URL: https://issues.apache.org/jira/browse/HBASE-9223
> Project: HBase
> Issue Type: Bug
> Components: util, Zookeeper
>Affects Versions: 0.95.2
>Reporter: Aleksandr Shulman
>
> Observed behavior:
> Command: hbase zkcli
> There is an error message about a missing class:
> {code}[root@data-compat-3 hbase]# hbase zkcli
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServerArg
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
> It looks like this class is no longer in 0.95.
> ZKCli still continues in its startup and continues working (at least reads
> continue to work)
> Expected behavior:
> HBase Zkcli should not be looking for classes that are no longer part of
> HBase. This indicates an underlying issue.
--
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-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740763#comment-13740763
]
Aleksandr Shulman commented on HBASE-9223:
--
It must be something more subtle then. I've eliminated JDK6 vs. JDK7. For now,
since this works cleanly on stock 0.95.2, let's assume it's an environmental
issue somewhere on my end.
> HBase ZKCli gives error because it is looking for class removed in 0.95:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> -
>
> Key: HBASE-9223
> URL: https://issues.apache.org/jira/browse/HBASE-9223
> Project: HBase
> Issue Type: Bug
> Components: util, Zookeeper
>Affects Versions: 0.95.2
>Reporter: Aleksandr Shulman
>
> Observed behavior:
> Command: hbase zkcli
> There is an error message about a missing class:
> {code}[root@data-compat-3 hbase]# hbase zkcli
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServerArg
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
> It looks like this class is no longer in 0.95.
> ZKCli still continues in its startup and continues working (at least reads
> continue to work)
> Expected behavior:
> HBase Zkcli should not be looking for classes that are no longer part of
> HBase. This indicates an underlying issue.
--
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-9232) Fix javadoc warning and a few findbugs items.
[
https://issues.apache.org/jira/browse/HBASE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740759#comment-13740759
]
Hadoop QA commented on HBASE-9232:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598159/9232.txt
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 hadoop1.0{color}. The patch failed to compile against the
hadoop 1.0 profile.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6758//console
This message is automatically generated.
> Fix javadoc warning and a few findbugs items.
> -
>
> Key: HBASE-9232
> URL: https://issues.apache.org/jira/browse/HBASE-9232
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Attachments: 9232.txt
>
>
> Findbugs and javadoc are complaining in hadoopqa builds. Try and fix.
--
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-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740757#comment-13740757
]
stack commented on HBASE-9223:
--
{code}durruti:0.95 stack$ ./bin/hbase zkcli
Connecting to localhost:2181
2013-08-14 23:31:13,951 INFO [main] zookeeper.ZooKeeper: Client
environment:zookeeper.version=3.4.5-1392090, built on 09/30/2012 17:52 GMT
2013-08-14 23:31:13,951 INFO [main] zookeeper.ZooKeeper: Client
environment:host.name=192.168.1.129
2013-08-14 23:31:13,951 INFO [main] zookeeper.ZooKeeper: Client
environment:java.version=1.6.0_51
2013-08-14 23:31:13,951 INFO [main] zookeeper.ZooKeeper: Client
environment:java.vendor=Apple Inc.
2013-08-14 23:31:13,951 INFO [main] zookeeper.ZooKeeper: Client
environment:java.home=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
2013-08-14 23:31:13,951 INFO [main] zookeeper.ZooKeeper: Client
environment:java.class.path=/Users/stack/checkouts/0.95/bin/../conf:/Library/Java/Home/lib/tools.jar:/Users/stack/checkouts/0.95/bin/../hbase-server/target:/Users/stack/.m2/repository/asm/asm/3.1/asm-3.1.jar:/Users/stack/.m2/repository/com/github/stephenc/findbugs/findbugs-annotations/1.3.9-1/findbugs-annotations-1.3.9-1.jar:/Users/stack/.m2/repository/com/github/stephenc/high-scale-lib/high-scale-lib/1.1.1/high-scale-lib-1.1.1.jar:/Users/stack/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar:/Users/stack/.m2/repository/com/google/guava/guava/12.0.1/guava-12.0.1.jar:/Users/stack/.m2/repository/com/google/protobuf/protobuf-java/2.4.1/protobuf-java-2.4.1.jar:/Users/stack/.m2/repository/com/sun/jersey/jersey-core/1.8/jersey-core-1.8.jar:/Users/stack/.m2/repository/com/sun/jersey/jersey-json/1.8/jersey-json-1.8.jar:/Users/stack/.m2/repository/com/sun/jersey/jersey-server/1.8/jersey-server-1.8.jar:/Users/stack/.m2/repository/com/sun/xml/bind/jaxb-impl/2.2.3-1/jaxb-impl-2.2.3-1.jar:/Users/stack/.m2/repository/com/yammer/metrics/metrics-core/2.1.2/metrics-core-2.1.2.jar:/Users/stack/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar:/Users/stack/.m2/repository/commons-beanutils/commons-beanutils-core/1.8.0/commons-beanutils-core-1.8.0.jar:/Users/stack/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar:/Users/stack/.m2/repository/commons-codec/commons-codec/1.7/commons-codec-1.7.jar:/Users/stack/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar:/Users/stack/.m2/repository/commons-configuration/commons-configuration/1.6/commons-configuration-1.6.jar:/Users/stack/.m2/repository/commons-digester/commons-digester/1.8/commons-digester-1.8.jar:/Users/stack/.m2/repository/commons-el/commons-el/1.0/commons-el-1.0.jar:/Users/stack/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar:/Users/stack/.m2/repository/commons-io/commons-io/2.4/commons-io-2.4.jar:/Users/stack/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar:/Users/stack/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar:/Users/stack/.m2/repository/commons-net/commons-net/1.4.1/commons-net-1.4.1.jar:/Users/stack/.m2/repository/io/netty/netty/3.5.9.Final/netty-3.5.9.Final.jar:/Users/stack/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar:/Users/stack/.m2/repository/javax/xml/bind/jaxb-api/2.1/jaxb-api-2.1.jar:/Users/stack/.m2/repository/junit/junit/4.11/junit-4.11.jar:/Users/stack/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar:/Users/stack/.m2/repository/org/apache/commons/commons-math/2.2/commons-math-2.2.jar:/Users/stack/.m2/repository/org/apache/hadoop/hadoop-core/1.1.2/hadoop-core-1.1.2.jar:/Users/stack/checkouts/0.95/hbase-client/target/hbase-client-0.95.2-SNAPSHOT.jar:/Users/stack/checkouts/0.95/hbase-common/target/hbase-common-0.95.2-SNAPSHOT.jar:/Users/stack/checkouts/0.95/hbase-common/target/hbase-common-0.95.2-SNAPSHOT-tests.jar:/Users/stack/checkouts/0.95/hbase-hadoop-compat/target/hbase-hadoop-compat-0.95.2-SNAPSHOT.jar:/Users/stack/checkouts/0.95/hbase-hadoop-compat/target/hbase-hadoop-compat-0.95.2-SNAPSHOT-tests.jar:/Users/stack/checkouts/0.95/hbase-hadoop1-compat/target/hbase-hadoop1-compat-0.95.2-SNAPSHOT.jar:/Users/stack/checkouts/0.95/hbase-hadoop1-compat/target/hbase-hadoop1-compat-0.95.2-SNAPSHOT-tests.jar:/Users/stack/checkouts/0.95/hbase-it/target/hbase-it-0.95.2-SNAPSHOT-tests.jar:/Users/stack/checkouts/0.95/hbase-prefix-tree/target/hbase-prefix-tree-0.95.2-SNAPSHOT.jar:/Users/stack/checkouts/0.95/hbase-protocol/target/hbase-protocol-0.95.2-SNAPSHOT.jar:/Users/stack/checkouts/0.95/hbase-server/target/hbase-server-0.95.2-SNAPSHOT.jar:/Users/stack/checkouts/0.95/hbase-server/target/hbase-server-0.95.2-SNAPSHOT-tests.jar:/Users/stack/.m2/repository/org/apache/httpcomponents/httpclient/4.1.3/httpclient-4.1.3.jar:/Users/stack/.m2/repository/org/apache/httpcomponents/httpcore/4.1.3/httpcore
[jira] [Commented] (HBASE-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740756#comment-13740756
]
stack commented on HBASE-9223:
--
I do not get the ClassNotFoundException when I run it.
> HBase ZKCli gives error because it is looking for class removed in 0.95:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> -
>
> Key: HBASE-9223
> URL: https://issues.apache.org/jira/browse/HBASE-9223
> Project: HBase
> Issue Type: Bug
> Components: util, Zookeeper
>Affects Versions: 0.95.2
>Reporter: Aleksandr Shulman
>
> Observed behavior:
> Command: hbase zkcli
> There is an error message about a missing class:
> {code}[root@data-compat-3 hbase]# hbase zkcli
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServerArg
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
> It looks like this class is no longer in 0.95.
> ZKCli still continues in its startup and continues working (at least reads
> continue to work)
> Expected behavior:
> HBase Zkcli should not be looking for classes that are no longer part of
> HBase. This indicates an underlying issue.
--
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-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740751#comment-13740751
]
Aleksandr Shulman commented on HBASE-9223:
--
The tool still works. At face value, it's just a warning that comes up.
However, that warning might be indicative of other problems.
> HBase ZKCli gives error because it is looking for class removed in 0.95:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> -
>
> Key: HBASE-9223
> URL: https://issues.apache.org/jira/browse/HBASE-9223
> Project: HBase
> Issue Type: Bug
> Components: util, Zookeeper
>Affects Versions: 0.95.2
>Reporter: Aleksandr Shulman
>
> Observed behavior:
> Command: hbase zkcli
> There is an error message about a missing class:
> {code}[root@data-compat-3 hbase]# hbase zkcli
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServerArg
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
> It looks like this class is no longer in 0.95.
> ZKCli still continues in its startup and continues working (at least reads
> continue to work)
> Expected behavior:
> HBase Zkcli should not be looking for classes that are no longer part of
> HBase. This indicates an underlying issue.
--
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-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9223:
-
Fix Version/s: (was: 0.95.2)
Seems to work for me [~aleksshulman]:
{code}
$ ./bin/hbase zkcli ls2 /
{code}
or just hbase zkcli
> HBase ZKCli gives error because it is looking for class removed in 0.95:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> -
>
> Key: HBASE-9223
> URL: https://issues.apache.org/jira/browse/HBASE-9223
> Project: HBase
> Issue Type: Bug
> Components: util, Zookeeper
>Affects Versions: 0.95.2
>Reporter: Aleksandr Shulman
>
> Observed behavior:
> Command: hbase zkcli
> There is an error message about a missing class:
> {code}[root@data-compat-3 hbase]# hbase zkcli
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServerArg
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
> It looks like this class is no longer in 0.95.
> ZKCli still continues in its startup and continues working (at least reads
> continue to work)
> Expected behavior:
> HBase Zkcli should not be looking for classes that are no longer part of
> HBase. This indicates an underlying issue.
--
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-9227) RESTServer should handle the loginUser correctly
[
https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740748#comment-13740748
]
Hadoop QA commented on HBASE-9227:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598141/9227-2.txt
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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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 1
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 1 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:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6757//console
This message is automatically generated.
> RESTServer should handle the loginUser correctly
>
>
> Key: HBASE-9227
> URL: https://issues.apache.org/jira/browse/HBASE-9227
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.95.0
>Reporter: Devaraj Das
>Assignee: Devaraj Das
>Priority: Blocker
> Fix For: 0.95.2
>
> Attachments: 9227-1.txt, 9227-2.txt
>
>
> HBASE-8662 introduced a change by which the realUser in the method
> RESTServer.main() gets assigned to the loginUser only when the config
> hbase.rest.authentication.type is set to something (like "kerberos").
> I think we should set the realUser to loginUser even when the config
> hbase.rest.authentication.type is null. Without that the regular
> (non-impersonated) accesses also fail.
--
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-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740744#comment-13740744
]
Aleksandr Shulman commented on HBASE-9223:
--
Commit 90d74327e21d74386e90eb35b8b7276d5576efa0 on the 0.95 branch on June
19th, 2013 renamed oahh.zookeeper.ZooKeeperMainServerArg.java to
oahh.zookeeper.ZooKeeperMainServer.java
https://github.com/apache/hbase/commit/90d74327e21d74386e90eb35b8b7276d5576efa0
> HBase ZKCli gives error because it is looking for class removed in 0.95:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> -
>
> Key: HBASE-9223
> URL: https://issues.apache.org/jira/browse/HBASE-9223
> Project: HBase
> Issue Type: Bug
> Components: util, Zookeeper
>Affects Versions: 0.95.2
>Reporter: Aleksandr Shulman
> Fix For: 0.95.2
>
>
> Observed behavior:
> Command: hbase zkcli
> There is an error message about a missing class:
> {code}[root@data-compat-3 hbase]# hbase zkcli
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServerArg
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
> It looks like this class is no longer in 0.95.
> ZKCli still continues in its startup and continues working (at least reads
> continue to work)
> Expected behavior:
> HBase Zkcli should not be looking for classes that are no longer part of
> HBase. This indicates an underlying issue.
--
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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9225: - Resolution: Fixed Status: Resolved (was: Patch Available) Resolving. Looks integrated. > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0, 0.95.2 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9232) Fix javadoc warning and a few findbugs items.
[ https://issues.apache.org/jira/browse/HBASE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9232: - Assignee: stack Status: Patch Available (was: Open) See how this does. > Fix javadoc warning and a few findbugs items. > - > > Key: HBASE-9232 > URL: https://issues.apache.org/jira/browse/HBASE-9232 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Attachments: 9232.txt > > > Findbugs and javadoc are complaining in hadoopqa builds. Try and fix. -- 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-9232) Fix javadoc warning and a few findbugs items.
[ https://issues.apache.org/jira/browse/HBASE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9232: - Attachment: 9232.txt > Fix javadoc warning and a few findbugs items. > - > > Key: HBASE-9232 > URL: https://issues.apache.org/jira/browse/HBASE-9232 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack > Attachments: 9232.txt > > > Findbugs and javadoc are complaining in hadoopqa builds. Try and fix. -- 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-9232) Fix javadoc warning and a few findbugs items.
stack created HBASE-9232: Summary: Fix javadoc warning and a few findbugs items. Key: HBASE-9232 URL: https://issues.apache.org/jira/browse/HBASE-9232 Project: HBase Issue Type: Bug Components: test Reporter: stack Findbugs and javadoc are complaining in hadoopqa builds. Try and fix. -- 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-9231) Multipage book is generated to the wrong location
[ https://issues.apache.org/jira/browse/HBASE-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740736#comment-13740736 ] stack commented on HBASE-9231: -- [~lhofhansl] Go for it. Check the generated website. See along left tab. Can you get single page and multipage version? If so, commit. > Multipage book is generated to the wrong location > - > > Key: HBASE-9231 > URL: https://issues.apache.org/jira/browse/HBASE-9231 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.11 >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Trivial > Fix For: 0.94.12 > > Attachments: 9231.txt > > -- 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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740728#comment-13740728 ] Elliott Clark commented on HBASE-9213: -- bq.Does the hive shim work well I looked into the hive shim when I was making the compat modules. It's not really possible for us since we're creating classes that need to inherit from different class names in hadoop1/2. :-( > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9194) Break HMaster metrics into multiple contexts
[ https://issues.apache.org/jira/browse/HBASE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9194: - Attachment: HBASE-9194-3.patch > Break HMaster metrics into multiple contexts > > > Key: HBASE-9194 > URL: https://issues.apache.org/jira/browse/HBASE-9194 > Project: HBase > Issue Type: Task > Components: metrics >Affects Versions: 0.98.0, 0.95.1 >Reporter: Ted Yu >Assignee: Elliott Clark > Attachments: 9194-v1.txt, HBASE-9194-0.patch, HBASE-9194-1.patch, > HBASE-9194-2.patch, HBASE-9194-3.patch, HBASE-9194-3.patch, HBASE-9194-3.patch > > > Some metrics about the HMaster are about RPC call duration and other are > about how internal processes are running. We should make the difference > clear so that adding more of either kind doesn't confuse the user. -- 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-9193) Make what Chaos monkey actions run configurable per test.
[
https://issues.apache.org/jira/browse/HBASE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-9193:
-
Resolution: Fixed
Fix Version/s: 0.95.2
0.98.0
Release Note: It is now possible to choose which ChaosMonkey you want to
run with an integration test.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to 95 and trunk.
> Make what Chaos monkey actions run configurable per test.
> -
>
> Key: HBASE-9193
> URL: https://issues.apache.org/jira/browse/HBASE-9193
> Project: HBase
> Issue Type: Task
>Affects Versions: 0.98.0, 0.95.1
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Fix For: 0.98.0, 0.95.2
>
> Attachments: HBASE-9193-0.patch, HBASE-9193-1.patch
>
>
> Would be awesome to have every it test derive from the same base class that
> all allow setting of which ChaosMonkey.Actions to run.
> Something like:
> {code}
> hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> -Dverify.reduce.tasks=12 -DchaosMonkeyActionSet=SlowDeterministic
> loadAndVerify
> {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-9231) Multipage book is generated to the wrong location
[ https://issues.apache.org/jira/browse/HBASE-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-9231: - Priority: Trivial (was: Major) > Multipage book is generated to the wrong location > - > > Key: HBASE-9231 > URL: https://issues.apache.org/jira/browse/HBASE-9231 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.11 >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Trivial > Fix For: 0.94.12 > > Attachments: 9231.txt > > -- 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-9231) Multipage book is generated to the wrong location
[ https://issues.apache.org/jira/browse/HBASE-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-9231: - Attachment: 9231.txt Trivial change. Fixes the issue for me. Not sure if that other negative side effect. [~stack]? > Multipage book is generated to the wrong location > - > > Key: HBASE-9231 > URL: https://issues.apache.org/jira/browse/HBASE-9231 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.11 >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl > Fix For: 0.94.12 > > Attachments: 9231.txt > > -- 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-9231) Multipage book is generated to the wrong location
Lars Hofhansl created HBASE-9231: Summary: Multipage book is generated to the wrong location Key: HBASE-9231 URL: https://issues.apache.org/jira/browse/HBASE-9231 Project: HBase Issue Type: Bug Affects Versions: 0.94.11 Reporter: Lars Hofhansl Assignee: Lars Hofhansl Fix For: 0.94.12 -- 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-8960) TestDistributedLogSplitting.testLogReplayForDisablingTable fails sometimes
[
https://issues.apache.org/jira/browse/HBASE-8960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740720#comment-13740720
]
stack commented on HBASE-8960:
--
[~jeffreyz] Thanks for taking a look.
> TestDistributedLogSplitting.testLogReplayForDisablingTable fails sometimes
> --
>
> Key: HBASE-8960
> URL: https://issues.apache.org/jira/browse/HBASE-8960
> Project: HBase
> Issue Type: Task
> Components: test
>Reporter: Jimmy Xiang
>Assignee: Jeffrey Zhong
>Priority: Minor
> Fix For: 0.95.2
>
> Attachments: hbase-8960-addendum-2.patch, hbase-8960-addendum.patch,
> hbase-8960.patch
>
>
> http://54.241.6.143/job/HBase-0.95-Hadoop-2/org.apache.hbase$hbase-server/634/testReport/junit/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testLogReplayForDisablingTable/
> {noformat}
> java.lang.AssertionError: expected:<1000> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.hbase.master.TestDistributedLogSplitting.testLogReplayForDisablingTable(TestDistributedLogSplitting.java:797)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {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-9164) Convert List anti pattern to List pattern.
[ https://issues.apache.org/jira/browse/HBASE-9164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740718#comment-13740718 ] stack commented on HBASE-9164: -- So, you'd like review of v2 [~jmhsieh]? > Convert List anti pattern to List pattern. > > > Key: HBASE-9164 > URL: https://issues.apache.org/jira/browse/HBASE-9164 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.95.1 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh >Priority: Blocker > Fix For: 0.95.2 > > Attachments: hbase-9164.patch, hbase-9164.v2.patch > > > As described in HBASE-9142, using List is an anti pattern > that adds unnecessary typing and casting clutter to the code base. It would > be best to remove this before we release 0.95.2 or 0.96. -- 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-9177) Cluster UUID is not properly parsable after rewriting to PB.
[
https://issues.apache.org/jira/browse/HBASE-9177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9177:
-
Resolution: Fixed
Fix Version/s: 0.95.2
0.98.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk and 0.95. Thanks for the patch [~rajesh23]
> Cluster UUID is not properly parsable after rewriting to PB.
>
>
> Key: HBASE-9177
> URL: https://issues.apache.org/jira/browse/HBASE-9177
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.98.0, 0.95.2
>Reporter: rajeshbabu
>Assignee: rajeshbabu
> Fix For: 0.98.0, 0.95.2
>
> Attachments: HBASE-9177.patch
>
>
> I am facing this problem while testing HBASE-8348(migration).
> ->I have started two clusters with 0.94 version to replicate data from one
> cluster to other. When we have started master,writing cluster id without PB.
> -> killed both the clusters when Replication in progress
> -> running migration script to migrate hdfs and zk data to 0.96.0(No changes
> in cluster id.)
> -> starting 0.96.0 processes.
> Then not able to start region server.
> {code}
> java.io.IOException: Region server startup failed
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:2629)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:1202)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:802)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.NumberFormatException: For input string: " $411f611e
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Long.parseLong(Long.java:410)
> at java.lang.Long.valueOf(Long.java:498)
> at java.lang.Long.decode(Long.java:641)
> at java.util.UUID.fromString(UUID.java:208)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.getUUIDForCluster(ZKClusterId.java:90)
> at
> org.apache.hadoop.hbase.replication.regionserver.Replication.initialize(Replication.java:127)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.newReplicationInstance(HRegionServer.java:2248)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.createNewReplicationInstance(HRegionServer.java:2219)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.setupWALAndReplication(HRegionServer.java:1423)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:1190)
> ... 2 more
> {code}
> {code}
> try {
> clusterId = ClusterId.parseFrom(content);
> } catch (DeserializationException e) {
> throw new IOException("content=" + Bytes.toString(content), e);
> }
> // If not pb'd, make it so.
> if (!ProtobufUtil.isPBMagicPrefix(content)) rewriteAsPb(fs, rootdir,
> idPath, clusterId);
> {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-9223) HBase ZKCli gives error because it is looking for class removed in 0.95: org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
[
https://issues.apache.org/jira/browse/HBASE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740711#comment-13740711
]
stack commented on HBASE-9223:
--
dang That was a bit of useful utility. You know where we removed it
[~aleksshulman]?
> HBase ZKCli gives error because it is looking for class removed in 0.95:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> -
>
> Key: HBASE-9223
> URL: https://issues.apache.org/jira/browse/HBASE-9223
> Project: HBase
> Issue Type: Bug
> Components: util, Zookeeper
>Affects Versions: 0.95.2
>Reporter: Aleksandr Shulman
> Fix For: 0.95.2
>
>
> Observed behavior:
> Command: hbase zkcli
> There is an error message about a missing class:
> {code}[root@data-compat-3 hbase]# hbase zkcli
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServerArg
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
> It looks like this class is no longer in 0.95.
> ZKCli still continues in its startup and continues working (at least reads
> continue to work)
> Expected behavior:
> HBase Zkcli should not be looking for classes that are no longer part of
> HBase. This indicates an underlying issue.
--
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-9194) Break HMaster metrics into multiple contexts
[ https://issues.apache.org/jira/browse/HBASE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740710#comment-13740710 ] Elliott Clark commented on HBASE-9194: -- Yep re-attaching now > Break HMaster metrics into multiple contexts > > > Key: HBASE-9194 > URL: https://issues.apache.org/jira/browse/HBASE-9194 > Project: HBase > Issue Type: Task > Components: metrics >Affects Versions: 0.98.0, 0.95.1 >Reporter: Ted Yu >Assignee: Elliott Clark > Attachments: 9194-v1.txt, HBASE-9194-0.patch, HBASE-9194-1.patch, > HBASE-9194-2.patch, HBASE-9194-3.patch, HBASE-9194-3.patch > > > Some metrics about the HMaster are about RPC call duration and other are > about how internal processes are running. We should make the difference > clear so that adding more of either kind doesn't confuse the user. -- 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-9209) [0.92] TestSplitTransactionOnCluster occasionally fails
[ https://issues.apache.org/jira/browse/HBASE-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-9209. --- Resolution: Fixed Committed amendment that backports additional waits and state checks from 0.94 branch. Test passes locally through 100 repetitions and also in several EC2 builds. > [0.92] TestSplitTransactionOnCluster occasionally fails > --- > > Key: HBASE-9209 > URL: https://issues.apache.org/jira/browse/HBASE-9209 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.3 >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Minor > Fix For: 0.92.3 > > Attachments: 9209.patch, 9209.patch, 9209.patch > > > There are some issues with this test fixed in later branches. It doesn't seem > pressing to backport any of that work. Will resolve by disabling the test in > the 0.92 branch. Please indicate if you prefer an alternate approach. -- 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-9194) Break HMaster metrics into multiple contexts
[ https://issues.apache.org/jira/browse/HBASE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740708#comment-13740708 ] stack commented on HBASE-9194: -- Looks like we have an 'invisible' making an appearance. Want to rerun your patch? > Break HMaster metrics into multiple contexts > > > Key: HBASE-9194 > URL: https://issues.apache.org/jira/browse/HBASE-9194 > Project: HBase > Issue Type: Task > Components: metrics >Affects Versions: 0.98.0, 0.95.1 >Reporter: Ted Yu >Assignee: Elliott Clark > Attachments: 9194-v1.txt, HBASE-9194-0.patch, HBASE-9194-1.patch, > HBASE-9194-2.patch, HBASE-9194-3.patch, HBASE-9194-3.patch > > > Some metrics about the HMaster are about RPC call duration and other are > about how internal processes are running. We should make the difference > clear so that adding more of either kind doesn't confuse the user. -- 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-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740698#comment-13740698 ] stack commented on HBASE-9221: -- You have a patch [~jesse_yates]? > Provide interface for getting a User in the client > -- > > Key: HBASE-9221 > URL: https://issues.apache.org/jira/browse/HBASE-9221 > Project: HBase > Issue Type: Improvement > Components: Client, hadoop2, security >Affects Versions: 0.98.0, 0.95.2, 0.94.12 >Reporter: Jesse Yates >Assignee: Jesse Yates > Attachments: hbase-9221-0.94-v0.patch > > > Sometimes, users will want to provide their own User class depending on the > type of security they will support in their local environment. For instance, > running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting > the UserGroupInformation. > This issue abstracts out the mechanism by which we obtain an > o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be > extented as a Hadoop 1/2 shim as well as supporting custom authentication > 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-9193) Make what Chaos monkey actions run configurable per test.
[
https://issues.apache.org/jira/browse/HBASE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740696#comment-13740696
]
stack commented on HBASE-9193:
--
+1 if it works on your testbed. It is nice cleanup in hbase-it.
> Make what Chaos monkey actions run configurable per test.
> -
>
> Key: HBASE-9193
> URL: https://issues.apache.org/jira/browse/HBASE-9193
> Project: HBase
> Issue Type: Task
>Affects Versions: 0.98.0, 0.95.1
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-9193-0.patch, HBASE-9193-1.patch
>
>
> Would be awesome to have every it test derive from the same base class that
> all allow setting of which ChaosMonkey.Actions to run.
> Something like:
> {code}
> hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> -Dverify.reduce.tasks=12 -DchaosMonkeyActionSet=SlowDeterministic
> loadAndVerify
> {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-9193) Make what Chaos monkey actions run configurable per test.
[
https://issues.apache.org/jira/browse/HBASE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740697#comment-13740697
]
stack commented on HBASE-9193:
--
Oh, don't forget nice release note and how about a bit of doc over in reguide?
> Make what Chaos monkey actions run configurable per test.
> -
>
> Key: HBASE-9193
> URL: https://issues.apache.org/jira/browse/HBASE-9193
> Project: HBase
> Issue Type: Task
>Affects Versions: 0.98.0, 0.95.1
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-9193-0.patch, HBASE-9193-1.patch
>
>
> Would be awesome to have every it test derive from the same base class that
> all allow setting of which ChaosMonkey.Actions to run.
> Something like:
> {code}
> hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> -Dverify.reduce.tasks=12 -DchaosMonkeyActionSet=SlowDeterministic
> loadAndVerify
> {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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740695#comment-13740695 ] stack commented on HBASE-9213: -- [~sershe] A single build would be coolio. If you have ideas for how to make it work, I am all ears. Does the hive shim work well? It strikes me as a horror to keep up. Our compat modules that Elliott made are hard enough and these are just meshing APIs. We need to build tgzs and publish to maven. We need to do it for hadoop1 and hadoop2. The tgz needs to include all dependencies of which there are quiet a few when you are running on hadoop2. The dependencies are ill-specified in associated poms overly-cautious pulling in way more than is needed in the name of "just-in-case". hadoop1 and hadoop2 and their dependencies likely need to be siloed (We might do this in a subdir in a tgz). Remember also that the hadoop we ship w/ is likely moot anyways as it is unlikely to match what the user is running; user has to replace the hadoop we ship w/ the hadoop they are running. Thats the tgz. Then there is publishing to maven. When we publish to maven we say what we depend on in the associated pom we publish. The vocabulary available to you when you are doing maven publishing is limited, cryptic, broken (as best as I can discern), and there is no means of flipping a switch to say "I am currently dependent on hadoop1 (as opposed to hadoop2)" when downstream dependencies are doing their dependency pull. So, after messing w/ the maven arcane -- e.g. classifications, trying to set properties/profiles at publish and dependency fullfillment time, etc. (of note, each plugin is written by a different crew w/o enforcement of how to name the property that refers to a particular attribute so each plugin can name it as it will, and then when it comes to corner-facility such as classification, plugins may implement or not so you have 'interesting' cases such as classifications works for near all of the build pipeline but NOT for the final assembly plugin step, the plugin that makes the tgzsor the release plugin doesn't even know the name of the pom that it is supposed to be reading though you can pass it on the command line to mvn and all other plugins are fine w/ that making it so you have to tell this plugin what pom to use via gymnastics), we've ended up w/ our current hokey system where our build can be set against a target hadoop using maven profiles which works fine for local builds or builds up on the build box for unit tests etc., but it is lacking when it comes time to publish. Publishing, we need to generate two different artifacts and we denote them by adding -hadoop1 and -hadoop2 to our version. I could not make mvn do this for us so I made the script to do it working off the committed poms. On hbase-common, we could likely have a single jar that would work with both hadoop1 and hadoop2. As Elliott says, we haven't done the work (it could be just a simple hack in the script over in HBASE-8224). I've not tried it (it didn't occur to me -- it is a good idea). The prefix-tree module could likely drop the hadoop1 and hadoop2 suffix. [~roshan_naik] Yes on 1. See publish SNAPSHOTS for examples (let us know if the recent ones do not work for you -- we have heard from others that they do work as dependencies for downstreamers so we are thinking we are good here until we hear otherwise). On 2., yes... all artifacts will have the -hadoop2 and -hadoop1 appended but you probably won't have to worry because they will be pulled in for you by maven (we did some tests to ensure the right dependencies come in). Let us know if it isn't working for you. Thanks. > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740690#comment-13740690 ] Hudson commented on HBASE-9213: --- SUCCESS: Integrated in HBase-TRUNK #4393 (See [https://builds.apache.org/job/HBase-TRUNK/4393/]) HBASE-9213 Fix release warning (eclark: rev 1514140) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/HBaseHTraceConfiguration.java > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das updated HBASE-9227: --- Status: Patch Available (was: Open) I thought I had submitted the patch earlier for hadoopqa to take a look but I hadn't. Doing it now. [~jxiang], I didn't quite get what you said (in the patch v2 realUser is inlined and the variable is not really there). I have left the patch as it is. > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt, 9227-2.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9121) Update HTrace to 2.00 and add new example usage.
[ https://issues.apache.org/jira/browse/HBASE-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740677#comment-13740677 ] Hudson commented on HBASE-9121: --- SUCCESS: Integrated in hbase-0.95 #450 (See [https://builds.apache.org/job/hbase-0.95/450/]) HBASE-9121 Update HTrace to 2.00 and add new example usage. -- ADD (eclark: rev 1514130) * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java > Update HTrace to 2.00 and add new example usage. > > > Key: HBASE-9121 > URL: https://issues.apache.org/jira/browse/HBASE-9121 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.95.1 >Reporter: Elliott Clark >Assignee: Elliott Clark > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9121-0.patch, HBASE-9121-1.patch, > HBASE-9121-2.patch, HBASE-9121-PRE.patch, Zipkin Trace c49e8c79b9555d62.png > > > Update HTrace to 2.00. This adds maven modularization so the client doesn't > need all of HTraces dependencies. > Also while changing to the new api I added some new very small ammounts of > tracing around ZK and HFileReaderv2. -- 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-9229) Fix release warning
[ https://issues.apache.org/jira/browse/HBASE-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740670#comment-13740670 ] stack commented on HBASE-9229: -- +1 > Fix release warning > --- > > Key: HBASE-9229 > URL: https://issues.apache.org/jira/browse/HBASE-9229 > Project: HBase > Issue Type: Task > Components: build >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Critical > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9229-0.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] [Created] (HBASE-9230) Fix the server so you can say 'no codec' when you set up a connection and then the communication is pure pb
stack created HBASE-9230: Summary: Fix the server so you can say 'no codec' when you set up a connection and then the communication is pure pb Key: HBASE-9230 URL: https://issues.apache.org/jira/browse/HBASE-9230 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Priority: Critical Fix For: 0.96.0 Working on the asynchbase update w/ B this afternoon so it can run against 0.95/0.96, I noticed that clients HAVE TO do cellblocks as the server is currently. That is an oversight. Lets fix so can do all pb all the time too (I thought this was there but it is not); it will make it easier dev'ing simple clients. This issue shouldn't hold up release but we should get it in to help the asynchbase convertion. -- 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-9191) Update Loadbalancer method to throw HBaseIOException
[ https://issues.apache.org/jira/browse/HBASE-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9191: - Resolution: Fixed Fix Version/s: 0.98.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) That looks better. Committed to 0.95 and trunk. > Update Loadbalancer method to throw HBaseIOException > > > Key: HBASE-9191 > URL: https://issues.apache.org/jira/browse/HBASE-9191 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Francis Liu > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9191_2.patch, HBASE-9191.patch > > > Some load balancers need a way to communicate failure scenarios so the AM has > the opportunity to better handle them. -- 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-9222) Thrift DemoClient failed with error IllegalArgument(message:Row length is 0)
[
https://issues.apache.org/jira/browse/HBASE-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740666#comment-13740666
]
stack commented on HBASE-9222:
--
+1
> Thrift DemoClient failed with error IllegalArgument(message:Row length is 0)
>
>
> Key: HBASE-9222
> URL: https://issues.apache.org/jira/browse/HBASE-9222
> Project: HBase
> Issue Type: Bug
>Reporter: Jeffrey Zhong
>Assignee: Jeffrey Zhong
>Priority: Minor
> Attachments: hbase-9222.patch
>
>
> We make it illegal passing null row to Put/Delete from hbase-8101. While
> Thrift demo client still verify empty row situation as following:
> {code}
> // try empty strings
> mutations = new ArrayList();
> mutations.add(new Mutation(false, ByteBuffer.wrap(bytes("entry:")),
> ByteBuffer.wrap(bytes("")), writeToWal));
> client.mutateRow(ByteBuffer.wrap(t), ByteBuffer.wrap(bytes("")),
> mutations, dummyAttributes);
> {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-9226) Thrift host and port are hardcoded in thrift2 DemoClient.java
[ https://issues.apache.org/jira/browse/HBASE-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740664#comment-13740664 ] stack commented on HBASE-9226: -- It would probably be best to not rely on position but this is fine for now. +1 > Thrift host and port are hardcoded in thrift2 DemoClient.java > - > > Key: HBASE-9226 > URL: https://issues.apache.org/jira/browse/HBASE-9226 > Project: HBase > Issue Type: Bug >Reporter: Jeffrey Zhong >Assignee: Jeffrey Zhong >Priority: Minor > Attachments: hbase-9226.patch > > > The hard coded host of the client can only let it run on the same host as the > thrift server. -- 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-9226) Thrift host and port are hardcoded in thrift2 DemoClient.java
[
https://issues.apache.org/jira/browse/HBASE-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740662#comment-13740662
]
Hadoop QA commented on HBASE-9226:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598116/hbase-9226.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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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 1
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 1 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:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6756//console
This message is automatically generated.
> Thrift host and port are hardcoded in thrift2 DemoClient.java
> -
>
> Key: HBASE-9226
> URL: https://issues.apache.org/jira/browse/HBASE-9226
> Project: HBase
> Issue Type: Bug
>Reporter: Jeffrey Zhong
>Assignee: Jeffrey Zhong
>Priority: Minor
> Attachments: hbase-9226.patch
>
>
> The hard coded host of the client can only let it run on the same host as the
> thrift server.
--
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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740635#comment-13740635 ] Hudson commented on HBASE-9225: --- SUCCESS: Integrated in HBase-TRUNK #4392 (See [https://builds.apache.org/job/HBase-TRUNK/4392/]) HBASE-9225 Enable TRACE logging in TestReplicationBase (tedyu: rev 1514107) * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationBase.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationKillRS.java > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0, 0.95.2 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9191) Update Loadbalancer method to throw HBaseIOException
[
https://issues.apache.org/jira/browse/HBASE-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740629#comment-13740629
]
Hadoop QA commented on HBASE-9191:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598119/HBASE-9191_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 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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 1
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 1 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6754//console
This message is automatically generated.
> Update Loadbalancer method to throw HBaseIOException
>
>
> Key: HBASE-9191
> URL: https://issues.apache.org/jira/browse/HBASE-9191
> Project: HBase
> Issue Type: Sub-task
>Reporter: Francis Liu
>Assignee: Francis Liu
> Fix For: 0.95.2
>
> Attachments: HBASE-9191_2.patch, HBASE-9191.patch
>
>
> Some load balancers need a way to communicate failure scenarios so the AM has
> the opportunity to better handle them.
--
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-9222) Thrift DemoClient failed with error IllegalArgument(message:Row length is 0)
[
https://issues.apache.org/jira/browse/HBASE-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740628#comment-13740628
]
Hadoop QA commented on HBASE-9222:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598081/hbase-9222.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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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 1
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 1 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6755//console
This message is automatically generated.
> Thrift DemoClient failed with error IllegalArgument(message:Row length is 0)
>
>
> Key: HBASE-9222
> URL: https://issues.apache.org/jira/browse/HBASE-9222
> Project: HBase
> Issue Type: Bug
>Reporter: Jeffrey Zhong
>Assignee: Jeffrey Zhong
>Priority: Minor
> Attachments: hbase-9222.patch
>
>
> We make it illegal passing null row to Put/Delete from hbase-8101. While
> Thrift demo client still verify empty row situation as following:
> {code}
> // try empty strings
> mutations = new ArrayList();
> mutations.add(new Mutation(false, ByteBuffer.wrap(bytes("entry:")),
> ByteBuffer.wrap(bytes("")), writeToWal));
> client.mutateRow(ByteBuffer.wrap(t), ByteBuffer.wrap(bytes("")),
> mutations, dummyAttributes);
> {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-9229) Fix release warning
[ https://issues.apache.org/jira/browse/HBASE-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark resolved HBASE-9229. -- Resolution: Fixed > Fix release warning > --- > > Key: HBASE-9229 > URL: https://issues.apache.org/jira/browse/HBASE-9229 > Project: HBase > Issue Type: Task > Components: build >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Critical > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9229-0.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-9229) Fix release warning
[ https://issues.apache.org/jira/browse/HBASE-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9229: - Attachment: HBASE-9229-0.patch > Fix release warning > --- > > Key: HBASE-9229 > URL: https://issues.apache.org/jira/browse/HBASE-9229 > Project: HBase > Issue Type: Task > Components: build >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Critical > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9229-0.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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740614#comment-13740614 ] Jimmy Xiang commented on HBASE-9227: I prefer v2. It is better to set realUser to User.getCurrent().getUGI() only if hbase.rest.authentication.type is not null? > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt, 9227-2.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9229) Fix release warning
[ https://issues.apache.org/jira/browse/HBASE-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9229: - Fix Version/s: 0.95.2 0.98.0 > Fix release warning > --- > > Key: HBASE-9229 > URL: https://issues.apache.org/jira/browse/HBASE-9229 > Project: HBase > Issue Type: Task >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Critical > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9229-0.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-9229) Fix release warning
[ https://issues.apache.org/jira/browse/HBASE-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9229: - Affects Version/s: 0.98.0 > Fix release warning > --- > > Key: HBASE-9229 > URL: https://issues.apache.org/jira/browse/HBASE-9229 > Project: HBase > Issue Type: Task >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Critical > Attachments: HBASE-9229-0.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-9229) Fix release warning
[ https://issues.apache.org/jira/browse/HBASE-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9229: - Component/s: build > Fix release warning > --- > > Key: HBASE-9229 > URL: https://issues.apache.org/jira/browse/HBASE-9229 > Project: HBase > Issue Type: Task > Components: build >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Critical > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9229-0.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] [Created] (HBASE-9229) Fix release warning
Elliott Clark created HBASE-9229: Summary: Fix release warning Key: HBASE-9229 URL: https://issues.apache.org/jira/browse/HBASE-9229 Project: HBase Issue Type: Task Reporter: Elliott Clark Assignee: Elliott Clark Priority: Critical -- 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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740608#comment-13740608 ] Jimmy Xiang commented on HBASE-9227: +1. Thanks for the explanation. > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt, 9227-2.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das updated HBASE-9227: --- Attachment: 9227-2.txt Maybe this is a better fix. I am still debating (and digging in) between the two.. > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt, 9227-2.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9209) [0.92] TestSplitTransactionOnCluster occasionally fails
[ https://issues.apache.org/jira/browse/HBASE-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-9209: -- Attachment: 9209.patch Testing updated patch. > [0.92] TestSplitTransactionOnCluster occasionally fails > --- > > Key: HBASE-9209 > URL: https://issues.apache.org/jira/browse/HBASE-9209 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.3 >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Minor > Fix For: 0.92.3 > > Attachments: 9209.patch, 9209.patch, 9209.patch > > > There are some issues with this test fixed in later branches. It doesn't seem > pressing to backport any of that work. Will resolve by disabling the test in > the 0.92 branch. Please indicate if you prefer an alternate approach. -- 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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740589#comment-13740589 ] Devaraj Das commented on HBASE-9227: The problem is that in the RESTServer code, we call loginUserFromKeytabAndReturnUGI. This doesn't set the loginUser in the UGI. Thereafter, when the getCurrentUser would be called (which at some point would be called in the RPC client), it would try to login, but the keytabFile wouldn't be set and it the login will be as a regular user (non-keytab). This will work if someone had done a kinit outside the process prior to the first RPC invocation from the REST server. But this is not what we want.. [Note that the keytabFile would be set only when loginUserFromKeytab is called.] > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740589#comment-13740589 ] Devaraj Das edited comment on HBASE-9227 at 8/15/13 2:15 AM: - The problem is that in the RESTServer code, we call loginUserFromKeytabAndReturnUGI. This doesn't set the loginUser in the UGI. Thereafter, when the getCurrentUser would be called (which at some point would be called in the RPC client), it would try to login, but the keytabFile wouldn't be set and the login will be as a regular user (non-keytab). This will work if someone had done a kinit outside the process prior to the first RPC invocation from the REST server. But this is not what we want.. [Note that the keytabFile would be set only when loginUserFromKeytab is called.] was (Author: devaraj): The problem is that in the RESTServer code, we call loginUserFromKeytabAndReturnUGI. This doesn't set the loginUser in the UGI. Thereafter, when the getCurrentUser would be called (which at some point would be called in the RPC client), it would try to login, but the keytabFile wouldn't be set and it the login will be as a regular user (non-keytab). This will work if someone had done a kinit outside the process prior to the first RPC invocation from the REST server. But this is not what we want.. [Note that the keytabFile would be set only when loginUserFromKeytab is called.] > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740587#comment-13740587 ] Sergey Shelukhin commented on HBASE-9213: - So what's the story for this going forward? Will it be official HBase build for 0.95 and trunk for now? > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740585#comment-13740585 ] Andrew Purtell commented on HBASE-9221: --- +1 There are Hadoop JIRAs active now on refactoring UGI. One is HADOOP-9797. > Provide interface for getting a User in the client > -- > > Key: HBASE-9221 > URL: https://issues.apache.org/jira/browse/HBASE-9221 > Project: HBase > Issue Type: Improvement > Components: Client, hadoop2, security >Affects Versions: 0.98.0, 0.95.2, 0.94.12 >Reporter: Jesse Yates >Assignee: Jesse Yates > Attachments: hbase-9221-0.94-v0.patch > > > Sometimes, users will want to provide their own User class depending on the > type of security they will support in their local environment. For instance, > running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting > the UserGroupInformation. > This issue abstracts out the mechanism by which we obtain an > o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be > extented as a Hadoop 1/2 shim as well as supporting custom authentication > 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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740581#comment-13740581 ] Elliott Clark commented on HBASE-9213: -- It was a manual test by stack I think. > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740575#comment-13740575 ] Jimmy Xiang commented on HBASE-9227: For the regular secure access, why do we need to manage the connection ourselves? HBaseAdmin doesn't handle it any more? It should use the login user by default, right? > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9194) Break HMaster metrics into multiple contexts
[
https://issues.apache.org/jira/browse/HBASE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740573#comment-13740573
]
Hadoop QA commented on HBASE-9194:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598103/HBASE-9194-3.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 4 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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 1
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 1 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.TestZooKeeper.testRegionAssignmentAfterMasterRecoveryDueToZKExpiry(TestZooKeeper.java:486)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6751//console
This message is automatically generated.
> Break HMaster metrics into multiple contexts
>
>
> Key: HBASE-9194
> URL: https://issues.apache.org/jira/browse/HBASE-9194
> Project: HBase
> Issue Type: Task
> Components: metrics
>Affects Versions: 0.98.0, 0.95.1
>Reporter: Ted Yu
>Assignee: Elliott Clark
> Attachments: 9194-v1.txt, HBASE-9194-0.patch, HBASE-9194-1.patch,
> HBASE-9194-2.patch, HBASE-9194-3.patch, HBASE-9194-3.patch
>
>
> Some metrics about the HMaster are about RPC call duration and other are
> about how internal processes are running. We should make the difference
> clear so that adding more of either kind doesn't confuse the user.
--
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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740569#comment-13740569 ] Sergey Shelukhin commented on HBASE-9213: - Well, ideally we should solve that problem. Can you point at builds that produced these? I am looking at recent Apache builds e.g. https://builds.apache.org/job/hbase-0.95/448/consoleText and I still see old variants being installed e.g. bq. Installing /home/jenkins/jenkins-slave/workspace/hbase-0.95/0.95/hbase-common/target/hbase-common-0.95.2-SNAPSHOT.jar to /home/jenkins/.m2/repository/org/apache/hbase/hbase-common/0.95.2-SNAPSHOT/hbase-common-0.95.2-SNAPSHOT.jar > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9193) Make what Chaos monkey actions run configurable per test.
[
https://issues.apache.org/jira/browse/HBASE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740570#comment-13740570
]
Hadoop QA commented on HBASE-9193:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598106/HBASE-9193-1.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 161
new or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{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 1
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 1 new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6753//console
This message is automatically generated.
> Make what Chaos monkey actions run configurable per test.
> -
>
> Key: HBASE-9193
> URL: https://issues.apache.org/jira/browse/HBASE-9193
> Project: HBase
> Issue Type: Task
>Affects Versions: 0.98.0, 0.95.1
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-9193-0.patch, HBASE-9193-1.patch
>
>
> Would be awesome to have every it test derive from the same base class that
> all allow setting of which ChaosMonkey.Actions to run.
> Something like:
> {code}
> hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> -Dverify.reduce.tasks=12 -DchaosMonkeyActionSet=SlowDeterministic
> loadAndVerify
> {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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740562#comment-13740562 ] Elliott Clark commented on HBASE-9213: -- Hadoop changed some interfaces in 1.0 to classes in 2.0 (or maybe it was the other way around I never fully investigated) so the byte code produced isn't compatible. It should be possible to move all such cases into the shim layer only, but that work hasn't been done. Because of that I'm not 100% sure that the hbase-common module is hadoop version agnostic. (That seems like a problem worth solving) I believe that the problem of building both compat shims when only one is needed, has been fixed. If you look at maven now you'll see only one compat module per build. > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9224) Print out name of the method we do not support rather than throw NPE
[ https://issues.apache.org/jira/browse/HBASE-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740557#comment-13740557 ] Hudson commented on HBASE-9224: --- SUCCESS: Integrated in HBase-TRUNK #4391 (See [https://builds.apache.org/job/HBase-TRUNK/4391/]) HBASE-9224 Print out name of the method we do not support rather than throw NPE (stack: rev 1514102) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java > Print out name of the method we do not support rather than throw NPE > > > Key: HBASE-9224 > URL: https://issues.apache.org/jira/browse/HBASE-9224 > Project: HBase > Issue Type: Bug > Components: IPC/RPC >Reporter: stack >Assignee: stack > Fix For: 0.98.0, 0.95.2 > > Attachments: 9224.txt > > > If a client is trying to invoke a method we do not support, we just NPE, > rather than return an unsupported exception w/ name of the method we do not > support. Makes it hard debugging what client is doing wrong. -- 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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740561#comment-13740561 ] Hudson commented on HBASE-9225: --- FAILURE: Integrated in hbase-0.95 #449 (See [https://builds.apache.org/job/hbase-0.95/449/]) HBASE-9225 Enable TRACE logging in TestReplicationBase (tedyu: rev 1514106) * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationBase.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationKillRS.java > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0, 0.95.2 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9121) Update HTrace to 2.00 and add new example usage.
[ https://issues.apache.org/jira/browse/HBASE-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740560#comment-13740560 ] Hudson commented on HBASE-9121: --- FAILURE: Integrated in hbase-0.95 #449 (See [https://builds.apache.org/job/hbase-0.95/449/]) HBASE-9121 Update HTrace to 2.00 and add new example usage. -- Part2 (eclark: rev 1514093) * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/trace * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/trace/IntegrationTestSendTraceRequests.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/HBaseHTraceConfiguration.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/HBaseLocalFileSpanReceiver.java HBASE-9121 Update HTrace to 2.00 and add new example usage. (eclark: rev 1514092) * /hbase/branches/0.95/hbase-client/pom.xml * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncProcess.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/RecoverableZooKeeper.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java * /hbase/branches/0.95/hbase-it/pom.xml * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/mttr/IntegrationTestMTTR.java * /hbase/branches/0.95/hbase-server/pom.xml * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/executor/EventHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileReaderV2.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RequestContext.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/DisableTableHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/EnableTableHandler.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/SpanReceiverHost.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/trace/TestHTraceHooks.java * /hbase/branches/0.95/pom.xml > Update HTrace to 2.00 and add new example usage. > > > Key: HBASE-9121 > URL: https://issues.apache.org/jira/browse/HBASE-9121 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.95.1 >Reporter: Elliott Clark >Assignee: Elliott Clark > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9121-0.patch, HBASE-9121-1.patch, > HBASE-9121-2.patch, HBASE-9121-PRE.patch, Zipkin Trace c49e8c79b9555d62.png > > > Update HTrace to 2.00. This adds maven modularization so the client doesn't > need all of HTraces dependencies. > Also while changing to the new api I added some new very small ammounts of > tracing around ZK and HFileReaderv2. -- 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-9121) Update HTrace to 2.00 and add new example usage.
[ https://issues.apache.org/jira/browse/HBASE-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740558#comment-13740558 ] Hudson commented on HBASE-9121: --- SUCCESS: Integrated in HBase-TRUNK #4391 (See [https://builds.apache.org/job/HBase-TRUNK/4391/]) HBASE-9121 Update HTrace to 2.00 and add new example usage. -- Part2 (eclark: rev 1514094) * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/trace * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/trace/IntegrationTestSendTraceRequests.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/HBaseHTraceConfiguration.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/HBaseLocalFileSpanReceiver.java > Update HTrace to 2.00 and add new example usage. > > > Key: HBASE-9121 > URL: https://issues.apache.org/jira/browse/HBASE-9121 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.95.1 >Reporter: Elliott Clark >Assignee: Elliott Clark > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9121-0.patch, HBASE-9121-1.patch, > HBASE-9121-2.patch, HBASE-9121-PRE.patch, Zipkin Trace c49e8c79b9555d62.png > > > Update HTrace to 2.00. This adds maven modularization so the client doesn't > need all of HTraces dependencies. > Also while changing to the new api I added some new very small ammounts of > tracing around ZK and HFileReaderv2. -- 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-8719) Fix responseTooSlow formatting
[
https://issues.apache.org/jira/browse/HBASE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740550#comment-13740550
]
Hudson commented on HBASE-8719:
---
SUCCESS: Integrated in hbase-0.95 #448 (See
[https://builds.apache.org/job/hbase-0.95/448/])
HBASE-8719 Fix responseTooSlow formatting (jdcryans: rev 1514037)
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcCallContext.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> Fix responseTooSlow formatting
> --
>
> Key: HBASE-8719
> URL: https://issues.apache.org/jira/browse/HBASE-8719
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: Jean-Daniel Cryans
> Fix For: 0.98.0, 0.95.2
>
> Attachments: HBASE-8719.patch
>
>
> Make sure the responseTooSlow, etc., logs region at least and possibly row.
> As one well-known tall man once said:
> {code}
> I really hate this:
> org.apache.hadoop.hbase.ipc.CallerDisconnectedException: Aborting call
> next(-5472965299350279760, 101), rpc version=1, client version=29,
> methodsFingerPrint=-56040613 from 10.4.21.36:59647 after 192373 ms, since
> caller disconnected
> WHICH REGION WAS IT???
>
> 2013-06-09 01:11:03,574 WARN org.apache.hadoop.ipc.HBaseServer:
> (responseTooSlow):
> {"processingtimems":1141537,"call":"next(6527877619467313103, 101), rpc
> version=1, client version=29,
> methodsFingerPrint=-56040613","client":"10.4.21.44:41453","starttimems":1370739122036,"queuetimems":0,"class":"HRegionServer","responsesize":293994,"method":"next"}
> which region is this?
> {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] [Created] (HBASE-9228) Provide metrics for names of regions in transition
Ted Yu created HBASE-9228: - Summary: Provide metrics for names of regions in transition Key: HBASE-9228 URL: https://issues.apache.org/jira/browse/HBASE-9228 Project: HBase Issue Type: Task Reporter: Ted Yu 0.94 provides regionsInTransition metric which is an array We should provide this metric for 0.95 / trunk -- 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-8719) Fix responseTooSlow formatting
[
https://issues.apache.org/jira/browse/HBASE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740538#comment-13740538
]
Hudson commented on HBASE-8719:
---
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #676 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/676/])
HBASE-8719 Fix responseTooSlow formatting (jdcryans: rev 1514036)
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcCallContext.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> Fix responseTooSlow formatting
> --
>
> Key: HBASE-8719
> URL: https://issues.apache.org/jira/browse/HBASE-8719
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: Jean-Daniel Cryans
> Fix For: 0.98.0, 0.95.2
>
> Attachments: HBASE-8719.patch
>
>
> Make sure the responseTooSlow, etc., logs region at least and possibly row.
> As one well-known tall man once said:
> {code}
> I really hate this:
> org.apache.hadoop.hbase.ipc.CallerDisconnectedException: Aborting call
> next(-5472965299350279760, 101), rpc version=1, client version=29,
> methodsFingerPrint=-56040613 from 10.4.21.36:59647 after 192373 ms, since
> caller disconnected
> WHICH REGION WAS IT???
>
> 2013-06-09 01:11:03,574 WARN org.apache.hadoop.ipc.HBaseServer:
> (responseTooSlow):
> {"processingtimems":1141537,"call":"next(6527877619467313103, 101), rpc
> version=1, client version=29,
> methodsFingerPrint=-56040613","client":"10.4.21.44:41453","starttimems":1370739122036,"queuetimems":0,"class":"HRegionServer","responsesize":293994,"method":"next"}
> which region is this?
> {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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740539#comment-13740539 ] Sergey Shelukhin commented on HBASE-9213: - I wonder what the advantage of this model is though. You have two separate builds for what is essentially the same code, as opposed to one that can be used with both versions of Hadoop. Will hbase-common-hadoop1 work with hadoop2 if you upgrade to hadoop2 and replace the dependencies in hbase classpath? If yes this is still confusing, and an unnecessary coupling. PS: there's also https://repository.apache.org/content/groups/snapshots/org/apache/hbase/hbase-hadoop1-compat/0.95.2-hadoop2-SNAPSHOT/ > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9121) Update HTrace to 2.00 and add new example usage.
[ https://issues.apache.org/jira/browse/HBASE-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740537#comment-13740537 ] Hudson commented on HBASE-9121: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #676 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/676/]) HBASE-9121 Update HTrace to 2.00 and add new example usage. -- Part2 (eclark: rev 1514094) * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/trace * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/trace/IntegrationTestSendTraceRequests.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/HBaseHTraceConfiguration.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/HBaseLocalFileSpanReceiver.java HBASE-9121 Update HTrace to 2.00 and add new example usage. (eclark: rev 1514091) * /hbase/trunk/hbase-client/pom.xml * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncProcess.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/RecoverableZooKeeper.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java * /hbase/trunk/hbase-it/pom.xml * /hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/mttr/IntegrationTestMTTR.java * /hbase/trunk/hbase-server/pom.xml * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/executor/EventHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileReaderV2.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RequestContext.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/DisableTableHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/EnableTableHandler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/trace/SpanReceiverHost.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/trace/TestHTraceHooks.java * /hbase/trunk/pom.xml > Update HTrace to 2.00 and add new example usage. > > > Key: HBASE-9121 > URL: https://issues.apache.org/jira/browse/HBASE-9121 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.95.1 >Reporter: Elliott Clark >Assignee: Elliott Clark > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9121-0.patch, HBASE-9121-1.patch, > HBASE-9121-2.patch, HBASE-9121-PRE.patch, Zipkin Trace c49e8c79b9555d62.png > > > Update HTrace to 2.00. This adds maven modularization so the client doesn't > need all of HTraces dependencies. > Also while changing to the new api I added some new very small ammounts of > tracing around ZK and HFileReaderv2. -- 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-9227) RESTServer should handle the loginUser correctly
[ https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das updated HBASE-9227: --- Attachment: 9227-1.txt Straightforward fix. [~jxiang] mind taking a look. > RESTServer should handle the loginUser correctly > > > Key: HBASE-9227 > URL: https://issues.apache.org/jira/browse/HBASE-9227 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Blocker > Fix For: 0.95.2 > > Attachments: 9227-1.txt > > > HBASE-8662 introduced a change by which the realUser in the method > RESTServer.main() gets assigned to the loginUser only when the config > hbase.rest.authentication.type is set to something (like "kerberos"). > I think we should set the realUser to loginUser even when the config > hbase.rest.authentication.type is null. Without that the regular > (non-impersonated) accesses also fail. -- 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-9227) RESTServer should handle the loginUser correctly
Devaraj Das created HBASE-9227: -- Summary: RESTServer should handle the loginUser correctly Key: HBASE-9227 URL: https://issues.apache.org/jira/browse/HBASE-9227 Project: HBase Issue Type: Bug Affects Versions: 0.95.0 Reporter: Devaraj Das Assignee: Devaraj Das Priority: Blocker Fix For: 0.95.2 HBASE-8662 introduced a change by which the realUser in the method RESTServer.main() gets assigned to the loginUser only when the config hbase.rest.authentication.type is set to something (like "kerberos"). I think we should set the realUser to loginUser even when the config hbase.rest.authentication.type is null. Without that the regular (non-impersonated) accesses also fail. -- 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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740528#comment-13740528 ] Elliott Clark commented on HBASE-9213: -- https://repository.apache.org/content/groups/snapshots/org/apache/hbase/hbase-common/ I think that there will be two different versions of hbase-common > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9203) Secondary index support through coprocessors
[
https://issues.apache.org/jira/browse/HBASE-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740511#comment-13740511
]
Ted Yu commented on HBASE-9203:
---
First batch of comments.
{code}
+ public static boolean isIndexTable(String tableName) {
+return tableName.endsWith(INDEX_TABLE_SUFFIX);
+ }
{code}
What if some existing table(s) at customer site already uses the above suffix ?
How about using metadata in HTableDescriptor for this purpose ?
{code}
+boolean indexEnabled = this.conf.getBoolean("hbase.use.secondary.index",
false);
{code}
Please introduce constant for the above config.
Looking at changes in BaseMasterObserver.java :
{code}
+ public void preCreateTableHandler(final
ObserverContext ctx,
+ HTableDescriptor desc, HRegionInfo[] regions) throws IOException {
+ }
{code}
It would be nice if the above changes are extracted from the big patch into a
small one which adds additional hooks to coprocessor API - this way it would be
easier for the small patch to be accepted.
{code}
+ * Copyright 2011 The Apache Software Foundation
{code}
Year is not needed.
For MasterObserverExt.java:
{code}
* This is an extension for the MasterObserver interface. The APIs added into
this interface are not
+ * exposed by HBase. This is internally being used by CMWH HBase. Customer
should not make use of
+ * this interface points.
{code}
Please modify the above comment - it is not consistent with Apache HBase.
> Secondary index support through coprocessors
>
>
> Key: HBASE-9203
> URL: https://issues.apache.org/jira/browse/HBASE-9203
> Project: HBase
> Issue Type: New Feature
>Affects Versions: 0.98.0
>Reporter: rajeshbabu
>Assignee: rajeshbabu
>
> We have been working on implementing secondary index in HBase and open
> sourced on hbase 0.94.8 version.
> The project is available on github.
> https://github.com/Huawei-Hadoop/hindex
> This Jira is to support secondary index on trunk(0.98).
> Following features will be supported.
> - multiple indexes on table,
> - multi column index,
> - index based on part of a column value,
> - equals and range condition scans using index, and
> - bulk loading data to indexed table (Indexing done with bulk load)
> Most of the kernel changes needed for secondary index is available in trunk.
> Very minimal changes needed for 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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740497#comment-13740497 ] Ted Yu commented on HBASE-9225: --- Ran TestReplicationBase and TestReplicationKillRS twice with patch. They passed locally. Integrated to 0.95 and trunk. > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-9225: -- Fix Version/s: 0.95.2 Hadoop Flags: Reviewed > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0, 0.95.2 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9191) Update Loadbalancer method to throw HBaseIOException
[ https://issues.apache.org/jira/browse/HBASE-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Liu updated HBASE-9191: --- Attachment: HBASE-9191_2.patch > Update Loadbalancer method to throw HBaseIOException > > > Key: HBASE-9191 > URL: https://issues.apache.org/jira/browse/HBASE-9191 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Francis Liu > Fix For: 0.95.2 > > Attachments: HBASE-9191_2.patch, HBASE-9191.patch > > > Some load balancers need a way to communicate failure scenarios so the AM has > the opportunity to better handle them. -- 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-8760) possible loss of data in snapshot taken after region split
[
https://issues.apache.org/jira/browse/HBASE-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740496#comment-13740496
]
Hadoop QA commented on HBASE-8760:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598102/HBASE-8760-0.94-v6.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/6752//console
This message is automatically generated.
> possible loss of data in snapshot taken after region split
> --
>
> Key: HBASE-8760
> URL: https://issues.apache.org/jira/browse/HBASE-8760
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Affects Versions: 0.94.8, 0.95.1
>Reporter: Jerry He
> Fix For: 0.98.0, 0.95.2, 0.94.12
>
> Attachments: HBase-8760-0.94.8.patch, HBase-8760-0.94.8-v1.patch,
> HBASE-8760-0.94-v4.patch, HBASE-8760-0.94-v5.patch, HBASE-8760-0.94-v6.patch,
> HBASE-8760-thz-v0.patch, HBASE-8760-thz-v1.patch, HBASE-8760-thz-v2.patch,
> HBASE-8760-thz-v3.patch, HBASE-8760-v4.patch, v4-patch-testing-0.94.zip,
> v4-patch-testing-0.95.2.zip
>
>
> Right after a region split but before the daughter regions are compacted, we
> have two daughter regions containing Reference files to the parent hfiles.
> If we take snapshot right at the moment, the snapshot will succeed, but it
> will only contain the daughter Reference files. Since there is no hold on the
> parent hfiles, they will be deleted by the HFile Cleaner after they are no
> longer needed by the daughter regions soon after.
> A minimum we need to do is the keep these parent hfiles from being deleted.
--
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-9226) Thrift host and port are hardcoded in thrift2 DemoClient.java
[ https://issues.apache.org/jira/browse/HBASE-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Zhong updated HBASE-9226: - Status: Patch Available (was: Open) > Thrift host and port are hardcoded in thrift2 DemoClient.java > - > > Key: HBASE-9226 > URL: https://issues.apache.org/jira/browse/HBASE-9226 > Project: HBase > Issue Type: Bug >Reporter: Jeffrey Zhong >Assignee: Jeffrey Zhong >Priority: Minor > Attachments: hbase-9226.patch > > > The hard coded host of the client can only let it run on the same host as the > thrift server. -- 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-9222) Thrift DemoClient failed with error IllegalArgument(message:Row length is 0)
[
https://issues.apache.org/jira/browse/HBASE-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated HBASE-9222:
-
Status: Patch Available (was: Open)
> Thrift DemoClient failed with error IllegalArgument(message:Row length is 0)
>
>
> Key: HBASE-9222
> URL: https://issues.apache.org/jira/browse/HBASE-9222
> Project: HBase
> Issue Type: Bug
>Reporter: Jeffrey Zhong
>Assignee: Jeffrey Zhong
>Priority: Minor
> Attachments: hbase-9222.patch
>
>
> We make it illegal passing null row to Put/Delete from hbase-8101. While
> Thrift demo client still verify empty row situation as following:
> {code}
> // try empty strings
> mutations = new ArrayList();
> mutations.add(new Mutation(false, ByteBuffer.wrap(bytes("entry:")),
> ByteBuffer.wrap(bytes("")), writeToWal));
> client.mutateRow(ByteBuffer.wrap(t), ByteBuffer.wrap(bytes("")),
> mutations, dummyAttributes);
> {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-9226) Thrift host and port are hardcoded in thrift2 DemoClient.java
[ https://issues.apache.org/jira/browse/HBASE-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Zhong updated HBASE-9226: - Attachment: hbase-9226.patch trivial changes. > Thrift host and port are hardcoded in thrift2 DemoClient.java > - > > Key: HBASE-9226 > URL: https://issues.apache.org/jira/browse/HBASE-9226 > Project: HBase > Issue Type: Bug >Reporter: Jeffrey Zhong >Assignee: Jeffrey Zhong >Priority: Minor > Attachments: hbase-9226.patch > > > The hard coded host of the client can only let it run on the same host as the > thrift server. -- 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-9191) Update Loadbalancer method to throw HBaseIOException
[ https://issues.apache.org/jira/browse/HBASE-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740483#comment-13740483 ] Francis Liu commented on HBASE-9191: I was thinking, that it will use the old plan since we failed to get a new one. And ClosedRegionHandler will behave accordingly. Couldn't imagine that would make anything worse. Tho wrapping including the handler would be a more conservative approach. Let me do that. > Update Loadbalancer method to throw HBaseIOException > > > Key: HBASE-9191 > URL: https://issues.apache.org/jira/browse/HBASE-9191 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Francis Liu > Fix For: 0.95.2 > > Attachments: HBASE-9191.patch > > > Some load balancers need a way to communicate failure scenarios so the AM has > the opportunity to better handle them. -- 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-9195) TestFSHDFSUtils is too aggressive
[ https://issues.apache.org/jira/browse/HBASE-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740482#comment-13740482 ] Himanshu Vashishtha commented on HBASE-9195: To add more info: The interesting bit is it fails on java7 build, and has never failed on java6 (yet). This failure is hard to reproduce as I couldn't repro it on any other m/c (tried it on local/other vms on java7). Whenever it fails, it just stops printing after second iteration, and then test just times out (30 sec). The only thing it does b/w 2nd and 3rd try is to keep invoking isFileClosed after every 10ms. This made me think that it is hanging on that call. Upping the pause time is a safety measure just to reduce the number of calls. > TestFSHDFSUtils is too aggressive > - > > Key: HBASE-9195 > URL: https://issues.apache.org/jira/browse/HBASE-9195 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.95.1 >Reporter: Himanshu Vashishtha >Priority: Minor > Attachments: HBase-9195.patch, HBase-9195.patch > > > The recoverLease test in this class sets hbase.lease.recovery.pause to 10ms. > It causes that after every 10 ms, it calls isFileClosed (if it is available). > Though the test takes only 3-4 sec, but it makes about 270 isFileClosed > calls. This cause test to become somewhat flaky in our internal testing. > The proposed fix is to just to increase the pause interval to 100 ms. This > reduces the number of calls to about 30. -- 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-9226) Thrift host and port are hardcoded in thrift2 DemoClient.java
Jeffrey Zhong created HBASE-9226: Summary: Thrift host and port are hardcoded in thrift2 DemoClient.java Key: HBASE-9226 URL: https://issues.apache.org/jira/browse/HBASE-9226 Project: HBase Issue Type: Bug Reporter: Jeffrey Zhong Assignee: Jeffrey Zhong Priority: Minor The hard coded host of the client can only let it run on the same host as the thrift server. -- 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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740480#comment-13740480 ] Ted Yu commented on HBASE-9225: --- Thanks for the quick review, J-D. > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740476#comment-13740476 ] Jean-Daniel Cryans commented on HBASE-9225: --- +1 > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9213) create a unified shim for hadoop 1 and 2 so that there's one build of HBase
[ https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740475#comment-13740475 ] Roshan Naik commented on HBASE-9213: Two questions: 1) So can somebody confirm that the in Apache HBase will be publishing a separate maven artifacts like this for instance: -> hbase-common-0.9X.Y-hadoop1 & hbase-common-0.9X.Y-hadoop2 Minor detail...I am not certain if '-hadoop1' and '-hadoop2' will preced the version number or follow it in the above naming convention. 2) If the above is true, is there going to be an additional third artifact also going to be published of the form : -> hbase-common-0.9X.Y > create a unified shim for hadoop 1 and 2 so that there's one build of HBase > --- > > Key: HBASE-9213 > URL: https://issues.apache.org/jira/browse/HBASE-9213 > Project: HBase > Issue Type: Brainstorming > Components: build >Reporter: Sergey Shelukhin > Fix For: 0.96.0 > > > This is a brainstorming JIRA. Working with HBase dependency at this point > seems to be rather painful from what I hear from other folks. We could do the > hive model with unified shim, built in such manner that it can work with > either version, where at build time dependencies for all 2-3 versions are > pulled and the appropriate one is used for tests, and when running HBase you > have to point at Hadoop directory to get the dependencies. I am not very > proficient at maven so not quite certain of the best solution yet. -- 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-9217) TestReplicationSmallTests#testDisableEnable fails intermittently
[
https://issues.apache.org/jira/browse/HBASE-9217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740472#comment-13740472
]
Ted Yu commented on HBASE-9217:
---
Logged HBASE-9225 for LOG level change.
> TestReplicationSmallTests#testDisableEnable fails intermittently
>
>
> Key: HBASE-9217
> URL: https://issues.apache.org/jira/browse/HBASE-9217
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 9217-v1.txt, 9217-v2.txt, 9217-v3.txt,
> testDisableEnable.txt
>
>
> From
> https://builds.apache.org/job/HBase-0.95/444/testReport/junit/org.apache.hadoop.hbase.replication/TestReplicationSmallTests/testDisableEnable/
> :
> {code}
> java.lang.AssertionError: Waited too much time for put replication
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.hadoop.hbase.replication.TestReplicationSmallTests.testDisableEnable(TestReplicationSmallTests.java:313)
> ...
> 2013-08-14 08:06:47,228 DEBUG
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> wal.ProtobufLogReader(118): After reading the trailer: walEditsStopOffset: 0,
> fileLength: 0, trailerPresent: false
> 2013-08-14 08:06:47,228 WARN
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> regionserver.ReplicationSource(301): 2 Got:
> java.io.IOException: Cannot seek after EOF
> at
> org.apache.hadoop.hdfs.DFSClient$DFSInputStream.seek(DFSClient.java:2593)
> at
> org.apache.hadoop.fs.FSDataInputStream.seek(FSDataInputStream.java:37)
> at
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.seekOnFs(ProtobufLogReader.java:275)
> at
> org.apache.hadoop.hbase.regionserver.wal.ReaderBase.seek(ReaderBase.java:115)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogReaderManager.seek(ReplicationHLogReaderManager.java:108)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.readAllEntriesToReplicateOrNextFile(ReplicationSource.java:388)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:297)
> 2013-08-14 08:06:47,228 DEBUG
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> regionserver.ReplicationSource(578): Nothing to replicate, sleeping 100 times
> 1
> 2013-08-14 08:06:47,329 DEBUG
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> fs.HFileSystem$ReorderWALBlocks(327):
> /user/jenkins/hbase/WALs/vesta.apache.org,39079,1376467506138/vesta.apache.org%2C39079%2C1376467506138.1376467603252
> is an HLog file, so reordering blocks, last hostname will be:vesta.apache.org
> {code}
> Looking at test output from successful builds, I didn't see the above
> exception.
--
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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-9225: -- Attachment: 9225-v1.txt Patch v3 from HBASE-9217 > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9225) Enable TRACE logging in TestReplicationBase
[ https://issues.apache.org/jira/browse/HBASE-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-9225: -- Fix Version/s: 0.98.0 Status: Patch Available (was: Open) > Enable TRACE logging in TestReplicationBase > --- > > Key: HBASE-9225 > URL: https://issues.apache.org/jira/browse/HBASE-9225 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0 > > Attachments: 9225-v1.txt > > > During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' > was found in one run of TestReplicationSmallTests#testDisableEnable, J-D > suggested that we enable TRACE level logging in TestReplicationBase so that > we can have better clue as to the cause when this IOE happens again. -- 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-9225) Enable TRACE logging in TestReplicationBase
Ted Yu created HBASE-9225: - Summary: Enable TRACE logging in TestReplicationBase Key: HBASE-9225 URL: https://issues.apache.org/jira/browse/HBASE-9225 Project: HBase Issue Type: Test Reporter: Ted Yu Assignee: Ted Yu During discussion on HBASE-9217 where 'IOException: Cannot seek after EOF' was found in one run of TestReplicationSmallTests#testDisableEnable, J-D suggested that we enable TRACE level logging in TestReplicationBase so that we can have better clue as to the cause when this IOE happens again. -- 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-9217) TestReplicationSmallTests#testDisableEnable fails intermittently
[
https://issues.apache.org/jira/browse/HBASE-9217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740469#comment-13740469
]
Jean-Daniel Cryans commented on HBASE-9217:
---
Looks good.
> TestReplicationSmallTests#testDisableEnable fails intermittently
>
>
> Key: HBASE-9217
> URL: https://issues.apache.org/jira/browse/HBASE-9217
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 9217-v1.txt, 9217-v2.txt, 9217-v3.txt,
> testDisableEnable.txt
>
>
> From
> https://builds.apache.org/job/HBase-0.95/444/testReport/junit/org.apache.hadoop.hbase.replication/TestReplicationSmallTests/testDisableEnable/
> :
> {code}
> java.lang.AssertionError: Waited too much time for put replication
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.hadoop.hbase.replication.TestReplicationSmallTests.testDisableEnable(TestReplicationSmallTests.java:313)
> ...
> 2013-08-14 08:06:47,228 DEBUG
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> wal.ProtobufLogReader(118): After reading the trailer: walEditsStopOffset: 0,
> fileLength: 0, trailerPresent: false
> 2013-08-14 08:06:47,228 WARN
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> regionserver.ReplicationSource(301): 2 Got:
> java.io.IOException: Cannot seek after EOF
> at
> org.apache.hadoop.hdfs.DFSClient$DFSInputStream.seek(DFSClient.java:2593)
> at
> org.apache.hadoop.fs.FSDataInputStream.seek(FSDataInputStream.java:37)
> at
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.seekOnFs(ProtobufLogReader.java:275)
> at
> org.apache.hadoop.hbase.regionserver.wal.ReaderBase.seek(ReaderBase.java:115)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogReaderManager.seek(ReplicationHLogReaderManager.java:108)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.readAllEntriesToReplicateOrNextFile(ReplicationSource.java:388)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:297)
> 2013-08-14 08:06:47,228 DEBUG
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> regionserver.ReplicationSource(578): Nothing to replicate, sleeping 100 times
> 1
> 2013-08-14 08:06:47,329 DEBUG
> [RS:1;vesta:39079-EventThread.replicationSource,2]
> fs.HFileSystem$ReorderWALBlocks(327):
> /user/jenkins/hbase/WALs/vesta.apache.org,39079,1376467506138/vesta.apache.org%2C39079%2C1376467506138.1376467603252
> is an HLog file, so reordering blocks, last hostname will be:vesta.apache.org
> {code}
> Looking at test output from successful builds, I didn't see the above
> exception.
--
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-9193) Make what Chaos monkey actions run configurable per test.
[
https://issues.apache.org/jira/browse/HBASE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-9193:
-
Affects Version/s: 0.95.1
> Make what Chaos monkey actions run configurable per test.
> -
>
> Key: HBASE-9193
> URL: https://issues.apache.org/jira/browse/HBASE-9193
> Project: HBase
> Issue Type: Task
>Affects Versions: 0.98.0, 0.95.1
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-9193-0.patch, HBASE-9193-1.patch
>
>
> Would be awesome to have every it test derive from the same base class that
> all allow setting of which ChaosMonkey.Actions to run.
> Something like:
> {code}
> hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> -Dverify.reduce.tasks=12 -DchaosMonkeyActionSet=SlowDeterministic
> loadAndVerify
> {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-9193) Make what Chaos monkey actions run configurable per test.
[
https://issues.apache.org/jira/browse/HBASE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-9193:
-
Attachment: HBASE-9193-1.patch
Patch that does what I was thinking.
> Make what Chaos monkey actions run configurable per test.
> -
>
> Key: HBASE-9193
> URL: https://issues.apache.org/jira/browse/HBASE-9193
> Project: HBase
> Issue Type: Task
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-9193-0.patch, HBASE-9193-1.patch
>
>
> Would be awesome to have every it test derive from the same base class that
> all allow setting of which ChaosMonkey.Actions to run.
> Something like:
> {code}
> hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> -Dverify.reduce.tasks=12 -DchaosMonkeyActionSet=SlowDeterministic
> loadAndVerify
> {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-9193) Make what Chaos monkey actions run configurable per test.
[
https://issues.apache.org/jira/browse/HBASE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-9193:
-
Affects Version/s: 0.98.0
Status: Patch Available (was: Open)
> Make what Chaos monkey actions run configurable per test.
> -
>
> Key: HBASE-9193
> URL: https://issues.apache.org/jira/browse/HBASE-9193
> Project: HBase
> Issue Type: Task
>Affects Versions: 0.98.0
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-9193-0.patch, HBASE-9193-1.patch
>
>
> Would be awesome to have every it test derive from the same base class that
> all allow setting of which ChaosMonkey.Actions to run.
> Something like:
> {code}
> hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> -Dverify.reduce.tasks=12 -DchaosMonkeyActionSet=SlowDeterministic
> loadAndVerify
> {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-9194) Break HMaster metrics into multiple contexts
[
https://issues.apache.org/jira/browse/HBASE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-9194:
-
Description:
Some metrics about the HMaster are about RPC call duration and other are about
how internal processes are running. We should make the difference clear so
that adding more of either kind doesn't confuse the user.
was:
The following metrics are supported by 0.94.x:
{code}
rpc.rpc.addColumn.aboveOneSec._avg_time
rpc.rpc.addColumn.aboveOneSec._num_ops
rpc.rpc.addColumn_avg_time
rpc.rpc.addColumn_num_ops
rpc.rpc.assign.aboveOneSec._avg_time
rpc.rpc.assign.aboveOneSec._num_ops
rpc.rpc.assign_avg_time
rpc.rpc.assign_num_ops
rpc.rpc.balance.aboveOneSec._avg_time
rpc.rpc.balance.aboveOneSec._num_ops
rpc.rpc.balanceSwitch.aboveOneSec._avg_time
rpc.rpc.balanceSwitch.aboveOneSec._num_ops
rpc.rpc.balanceSwitch_avg_time
rpc.rpc.balanceSwitch_num_ops
rpc.rpc.balance_avg_time
rpc.rpc.balance_num_ops
rpc.rpc.bulkLoadHFiles_avg_time
rpc.rpc.bulkLoadHFiles_num_ops
rpc.rpc.callQueueLen
rpc.rpc.checkAndDelete_avg_time
rpc.rpc.checkAndDelete_num_ops
rpc.rpc.checkAndPut_avg_time
rpc.rpc.checkAndPut_num_ops
rpc.rpc.closeRegion_avg_time
rpc.rpc.closeRegion_num_ops
rpc.rpc.close_avg_time
rpc.rpc.close_num_ops
rpc.rpc.compactRegion_avg_time
rpc.rpc.compactRegion_num_ops
rpc.rpc.createTable.aboveOneSec._avg_time
rpc.rpc.createTable.aboveOneSec._num_ops
rpc.rpc.createTable_avg_time
rpc.rpc.createTable_num_ops
rpc.rpc.deleteColumn.aboveOneSec._avg_time
rpc.rpc.deleteColumn.aboveOneSec._num_ops
rpc.rpc.deleteColumn_avg_time
rpc.rpc.deleteColumn_num_ops
rpc.rpc.deleteTable.aboveOneSec._avg_time
rpc.rpc.deleteTable.aboveOneSec._num_ops
rpc.rpc.deleteTable_avg_time
rpc.rpc.deleteTable_num_ops
rpc.rpc.delete_avg_time
rpc.rpc.delete_num_ops
rpc.rpc.disableTable.aboveOneSec._avg_time
rpc.rpc.disableTable.aboveOneSec._num_ops
rpc.rpc.disableTable_avg_time
rpc.rpc.disableTable_num_ops
rpc.rpc.enableTable.aboveOneSec._avg_time
rpc.rpc.enableTable.aboveOneSec._num_ops
rpc.rpc.enableTable_avg_time
rpc.rpc.enableTable_num_ops
rpc.rpc.execCoprocessor_avg_time
rpc.rpc.execCoprocessor_num_ops
rpc.rpc.exists_avg_time
rpc.rpc.exists_num_ops
rpc.rpc.flushRegion_avg_time
rpc.rpc.flushRegion_num_ops
rpc.rpc.getAlterStatus.aboveOneSec._avg_time
rpc.rpc.getAlterStatus.aboveOneSec._num_ops
rpc.rpc.getAlterStatus_avg_time
rpc.rpc.getAlterStatus_num_ops
rpc.rpc.getBlockCacheColumnFamilySummaries_avg_time
rpc.rpc.getBlockCacheColumnFamilySummaries_num_ops
rpc.rpc.getClosestRowBefore_avg_time
rpc.rpc.getClosestRowBefore_num_ops
rpc.rpc.getClusterStatus.aboveOneSec._avg_time
rpc.rpc.getClusterStatus.aboveOneSec._num_ops
rpc.rpc.getClusterStatus_avg_time
rpc.rpc.getClusterStatus_num_ops
rpc.rpc.getHServerInfo_avg_time
rpc.rpc.getHServerInfo_num_ops
rpc.rpc.getHTableDescriptors.aboveOneSec._avg_time
rpc.rpc.getHTableDescriptors.aboveOneSec._num_ops
rpc.rpc.getHTableDescriptors_avg_time
rpc.rpc.getHTableDescriptors_num_ops
rpc.rpc.getOnlineRegions_avg_time
rpc.rpc.getOnlineRegions_num_ops
rpc.rpc.getProtocolSignature.aboveOneSec._avg_time
rpc.rpc.getProtocolSignature.aboveOneSec._num_ops
rpc.rpc.getProtocolSignature_avg_time
rpc.rpc.getProtocolSignature_num_ops
rpc.rpc.getProtocolVersion.aboveOneSec._avg_time
rpc.rpc.getProtocolVersion.aboveOneSec._num_ops
rpc.rpc.getProtocolVersion_avg_time
rpc.rpc.getProtocolVersion_num_ops
rpc.rpc.getRegionInfo_avg_time
rpc.rpc.getRegionInfo_num_ops
rpc.rpc.get_avg_time
rpc.rpc.get_num_ops
rpc.rpc.incrementColumnValue_avg_time
rpc.rpc.incrementColumnValue_num_ops
rpc.rpc.increment_avg_time
rpc.rpc.increment_num_ops
rpc.rpc.isMasterRunning.aboveOneSec._avg_time
rpc.rpc.isMasterRunning.aboveOneSec._num_ops
rpc.rpc.isMasterRunning_avg_time
rpc.rpc.isMasterRunning_num_ops
rpc.rpc.lockRow_avg_time
rpc.rpc.lockRow_num_ops
rpc.rpc.modifyColumn.aboveOneSec._avg_time
rpc.rpc.modifyColumn.aboveOneSec._num_ops
rpc.rpc.modifyColumn_avg_time
rpc.rpc.modifyColumn_num_ops
rpc.rpc.modifyTable.aboveOneSec._avg_time
rpc.rpc.modifyTable.aboveOneSec._num_ops
rpc.rpc.modifyTable_avg_time
rpc.rpc.modifyTable_num_ops
rpc.rpc.move.aboveOneSec._avg_time
rpc.rpc.move.aboveOneSec._num_ops
rpc.rpc.move_avg_time
rpc.rpc.move_num_ops
rpc.rpc.multi_avg_time
rpc.rpc.multi_num_ops
rpc.rpc.next_avg_time
rpc.rpc.next_num_ops
rpc.rpc.offline.aboveOneSec._avg_time
rpc.rpc.offline.aboveOneSec._num_ops
rpc.rpc.offline_avg_time
rpc.rpc.offline_num_ops
rpc.rpc.openRegion_avg_time
rpc.rpc.openRegion_num_ops
rpc.rpc.openRegions_avg_time
rpc.rpc.openRegions_num_ops
rpc.rpc.openScanner_avg_time
rpc.rpc.openScanner_num_ops
rpc.rpc.put_avg_time
rpc.rpc.put_num_ops
rpc.rpc.regionServerReport.aboveOneSec._avg_time
rpc.rpc.regionServerReport.aboveOneSec._num_ops
rpc.rpc.regionServerReport_avg_time
rpc.rpc.regionServerReport_num_ops
rpc.rpc.regionServerStartup.aboveOneSec._avg_time
rpc.rpc.regionServerStartup.aboveOneSec._num_ops
rpc.rpc.regionServerStartup_avg_t
[jira] [Updated] (HBASE-9194) Break HMaster metrics into multiple contexts
[
https://issues.apache.org/jira/browse/HBASE-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-9194:
-
Attachment: HBASE-9194-3.patch
Reattaching to run tests again. Tests run well for me but I want to be extra
careful before we cut an rc.
I also changed the title to more accurately reflect what was completed here.
> Break HMaster metrics into multiple contexts
>
>
> Key: HBASE-9194
> URL: https://issues.apache.org/jira/browse/HBASE-9194
> Project: HBase
> Issue Type: Task
> Components: metrics
>Affects Versions: 0.98.0, 0.95.1
>Reporter: Ted Yu
>Assignee: Elliott Clark
> Attachments: 9194-v1.txt, HBASE-9194-0.patch, HBASE-9194-1.patch,
> HBASE-9194-2.patch, HBASE-9194-3.patch, HBASE-9194-3.patch
>
>
> The following metrics are supported by 0.94.x:
> {code}
> rpc.rpc.addColumn.aboveOneSec._avg_time
> rpc.rpc.addColumn.aboveOneSec._num_ops
> rpc.rpc.addColumn_avg_time
> rpc.rpc.addColumn_num_ops
> rpc.rpc.assign.aboveOneSec._avg_time
> rpc.rpc.assign.aboveOneSec._num_ops
> rpc.rpc.assign_avg_time
> rpc.rpc.assign_num_ops
> rpc.rpc.balance.aboveOneSec._avg_time
> rpc.rpc.balance.aboveOneSec._num_ops
> rpc.rpc.balanceSwitch.aboveOneSec._avg_time
> rpc.rpc.balanceSwitch.aboveOneSec._num_ops
> rpc.rpc.balanceSwitch_avg_time
> rpc.rpc.balanceSwitch_num_ops
> rpc.rpc.balance_avg_time
> rpc.rpc.balance_num_ops
> rpc.rpc.bulkLoadHFiles_avg_time
> rpc.rpc.bulkLoadHFiles_num_ops
> rpc.rpc.callQueueLen
> rpc.rpc.checkAndDelete_avg_time
> rpc.rpc.checkAndDelete_num_ops
> rpc.rpc.checkAndPut_avg_time
> rpc.rpc.checkAndPut_num_ops
> rpc.rpc.closeRegion_avg_time
> rpc.rpc.closeRegion_num_ops
> rpc.rpc.close_avg_time
> rpc.rpc.close_num_ops
> rpc.rpc.compactRegion_avg_time
> rpc.rpc.compactRegion_num_ops
> rpc.rpc.createTable.aboveOneSec._avg_time
> rpc.rpc.createTable.aboveOneSec._num_ops
> rpc.rpc.createTable_avg_time
> rpc.rpc.createTable_num_ops
> rpc.rpc.deleteColumn.aboveOneSec._avg_time
> rpc.rpc.deleteColumn.aboveOneSec._num_ops
> rpc.rpc.deleteColumn_avg_time
> rpc.rpc.deleteColumn_num_ops
> rpc.rpc.deleteTable.aboveOneSec._avg_time
> rpc.rpc.deleteTable.aboveOneSec._num_ops
> rpc.rpc.deleteTable_avg_time
> rpc.rpc.deleteTable_num_ops
> rpc.rpc.delete_avg_time
> rpc.rpc.delete_num_ops
> rpc.rpc.disableTable.aboveOneSec._avg_time
> rpc.rpc.disableTable.aboveOneSec._num_ops
> rpc.rpc.disableTable_avg_time
> rpc.rpc.disableTable_num_ops
> rpc.rpc.enableTable.aboveOneSec._avg_time
> rpc.rpc.enableTable.aboveOneSec._num_ops
> rpc.rpc.enableTable_avg_time
> rpc.rpc.enableTable_num_ops
> rpc.rpc.execCoprocessor_avg_time
> rpc.rpc.execCoprocessor_num_ops
> rpc.rpc.exists_avg_time
> rpc.rpc.exists_num_ops
> rpc.rpc.flushRegion_avg_time
> rpc.rpc.flushRegion_num_ops
> rpc.rpc.getAlterStatus.aboveOneSec._avg_time
> rpc.rpc.getAlterStatus.aboveOneSec._num_ops
> rpc.rpc.getAlterStatus_avg_time
> rpc.rpc.getAlterStatus_num_ops
> rpc.rpc.getBlockCacheColumnFamilySummaries_avg_time
> rpc.rpc.getBlockCacheColumnFamilySummaries_num_ops
> rpc.rpc.getClosestRowBefore_avg_time
> rpc.rpc.getClosestRowBefore_num_ops
> rpc.rpc.getClusterStatus.aboveOneSec._avg_time
> rpc.rpc.getClusterStatus.aboveOneSec._num_ops
> rpc.rpc.getClusterStatus_avg_time
> rpc.rpc.getClusterStatus_num_ops
> rpc.rpc.getHServerInfo_avg_time
> rpc.rpc.getHServerInfo_num_ops
> rpc.rpc.getHTableDescriptors.aboveOneSec._avg_time
> rpc.rpc.getHTableDescriptors.aboveOneSec._num_ops
> rpc.rpc.getHTableDescriptors_avg_time
> rpc.rpc.getHTableDescriptors_num_ops
> rpc.rpc.getOnlineRegions_avg_time
> rpc.rpc.getOnlineRegions_num_ops
> rpc.rpc.getProtocolSignature.aboveOneSec._avg_time
> rpc.rpc.getProtocolSignature.aboveOneSec._num_ops
> rpc.rpc.getProtocolSignature_avg_time
> rpc.rpc.getProtocolSignature_num_ops
> rpc.rpc.getProtocolVersion.aboveOneSec._avg_time
> rpc.rpc.getProtocolVersion.aboveOneSec._num_ops
> rpc.rpc.getProtocolVersion_avg_time
> rpc.rpc.getProtocolVersion_num_ops
> rpc.rpc.getRegionInfo_avg_time
> rpc.rpc.getRegionInfo_num_ops
> rpc.rpc.get_avg_time
> rpc.rpc.get_num_ops
> rpc.rpc.incrementColumnValue_avg_time
> rpc.rpc.incrementColumnValue_num_ops
> rpc.rpc.increment_avg_time
> rpc.rpc.increment_num_ops
> rpc.rpc.isMasterRunning.aboveOneSec._avg_time
> rpc.rpc.isMasterRunning.aboveOneSec._num_ops
> rpc.rpc.isMasterRunning_avg_time
> rpc.rpc.isMasterRunning_num_ops
> rpc.rpc.lockRow_avg_time
> rpc.rpc.lockRow_num_ops
> rpc.rpc.modifyColumn.aboveOneSec._avg_time
> rpc.rpc.modifyColumn.aboveOneSec._num_ops
> rpc.rpc.modifyColumn_avg_time
> rpc.rpc.modifyColumn_num_ops
> rpc.rpc.modifyTable.aboveOneSec._avg_time
> rpc.rpc.modifyTable.aboveOneSec._num_ops
> rpc.rpc.modifyTable_avg_time
> rpc.rpc.modifyTable_num_ops
> rpc.rpc.move.aboveOneSec._avg_time
> rpc.rpc.move.aboveOneSec._num_ops
> rpc.rpc.
