[jira] [Resolved] (HBASE-7477) Remove Proxy instance from HBase RPC
[ https://issues.apache.org/jira/browse/HBASE-7477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-7477. -- Resolution: Duplicate Resolving as duplicate; being implemented by HBASE-8214 Remove Proxy instance from HBase RPC Key: HBASE-7477 URL: https://issues.apache.org/jira/browse/HBASE-7477 Project: HBase Issue Type: Sub-task Affects Versions: 0.89-fb Reporter: Karthik Ranganathan Attachments: 7477experiment.txt, HBASE-7477.patch Currently, we use HBaseRPC.getProxy() to get an Invoker object to serialize the RPC parameters. This is pretty inefficient as it uses reflection to lookup the current method name. The aim is to break up the proxy into an actual proxy implementation so that: 1. we can make it more efficient by eliminating reflection 2. can re-write some parts of the protocol to make it even better -- 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-8214) Remove proxy and engine, rely directly on pb generated Service
[ https://issues.apache.org/jira/browse/HBASE-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8214: - Attachment: 8214v8.txt Rather than have one FatalConnectionException that i use for all fatal connection setup issues, instead, make an exception per failure type (all derive from FCE). For example UnsupportedCompressionCodecException, etc. Remove proxy and engine, rely directly on pb generated Service -- Key: HBASE-8214 URL: https://issues.apache.org/jira/browse/HBASE-8214 Project: HBase Issue Type: Bug Components: IPC/RPC Reporter: stack Assignee: stack Attachments: 8124.txt, 8214v2.txt, 8214v3.txt, 8214v4.txt, 8214v5.txt, 8214v6.txt, 8214v7.txt, 8214v8.txt Attached patch is not done. Removes two to three layers -- depending on how you count -- between client and rpc client and similar on server side (between rpc and server implementation). Strips ProtobufRpcServer/Client and HBaseClientRpc/HBaseServerRpc. Also gets rid of proxy. -- 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-8455) Update ExportSnapshot to reflect changes in HBASE-7419
[ https://issues.apache.org/jira/browse/HBASE-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Bertozzi updated HBASE-8455: --- Attachment: HBASE-8455-94.patch Update ExportSnapshot to reflect changes in HBASE-7419 -- Key: HBASE-8455 URL: https://issues.apache.org/jira/browse/HBASE-8455 Project: HBase Issue Type: Bug Affects Versions: 0.94.8 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Fix For: 0.95.2 Attachments: HBASE-8455-94.patch, HBASE-8455-v0.patch HBASE-7419 changed the link naming and the HFileLink/Reference check. ExportSnapshot was not updated after that, so with a Link Reference HFileLink.isLink() now returns false and causes an error during a exportSnapshot with reference files -- 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-8471) Server-side, remove convertion from pb type to client type before we call method
stack created HBASE-8471: Summary: Server-side, remove convertion from pb type to client type before we call method Key: HBASE-8471 URL: https://issues.apache.org/jira/browse/HBASE-8471 Project: HBase Issue Type: Improvement Components: IPC/RPC, regionserver Reporter: stack In the regionserver, when the rpc receives a call, the call is described using protobufs. Before we make the server-side invocation, we do a transform on the pb param objects to make a native pojo -- e.g. from a pb Puts into an hbase o.a.h.h.client.Put -- and only then do we make the call against the server. On the way out, similar, before putting the result on the wire, we will do a convertion from o.a.h.h.client.Result into pb Result. This issue is about our first INVESTIGATING if it is possible to do away w/ this marshalling/unmarshalling serverside especially given the pb objects themselves are rich in accessor and getters, etc. If it is possible to do w/ pbs alone serverside, then we should go ahead and rip out all the serverside convertions. -- 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-8446) Allow parallel snapshot of different tables
[
https://issues.apache.org/jira/browse/HBASE-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646090#comment-13646090
]
Hadoop QA commented on HBASE-8446:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581234/HBASE-8446-v4.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 9 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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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:
org.apache.hadoop.hbase.util.TestHBaseFsck
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5505//console
This message is automatically generated.
Allow parallel snapshot of different tables
---
Key: HBASE-8446
URL: https://issues.apache.org/jira/browse/HBASE-8446
Project: HBase
Issue Type: Improvement
Components: snapshots
Affects Versions: 0.95.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
Fix For: 0.95.2
Attachments: HBASE-8446-94.patch, HBASE-8446-v0.patch,
HBASE-8446-v1.patch, HBASE-8446-v2.patch, HBASE-8446-v3.patch,
HBASE-8446-v4.patch
currently only one snapshot at the time is allowed.
Like for the restore, we should allow taking snapshot of different tables in
parallel.
--
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-8468) IntegrationTestImportTsv fails on a cluster
[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646097#comment-13646097
]
Enis Soztutar commented on HBASE-8468:
--
Thanks Elliot. Lgtm.
IntegrationTestImportTsv fails on a cluster
---
Key: HBASE-8468
URL: https://issues.apache.org/jira/browse/HBASE-8468
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Attachments: HBASE-8468-0.patch, HBASE-8468-1.patch
It appears that the JobLaunchingOuputCommitter is not properly picking up the
configuration.
the quorum is set in the job conf when I look at it in the yarn mr history
manager. However as you can see below the zk session is still defaulting to
127.0.0.1
{code}
2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
org.apache.zookeeper.ClientCnxn: Opening socket connection to server
/127.0.0.1:2181
2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
this process is hconnection-0x1704de3e
2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
ZooKeeper, quorum=localhost:2181,
exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
2013-04-30 10:18:54,847 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.util.RetryCounter: Sleeping 2000ms before retry #1...
2013-04-30 10:18:54,882 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before
Scheduling: PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0
AssignedReds:1 CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0
HostLocal:0 RackLocal:1
2013-04-30 10:18:55,839 INFO [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Opening
socket connection to server localhost/127.0.0.1:2181
2013-04-30 10:18:55,840 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:55,887 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Received
completed container container_1367340870656_0004_01_03
2013-04-30 10:18:55,888 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: After Scheduling:
PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0 AssignedReds:0
CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0 HostLocal:0 RackLocal:1
2013-04-30 10:18:55,888 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics
report from attempt_1367340870656_0004_r_00_0: Container killed by the
ApplicationMaster.
{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-8470) Data file used by TestReference should be excluded from Apache Rat check
[
https://issues.apache.org/jira/browse/HBASE-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646103#comment-13646103
]
Hadoop QA commented on HBASE-8470:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581237/8470.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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces 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/5506//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5506//console
This message is automatically generated.
Data file used by TestReference should be excluded from Apache Rat check
Key: HBASE-8470
URL: https://issues.apache.org/jira/browse/HBASE-8470
Project: HBase
Issue Type: Improvement
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 8470.txt
hbase-server/src/test/data/a6a6562b777440fd9c34885428f5cb61.21e75333ada3d5bafb34bb918f29576c
is used by TestReference to verify the format compatibility.
We should exclude this file from Apache Rat check.
--
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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
Jonathan Hsieh created HBASE-8472:
-
Summary: mvn -Dhadoop.profile=2.0
-Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt
o.a.h.IdGenerator
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646107#comment-13646107
]
Jonathan Hsieh commented on HBASE-8472:
---
IdGenerator not in 2.0.2-alpha
We are pulling in 2.0.2-alpha jar for hadoop-common, but 2.0.5-SNAPSHOT for all
others.
{code}
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT depedenncy:tree
INFO] +- org.apache.hbase:hbase-hadoop2-compat:jar:0.97.0-SNAPSHOT:compile
[INFO] | \- org.apache.hadoop:hadoop-common:jar:2.0.2-alpha:compile
...
[INFO] +- org.cloudera.htrace:htrace:jar:1.50:compile
[INFO] +- org.apache.hadoop:hadoop-client:jar:2.0.5-SNAPSHOT:compile
[INFO] | +- org.apache.hadoop:hadoop-hdfs:jar:2.0.5-SNAPSHOT:compile
[INFO] | +-
org.apache.hadoop:hadoop-mapreduce-client-app:jar:2.0.5-SNAPSHOT:compile
...
{code}
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8455) Update ExportSnapshot to reflect changes in HBASE-7419
[ https://issues.apache.org/jira/browse/HBASE-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646115#comment-13646115 ] Ted Yu commented on HBASE-8455: --- Thanks for the quick response, Matteo. Update ExportSnapshot to reflect changes in HBASE-7419 -- Key: HBASE-8455 URL: https://issues.apache.org/jira/browse/HBASE-8455 Project: HBase Issue Type: Bug Affects Versions: 0.94.8 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Fix For: 0.95.2 Attachments: HBASE-8455-94.patch, HBASE-8455-v0.patch HBASE-7419 changed the link naming and the HFileLink/Reference check. ExportSnapshot was not updated after that, so with a Link Reference HFileLink.isLink() now returns false and causes an error during a exportSnapshot with reference files -- 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-8468) IntegrationTestImportTsv fails on a cluster
[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646125#comment-13646125
]
Hadoop QA commented on HBASE-8468:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581240/HBASE-8468-0.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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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:
org.apache.hadoop.hbase.util.TestHBaseFsck
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5507//console
This message is automatically generated.
IntegrationTestImportTsv fails on a cluster
---
Key: HBASE-8468
URL: https://issues.apache.org/jira/browse/HBASE-8468
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Attachments: HBASE-8468-0.patch, HBASE-8468-1.patch
It appears that the JobLaunchingOuputCommitter is not properly picking up the
configuration.
the quorum is set in the job conf when I look at it in the yarn mr history
manager. However as you can see below the zk session is still defaulting to
127.0.0.1
{code}
2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
org.apache.zookeeper.ClientCnxn: Opening socket connection to server
/127.0.0.1:2181
2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
this process is hconnection-0x1704de3e
2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
ZooKeeper, quorum=localhost:2181,
[jira] [Commented] (HBASE-8455) Update ExportSnapshot to reflect changes in HBASE-7419
[
https://issues.apache.org/jira/browse/HBASE-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646129#comment-13646129
]
Hadoop QA commented on HBASE-8455:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581253/HBASE-8455-94.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:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5510//console
This message is automatically generated.
Update ExportSnapshot to reflect changes in HBASE-7419
--
Key: HBASE-8455
URL: https://issues.apache.org/jira/browse/HBASE-8455
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.8
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Fix For: 0.95.2
Attachments: HBASE-8455-94.patch, HBASE-8455-v0.patch
HBASE-7419 changed the link naming and the HFileLink/Reference check.
ExportSnapshot was not updated after that, so with a Link Reference
HFileLink.isLink() now returns false and causes an error during a
exportSnapshot with reference files
--
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] [Assigned] (HBASE-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-8472:
-
Assignee: Jonathan Hsieh
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8470) Data file used by TestReference should be excluded from Apache Rat check
[ https://issues.apache.org/jira/browse/HBASE-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646154#comment-13646154 ] stack commented on HBASE-8470: -- +1 Data file used by TestReference should be excluded from Apache Rat check Key: HBASE-8470 URL: https://issues.apache.org/jira/browse/HBASE-8470 Project: HBase Issue Type: Improvement Reporter: Ted Yu Assignee: Ted Yu Attachments: 8470.txt hbase-server/src/test/data/a6a6562b777440fd9c34885428f5cb61.21e75333ada3d5bafb34bb918f29576c is used by TestReference to verify the format compatibility. We should exclude this file from Apache Rat check. -- 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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8472:
--
Attachment: hbase-8472.patch
This seems to do the trick. I believe the logic is something like this.
The hbase-hadoop2-compat module compiles properly and resolves to the specified
hadoop-two.version at comile time. There is some sort of order of operations
problem where when we get to the hbase-server module, the transitive pull in of
hbase-common gets overridden by the parent (which has a hard coded
hadoop-2.0.2-alpha).
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8468) IntegrationTestImportTsv fails on a cluster
[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-8468:
-
Resolution: Fixed
Fix Version/s: 0.95.1
0.98.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks enis.
IntegrationTestImportTsv fails on a cluster
---
Key: HBASE-8468
URL: https://issues.apache.org/jira/browse/HBASE-8468
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 0.98.0, 0.95.1
Attachments: HBASE-8468-0.patch, HBASE-8468-1.patch
It appears that the JobLaunchingOuputCommitter is not properly picking up the
configuration.
the quorum is set in the job conf when I look at it in the yarn mr history
manager. However as you can see below the zk session is still defaulting to
127.0.0.1
{code}
2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
org.apache.zookeeper.ClientCnxn: Opening socket connection to server
/127.0.0.1:2181
2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
this process is hconnection-0x1704de3e
2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
ZooKeeper, quorum=localhost:2181,
exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
2013-04-30 10:18:54,847 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.util.RetryCounter: Sleeping 2000ms before retry #1...
2013-04-30 10:18:54,882 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before
Scheduling: PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0
AssignedReds:1 CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0
HostLocal:0 RackLocal:1
2013-04-30 10:18:55,839 INFO [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Opening
socket connection to server localhost/127.0.0.1:2181
2013-04-30 10:18:55,840 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:55,887 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Received
completed container container_1367340870656_0004_01_03
2013-04-30 10:18:55,888 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: After Scheduling:
PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0 AssignedReds:0
CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0 HostLocal:0 RackLocal:1
2013-04-30 10:18:55,888 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics
report from attempt_1367340870656_0004_r_00_0: Container killed by the
ApplicationMaster.
{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-7680) implement compaction policy for stripe compactions
[ https://issues.apache.org/jira/browse/HBASE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-7680: Attachment: HBASE-7680-v8-with-7679.patch HBASE-7680-v8.patch Rebase patch and update size-based compactions implement compaction policy for stripe compactions -- Key: HBASE-7680 URL: https://issues.apache.org/jira/browse/HBASE-7680 Project: HBase Issue Type: Sub-task Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Attachments: HBASE-7680-v0.patch, HBASE-7680-v1.patch, HBASE-7680-v1-with-7679.patch, HBASE-7680-v2.patch, HBASE-7680-v2-with-7679-and-8034.patch, HBASE-7680-v3.patch, HBASE-7680-v3-with-7679.patch, HBASE-7680-v4.patch, HBASE-7680-v4-with-7679.patch, HBASE-7680-v5.patch, HBASE-7680-v5-with-7679.patch, HBASE-7680-v6.patch, HBASE-7680-v6-with-7679.patch, HBASE-7680-v7.patch, HBASE-7680-v8.patch, HBASE-7680-v8-with-7679.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-7680) implement compaction policy for stripe compactions
[ https://issues.apache.org/jira/browse/HBASE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-7680: Attachment: (was: HBASE-7680-v7-with-7679.patch) implement compaction policy for stripe compactions -- Key: HBASE-7680 URL: https://issues.apache.org/jira/browse/HBASE-7680 Project: HBase Issue Type: Sub-task Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Attachments: HBASE-7680-v0.patch, HBASE-7680-v1.patch, HBASE-7680-v1-with-7679.patch, HBASE-7680-v2.patch, HBASE-7680-v2-with-7679-and-8034.patch, HBASE-7680-v3.patch, HBASE-7680-v3-with-7679.patch, HBASE-7680-v4.patch, HBASE-7680-v4-with-7679.patch, HBASE-7680-v5.patch, HBASE-7680-v5-with-7679.patch, HBASE-7680-v6.patch, HBASE-7680-v6-with-7679.patch, HBASE-7680-v7.patch, HBASE-7680-v8.patch, HBASE-7680-v8-with-7679.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-7680) implement compaction policy for stripe compactions
[ https://issues.apache.org/jira/browse/HBASE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-7680: Attachment: (was: HBASE-7680-v0-with-7679-and-7935.patch) implement compaction policy for stripe compactions -- Key: HBASE-7680 URL: https://issues.apache.org/jira/browse/HBASE-7680 Project: HBase Issue Type: Sub-task Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Attachments: HBASE-7680-v0.patch, HBASE-7680-v1.patch, HBASE-7680-v1-with-7679.patch, HBASE-7680-v2.patch, HBASE-7680-v2-with-7679-and-8034.patch, HBASE-7680-v3.patch, HBASE-7680-v3-with-7679.patch, HBASE-7680-v4.patch, HBASE-7680-v4-with-7679.patch, HBASE-7680-v5.patch, HBASE-7680-v5-with-7679.patch, HBASE-7680-v6.patch, HBASE-7680-v6-with-7679.patch, HBASE-7680-v7.patch, HBASE-7680-v8.patch, HBASE-7680-v8-with-7679.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-8468) IntegrationTestImportTsv fails on a cluster
[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646166#comment-13646166
]
Hadoop QA commented on HBASE-8468:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581249/HBASE-8468-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 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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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/5508//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5508//console
This message is automatically generated.
IntegrationTestImportTsv fails on a cluster
---
Key: HBASE-8468
URL: https://issues.apache.org/jira/browse/HBASE-8468
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 0.98.0, 0.95.1
Attachments: HBASE-8468-0.patch, HBASE-8468-1.patch
It appears that the JobLaunchingOuputCommitter is not properly picking up the
configuration.
the quorum is set in the job conf when I look at it in the yarn mr history
manager. However as you can see below the zk session is still defaulting to
127.0.0.1
{code}
2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
org.apache.zookeeper.ClientCnxn: Opening socket connection to server
/127.0.0.1:2181
2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
this process is hconnection-0x1704de3e
2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
ZooKeeper, quorum=localhost:2181,
[jira] [Updated] (HBASE-8272) make compaction checker frequency configurable per table/cf
[ https://issues.apache.org/jira/browse/HBASE-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-8272: Status: Patch Available (was: Reopened) make compaction checker frequency configurable per table/cf --- Key: HBASE-8272 URL: https://issues.apache.org/jira/browse/HBASE-8272 Project: HBase Issue Type: Improvement Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Minor Attachments: HBASE-8272-addendum.patch, HBASE-8272-v0.patch, HBASE-8272-v1.patch, HBASE-8272-v2.patch, HBASE-8272-v2.patch, HBASE-8272-v3.patch Makes the compaction checker frequency configurable per table/cf; that is useful for compaction schemes where many compactions can be available at any time, so the default checks/requests that HBase performs may be insufficient. -- 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-8272) make compaction checker frequency configurable per table/cf
[ https://issues.apache.org/jira/browse/HBASE-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646174#comment-13646174 ] Sergey Shelukhin commented on HBASE-8272: - [~jdcryans] does the attached addendum work for you? thanks make compaction checker frequency configurable per table/cf --- Key: HBASE-8272 URL: https://issues.apache.org/jira/browse/HBASE-8272 Project: HBase Issue Type: Improvement Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Minor Attachments: HBASE-8272-addendum.patch, HBASE-8272-v0.patch, HBASE-8272-v1.patch, HBASE-8272-v2.patch, HBASE-8272-v2.patch, HBASE-8272-v3.patch Makes the compaction checker frequency configurable per table/cf; that is useful for compaction schemes where many compactions can be available at any time, so the default checks/requests that HBase performs may be insufficient. -- 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-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Vashishtha updated HBASE-7122:
---
Attachment: HBase-7122-94-v2.patch
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-94-v2.patch,
HBase-7122-95.patch, HBase-7122-95-v2.patch, HBase-7122-95-v3.patch,
HBase-7122-95-v4.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
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-7122) Proper warning message when opening a log file with no entries (idle cluster)
[
https://issues.apache.org/jira/browse/HBASE-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Vashishtha updated HBASE-7122:
---
Fix Version/s: 0.94.8
Proper warning message when opening a log file with no entries (idle cluster)
-
Key: HBASE-7122
URL: https://issues.apache.org/jira/browse/HBASE-7122
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 0.94.2
Reporter: Himanshu Vashishtha
Assignee: Himanshu Vashishtha
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: HBase-7122-94.patch, HBase-7122-94-v2.patch,
HBase-7122-95.patch, HBase-7122-95-v2.patch, HBase-7122-95-v3.patch,
HBase-7122-95-v4.patch, HBase-7122.patch, HBASE-7122.v2.patch
In case the cluster is idle and the log has rolled (offset to 0),
replicationSource tries to open the log and gets an EOF exception. This gets
printed after every 10 sec until an entry is inserted in it.
{code}
2012-11-07 15:47:40,924 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:openReader(487)) - Opening log for replication
c0315.hal.cloudera.com%2C40020%2C1352324202860.1352327804874 at 0
2012-11-07 15:47:40,926 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(543)) - 1 Got:
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1508)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1486)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1475)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1470)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:55)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:175)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:716)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.openReader(ReplicationSource.java:491)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:290)
2012-11-07 15:47:40,927 WARN regionserver.ReplicationSource
(ReplicationSource.java:openReader(547)) - Waited too long for this file,
considering dumping
2012-11-07 15:47:40,927 DEBUG regionserver.ReplicationSource
(ReplicationSource.java:sleepForRetries(562)) - Unable to open a reader,
sleeping 1000 times 10
{code}
We should reduce the log spewing in this case (or some informative message,
based on the offset).
--
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-8460) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues
[ https://issues.apache.org/jira/browse/HBASE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated HBASE-8460: Attachment: HBASE-8460-trunk-v2.patch Attached a new version of the patch addressing comments from [~sershe] and [~jdcryans]. Thanks guys for the review! [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues Key: HBASE-8460 URL: https://issues.apache.org/jira/browse/HBASE-8460 Project: HBase Issue Type: Bug Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Priority: Minor Fix For: 0.95.1 Attachments: HBASE-8460-trunk-v1.patch, HBASE-8460-trunk-v2.patch There are three TODO's in TestReplicationStateBasic.testReplicationQueues. 1. Possible NPE when getLogPosition is called on a Bogus HLog file. 2. The assertion that tested setting a log position on a bogus file was commented out. 3. When claimQueues is given the regionserver znode for itself, it will try to copy its own queues. -- 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-8460) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues
[ https://issues.apache.org/jira/browse/HBASE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated HBASE-8460: Attachment: (was: HBASE-8460-trunk-v2.patch) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues Key: HBASE-8460 URL: https://issues.apache.org/jira/browse/HBASE-8460 Project: HBase Issue Type: Bug Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Priority: Minor Fix For: 0.95.1 Attachments: HBASE-8460-trunk-v1.patch There are three TODO's in TestReplicationStateBasic.testReplicationQueues. 1. Possible NPE when getLogPosition is called on a Bogus HLog file. 2. The assertion that tested setting a log position on a bogus file was commented out. 3. When claimQueues is given the regionserver znode for itself, it will try to copy its own queues. -- 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-8460) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues
[ https://issues.apache.org/jira/browse/HBASE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646177#comment-13646177 ] Sergey Shelukhin commented on HBASE-8460: - I see all the same issues in this patch, are you sure it's the correct one? [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues Key: HBASE-8460 URL: https://issues.apache.org/jira/browse/HBASE-8460 Project: HBase Issue Type: Bug Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Priority: Minor Fix For: 0.95.1 Attachments: HBASE-8460-trunk-v1.patch There are three TODO's in TestReplicationStateBasic.testReplicationQueues. 1. Possible NPE when getLogPosition is called on a Bogus HLog file. 2. The assertion that tested setting a log position on a bogus file was commented out. 3. When claimQueues is given the regionserver znode for itself, it will try to copy its own queues. -- 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-8460) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues
[ https://issues.apache.org/jira/browse/HBASE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated HBASE-8460: Attachment: HBASE-8460-trunk-v2.patch Posted the wrong file. Attached is the correct v2. [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues Key: HBASE-8460 URL: https://issues.apache.org/jira/browse/HBASE-8460 Project: HBase Issue Type: Bug Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Priority: Minor Fix For: 0.95.1 Attachments: HBASE-8460-trunk-v1.patch, HBASE-8460-trunk-v2.patch There are three TODO's in TestReplicationStateBasic.testReplicationQueues. 1. Possible NPE when getLogPosition is called on a Bogus HLog file. 2. The assertion that tested setting a log position on a bogus file was commented out. 3. When claimQueues is given the regionserver znode for itself, it will try to copy its own queues. -- 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-8214) Remove proxy and engine, rely directly on pb generated Service
[
https://issues.apache.org/jira/browse/HBASE-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646186#comment-13646186
]
Hadoop QA commented on HBASE-8214:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581251/8214v8.txt
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 120
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
15 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 5 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:red}-1 lineLengths{color}. The patch introduces 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:
org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient
org.apache.hadoop.hbase.coprocessor.TestMasterCoprocessorExceptionWithRemove
org.apache.hadoop.hbase.backup.TestHFileArchiving
org.apache.hadoop.hbase.master.handler.TestTableDeleteFamilyHandler
org.apache.hadoop.hbase.snapshot.TestFlushSnapshotFromClient
org.apache.hadoop.hbase.client.TestAdmin
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient
org.apache.hadoop.hbase.master.TestMaster
org.apache.hadoop.hbase.master.TestTableLockManager
org.apache.hadoop.hbase.ipc.TestDelayedRpc
org.apache.hadoop.hbase.security.token.TestTokenAuthentication
org.apache.hadoop.hbase.master.TestRestartCluster
org.apache.hadoop.hbase.client.TestSnapshotFromClient
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.client.TestClientTimeouts.testAdminTimeout(TestClientTimeouts.java:108)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5509//console
This message is automatically generated.
Remove proxy and engine, rely directly on pb generated Service
--
Key: HBASE-8214
URL: https://issues.apache.org/jira/browse/HBASE-8214
Project: HBase
Issue Type: Bug
Components: IPC/RPC
Reporter: stack
Assignee: stack
Attachments: 8124.txt, 8214v2.txt, 8214v3.txt, 8214v4.txt,
8214v5.txt, 8214v6.txt, 8214v7.txt, 8214v8.txt
Attached patch is not done. Removes two to three layers -- depending on how
you count -- between client and rpc client and similar on server side
(between rpc and server implementation). Strips ProtobufRpcServer/Client and
HBaseClientRpc/HBaseServerRpc. Also gets
[jira] [Commented] (HBASE-8369) MapReduce over snapshot files
[ https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646189#comment-13646189 ] Sergey Shelukhin commented on HBASE-8369: - Skimmed the patch... should it be reviewed now or is just an example? MapReduce over snapshot files - Key: HBASE-8369 URL: https://issues.apache.org/jira/browse/HBASE-8369 Project: HBase Issue Type: New Feature Components: mapreduce, snapshots Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 0.98.0, 0.95.2 Attachments: hbase-8369_v0.patch The idea is to add an InputFormat, which can run the mapreduce job over snapshot files directly bypassing hbase server layer. The IF is similar in usage to TableInputFormat, taking a Scan object from the user, but instead of running from an online table, it runs from a table snapshot. We do one split per region in the snapshot, and open an HRegion inside the RecordReader. A RegionScanner is used internally for doing the scan without any HRegionServer bits. Users have been asking and searching for ways to run MR jobs by reading directly from hfiles, so this allows new use cases if reading from stale data is ok: - Take snapshots periodically, and run MR jobs only on snapshots. - Export snapshots to remote hdfs cluster, run the MR jobs at that cluster without HBase cluster. - (Future use case) Combine snapshot data with online hbase data: Scan from yesterday's snapshot, but read today's data from online hbase cluster. -- 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-8455) Update ExportSnapshot to reflect changes in HBASE-7419
[ https://issues.apache.org/jira/browse/HBASE-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646193#comment-13646193 ] Sergey Shelukhin commented on HBASE-8455: - +1 Update ExportSnapshot to reflect changes in HBASE-7419 -- Key: HBASE-8455 URL: https://issues.apache.org/jira/browse/HBASE-8455 Project: HBase Issue Type: Bug Affects Versions: 0.94.8 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Fix For: 0.95.2 Attachments: HBASE-8455-94.patch, HBASE-8455-v0.patch HBASE-7419 changed the link naming and the HFileLink/Reference check. ExportSnapshot was not updated after that, so with a Link Reference HFileLink.isLink() now returns false and causes an error during a exportSnapshot with reference files -- 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-8446) Allow parallel snapshot of different tables
[ https://issues.apache.org/jira/browse/HBASE-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646205#comment-13646205 ] Sergey Shelukhin commented on HBASE-8446: - Perhaps the name and comment of is... methods could be made more explicit about modifying state? Allow parallel snapshot of different tables --- Key: HBASE-8446 URL: https://issues.apache.org/jira/browse/HBASE-8446 Project: HBase Issue Type: Improvement Components: snapshots Affects Versions: 0.95.0 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Priority: Minor Fix For: 0.95.2 Attachments: HBASE-8446-94.patch, HBASE-8446-v0.patch, HBASE-8446-v1.patch, HBASE-8446-v2.patch, HBASE-8446-v3.patch, HBASE-8446-v4.patch currently only one snapshot at the time is allowed. Like for the restore, we should allow taking snapshot of different tables in parallel. -- 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-8446) Allow parallel snapshot of different tables
[
https://issues.apache.org/jira/browse/HBASE-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646224#comment-13646224
]
Sergey Shelukhin commented on HBASE-8446:
-
{code}
* The thread limitation on the executorService's thread pool for snapshots
ensures the
* snapshot won't be started if there is another snapshot already running.
Does
{code}
What does this comment say? Thread number can be 1.
{code}
this.executorService.submit(handler);
this.snapshotHandlers.put(snapshot.getTable(), handler);
{code}
What ensures that put doesn't replace the old value?
{code}
/** Wait time before removing a finished sentinel from the in-progress map */
{code}
Is it possible to add explanation why this is necessary?
Allow parallel snapshot of different tables
---
Key: HBASE-8446
URL: https://issues.apache.org/jira/browse/HBASE-8446
Project: HBase
Issue Type: Improvement
Components: snapshots
Affects Versions: 0.95.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
Fix For: 0.95.2
Attachments: HBASE-8446-94.patch, HBASE-8446-v0.patch,
HBASE-8446-v1.patch, HBASE-8446-v2.patch, HBASE-8446-v3.patch,
HBASE-8446-v4.patch
currently only one snapshot at the time is allowed.
Like for the restore, we should allow taking snapshot of different tables in
parallel.
--
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-8460) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues
[ https://issues.apache.org/jira/browse/HBASE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646233#comment-13646233 ] Sergey Shelukhin commented on HBASE-8460: - +1, will commit after QA runs [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues Key: HBASE-8460 URL: https://issues.apache.org/jira/browse/HBASE-8460 Project: HBase Issue Type: Bug Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Priority: Minor Fix For: 0.95.1 Attachments: HBASE-8460-trunk-v1.patch, HBASE-8460-trunk-v2.patch There are three TODO's in TestReplicationStateBasic.testReplicationQueues. 1. Possible NPE when getLogPosition is called on a Bogus HLog file. 2. The assertion that tested setting a log position on a bogus file was commented out. 3. When claimQueues is given the regionserver znode for itself, it will try to copy its own queues. -- 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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646236#comment-13646236
]
Sergey Shelukhin commented on HBASE-8472:
-
Looks reasonable... there are tabs in the patch
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-7680) implement compaction policy for stripe compactions
[
https://issues.apache.org/jira/browse/HBASE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646250#comment-13646250
]
Hadoop QA commented on HBASE-7680:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581270/HBASE-7680-v8-with-7679.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 22 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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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/5511//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5511//console
This message is automatically generated.
implement compaction policy for stripe compactions
--
Key: HBASE-7680
URL: https://issues.apache.org/jira/browse/HBASE-7680
Project: HBase
Issue Type: Sub-task
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
Attachments: HBASE-7680-v0.patch, HBASE-7680-v1.patch,
HBASE-7680-v1-with-7679.patch, HBASE-7680-v2.patch,
HBASE-7680-v2-with-7679-and-8034.patch, HBASE-7680-v3.patch,
HBASE-7680-v3-with-7679.patch, HBASE-7680-v4.patch,
HBASE-7680-v4-with-7679.patch, HBASE-7680-v5.patch,
HBASE-7680-v5-with-7679.patch, HBASE-7680-v6.patch,
HBASE-7680-v6-with-7679.patch, HBASE-7680-v7.patch, HBASE-7680-v8.patch,
HBASE-7680-v8-with-7679.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-6295) Possible performance improvement in client batch operations: presplit and send in background
[
https://issues.apache.org/jira/browse/HBASE-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646260#comment-13646260
]
Sergey Shelukhin commented on HBASE-6295:
-
There are some nits in the patch that I won't go thru for now since it's not
complete.
Lots of the code seems to be copied from other parts of HCM, and the original
is not removed, will it be removed? Otherwise there's duplication.
Also, what happens to rows that are not added in AsyncProcess::submit? Not
clear on that
Possible performance improvement in client batch operations: presplit and
send in background
Key: HBASE-6295
URL: https://issues.apache.org/jira/browse/HBASE-6295
Project: HBase
Issue Type: Improvement
Components: Client, Performance
Affects Versions: 0.95.2
Reporter: Nicolas Liochon
Assignee: Nicolas Liochon
Labels: noob
Attachments: 6295.v1.patch, 6295.v2.patch, 6295.v3.patch,
6295.v4.patch, 6295.v5.patch
today batch algo is:
{noformat}
for Operation o: ListOp{
add o to todolist
if todolist maxsize or o last in list
split todolist per location
send split lists to region servers
clear todolist
wait
}
{noformat}
We could:
- create immediately the final object instead of an intermediate array
- split per location immediately
- instead of sending when the list as a whole is full, send it when there is
enough data for a single location
It would be:
{noformat}
for Operation o: ListOp{
get location
add o to todo location.todolist
if (location.todolist maxLocationSize)
send location.todolist to region server
clear location.todolist
// don't wait, continue the loop
}
send remaining
wait
{noformat}
It's not trivial to write if you add error management: retried list must be
shared with the operations added in the todolist. But it's doable.
It's interesting mainly for 'big' writes
--
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-8272) make compaction checker frequency configurable per table/cf
[
https://issues.apache.org/jira/browse/HBASE-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646263#comment-13646263
]
Hadoop QA commented on HBASE-8272:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581197/HBASE-8272-addendum.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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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:red}-1 lineLengths{color}. The patch introduces 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/5512//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5512//console
This message is automatically generated.
make compaction checker frequency configurable per table/cf
---
Key: HBASE-8272
URL: https://issues.apache.org/jira/browse/HBASE-8272
Project: HBase
Issue Type: Improvement
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
Priority: Minor
Attachments: HBASE-8272-addendum.patch, HBASE-8272-v0.patch,
HBASE-8272-v1.patch, HBASE-8272-v2.patch, HBASE-8272-v2.patch,
HBASE-8272-v3.patch
Makes the compaction checker frequency configurable per table/cf; that is
useful for compaction schemes where many compactions can be available at any
time, so the default checks/requests that HBase performs may be insufficient.
--
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-8473) add note to ref guide about snapshots and ec2 reverse dns requirements.
Jonathan Hsieh created HBASE-8473:
-
Summary: add note to ref guide about snapshots and ec2 reverse dns
requirements.
Key: HBASE-8473
URL: https://issues.apache.org/jira/browse/HBASE-8473
Project: HBase
Issue Type: Bug
Components: documentation, snapshots
Affects Versions: 0.95.0, 0.94.6.1, 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
From IRC from mighty Jeremy Carroll.
{code}
17:10 jeremy_carroll jmhsieh: I think I found the root cuase. All my region
servers reach the barrier, but it does not continue.
17:11 jeremy_carroll jmhsieh: All RS have this in their logs: 2013-05-01
00:04:56,356 DEBUG org.apache.hadoop.hbase.procedure.Subprocedure: Subprocedure
'backup1' coordinator notified of 'acquire', waiting on 'reached' or 'abort'
from coordinator.
17:11 jeremy_carroll jmhsieh: Then the coordinator (Master) never sends
anything. They just sit until the timeout.
17:12 jeremy_carroll jmhsieh: So basically 'reached' is never obtained. Then
abort it set, and it fails.
...
17:24 jeremy_carroll jmhsieh: Found the bug. The hostnames dont match the
master due to DNS resolution
17:25 jeremy_carroll jmhsieh: The barrier aquired is putting in the local
hostname from the regionservers. In EC2 (Where reverse DNS does not work well),
the master hands the internal name to the client.
17:25 jeremy_carroll jmhsieh:
https://s3.amazonaws.com/uploads.hipchat.com/23947/185789/au94meik0h3y5ii/Screen%20Shot%202013-04-30%20at%2017.25.50.png
17:26 jeremy_carroll jmhsieh: So it's waiting for something like
'ip-10-155-208-202.ec2.internal,60020,1367366580066' zNode to show up, but
instead 'hbasemetaclustera-d1b0a484,60020,1367366580066,' is being inserted.
Barrier is not reached
17:27 jeremy_carroll jmhsieh: Reason being in our environment the master does
not have a reverse DNS entry. So we get stuff like this on RegionServer startup
in our logs.
17:27 jeremy_carroll jmhsieh: 2013-05-01 00:03:00,614 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Master passed us hostname
to use. Was=hbasemetaclustera-d1b0a484, Now=ip-10-155-208-202.ec2.internal
17:54 jeremy_carroll jmhsieh: That was it. Verified. Now that Reverse DNS is
working, snapshots are working. Now how to figure out how to get Reverse DNS
working on Route53. I wished there was something like 'slave.host.name' inside
of Hadoop for this. Looking at source code.
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8472:
--
Attachment: hbase-8472.v2.patch
Replaced tabs with spaces.
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8472:
--
Attachment: (was: hbase-8472.v2.patch)
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8472:
--
Attachment: hbase-8472.v2.patch
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8469) [hadoop2] Several tests break because of HDFS-4305
[
https://issues.apache.org/jira/browse/HBASE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8469:
--
Attachment: hbase-8469.patch
[hadoop2] Several tests break because of HDFS-4305
--
Key: HBASE-8469
URL: https://issues.apache.org/jira/browse/HBASE-8469
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.98.0, 0.94.6.1, 0.95.0
Reporter: Jonathan Hsieh
Attachments: hbase-8469.patch
Several unit tests will break due to HDFS-4305 (which enforces a min block
size) because apprently, we set our block size smaller in these tests.
{code}
Specified block size is less than configured minimum value
(dfs.namenode.fs-limits.min-block-size): 1024 1048576
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1816)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1795)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:418)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:205)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44134)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1696)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1692)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1690)
{code}
org.apache.hadoop.hbase.regionserver.TestHRegion.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.replication.TestMasterReplication.testCyclicReplication
org.apache.hadoop.hbase.replication.TestMasterReplication.testSimplePutDelete
org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication
org.apache.hadoop.hbase.util.TestFSUtils.testcomputeHDFSBlocksDistribution
--
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-8469) [hadoop2] Several tests break because of HDFS-4305
[
https://issues.apache.org/jira/browse/HBASE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8469:
--
Fix Version/s: 0.95.1
0.94.8
0.98.0
Status: Patch Available (was: Open)
[hadoop2] Several tests break because of HDFS-4305
--
Key: HBASE-8469
URL: https://issues.apache.org/jira/browse/HBASE-8469
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0, 0.94.6.1, 0.98.0
Reporter: Jonathan Hsieh
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: hbase-8469.patch
Several unit tests will break due to HDFS-4305 (which enforces a min block
size) because apprently, we set our block size smaller in these tests.
{code}
Specified block size is less than configured minimum value
(dfs.namenode.fs-limits.min-block-size): 1024 1048576
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1816)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1795)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:418)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:205)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44134)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1696)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1692)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1690)
{code}
org.apache.hadoop.hbase.regionserver.TestHRegion.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.replication.TestMasterReplication.testCyclicReplication
org.apache.hadoop.hbase.replication.TestMasterReplication.testSimplePutDelete
org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication
org.apache.hadoop.hbase.util.TestFSUtils.testcomputeHDFSBlocksDistribution
--
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] [Assigned] (HBASE-8469) [hadoop2] Several tests break because of HDFS-4305
[
https://issues.apache.org/jira/browse/HBASE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-8469:
-
Assignee: Jonathan Hsieh
[hadoop2] Several tests break because of HDFS-4305
--
Key: HBASE-8469
URL: https://issues.apache.org/jira/browse/HBASE-8469
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.98.0, 0.94.6.1, 0.95.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: hbase-8469.patch
Several unit tests will break due to HDFS-4305 (which enforces a min block
size) because apprently, we set our block size smaller in these tests.
{code}
Specified block size is less than configured minimum value
(dfs.namenode.fs-limits.min-block-size): 1024 1048576
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1816)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1795)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:418)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:205)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44134)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1696)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1692)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1690)
{code}
org.apache.hadoop.hbase.regionserver.TestHRegion.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.replication.TestMasterReplication.testCyclicReplication
org.apache.hadoop.hbase.replication.TestMasterReplication.testSimplePutDelete
org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication
org.apache.hadoop.hbase.util.TestFSUtils.testcomputeHDFSBlocksDistribution
--
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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8472:
--
Status: Patch Available (was: Open)
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646279#comment-13646279
]
Sergey Shelukhin commented on HBASE-8472:
-
+1
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8474) there are dups in hadoop2 pom
Sergey Shelukhin created HBASE-8474: --- Summary: there are dups in hadoop2 pom Key: HBASE-8474 URL: https://issues.apache.org/jira/browse/HBASE-8474 Project: HBase Issue Type: Bug Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Trivial -- 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-8474) there are dups in hadoop2 pom
[ https://issues.apache.org/jira/browse/HBASE-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-8474: Attachment: HBASE-8474-v0.patch there are dups in hadoop2 pom - Key: HBASE-8474 URL: https://issues.apache.org/jira/browse/HBASE-8474 Project: HBase Issue Type: Bug Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Trivial Attachments: HBASE-8474-v0.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-8474) there are dups in hadoop2 pom
[ https://issues.apache.org/jira/browse/HBASE-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-8474: Status: Patch Available (was: Open) there are dups in hadoop2 pom - Key: HBASE-8474 URL: https://issues.apache.org/jira/browse/HBASE-8474 Project: HBase Issue Type: Bug Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Trivial Attachments: HBASE-8474-v0.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-8469) [hadoop2] Several tests break because of HDFS-4305
[
https://issues.apache.org/jira/browse/HBASE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646284#comment-13646284
]
Jonathan Hsieh commented on HBASE-8469:
---
After HBASE-8472 is applied so that we can properly run tests against hadoop
2.0.5-SNAPSHOT, we get this before the patch applied:
{code}
~/proj/hbase$ mvn clean test -Dhadoop.profile=2.0
-Dhadoop-two.version=2.0.5-SNAPSHOT
-Dtest=TestHRegion*,Test*Replication,TestFSUtils
---
Running org.apache.hadoop.hbase.regionserver.TestHRegion
Tests run: 62, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 20.811 sec
FAILURE!
Running org.apache.hadoop.hbase.replication.TestMasterReplication
... (takes a very long time, canceled) ...
---
T E S T S
---
Running org.apache.hadoop.hbase.TestHRegionLocation
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.435 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegion
Tests run: 62, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 19.571 sec
FAILURE!
Running org.apache.hadoop.hbase.regionserver.TestHRegionOnCluster
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.669 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoad
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 38.514 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionInfo
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.629 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait
Tests run: 63, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 20.729 sec
FAILURE!
Running org.apache.hadoop.hbase.regionserver.TestHRegionFileSystem
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.29 sec
Running org.apache.hadoop.hbase.replication.TestMasterReplication
... (hanging or taking way too long).
{code}
and this after
{code}
~/proj/hbase$ mvn clean test -Dhadoop.profile=2.0
-Dhadoop-two.version=2.0.5-SNAPSHOT
-Dtest=TestHRegion*,Test*Replication,TestFSUtils
---
T E S T S
---
Running org.apache.hadoop.hbase.TestHRegionLocation
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.476 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegion
Tests run: 62, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.415 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionOnCluster
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.749 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoad
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 39.33 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionInfo
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.515 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait
Tests run: 63, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.96 sec
Running org.apache.hadoop.hbase.regionserver.TestHRegionFileSystem
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.215 sec
Running org.apache.hadoop.hbase.replication.TestMasterReplication
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.998 sec
Running org.apache.hadoop.hbase.replication.TestMultiSlaveReplication
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.739 sec
Running org.apache.hadoop.hbase.util.TestFSUtils
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.387 sec
{code}
[hadoop2] Several tests break because of HDFS-4305
--
Key: HBASE-8469
URL: https://issues.apache.org/jira/browse/HBASE-8469
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.98.0, 0.94.6.1, 0.95.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: hbase-8469.patch
Several unit tests will break due to HDFS-4305 (which enforces a min block
size) because apprently, we set our block size smaller in these tests.
{code}
Specified block size is less than configured minimum value
(dfs.namenode.fs-limits.min-block-size): 1024 1048576
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1816)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1795)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:418)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:205)
at
[jira] [Commented] (HBASE-8474) there are dups in hadoop2 pom
[ https://issues.apache.org/jira/browse/HBASE-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646286#comment-13646286 ] Jonathan Hsieh commented on HBASE-8474: --- +1, lgtm. there are dups in hadoop2 pom - Key: HBASE-8474 URL: https://issues.apache.org/jira/browse/HBASE-8474 Project: HBase Issue Type: Bug Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Trivial Attachments: HBASE-8474-v0.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-8469) [hadoop2] Several tests break because of HDFS-4305
[
https://issues.apache.org/jira/browse/HBASE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646288#comment-13646288
]
Jonathan Hsieh commented on HBASE-8469:
---
in the patch, I essentially programmatically set the config value to 0 in the
testing cluster's config.
[hadoop2] Several tests break because of HDFS-4305
--
Key: HBASE-8469
URL: https://issues.apache.org/jira/browse/HBASE-8469
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.98.0, 0.94.6.1, 0.95.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: hbase-8469.patch
Several unit tests will break due to HDFS-4305 (which enforces a min block
size) because apprently, we set our block size smaller in these tests.
{code}
Specified block size is less than configured minimum value
(dfs.namenode.fs-limits.min-block-size): 1024 1048576
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1816)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1795)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:418)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:205)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44134)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1696)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1692)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1690)
{code}
org.apache.hadoop.hbase.regionserver.TestHRegion.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait.testgetHDFSBlocksDistribution
org.apache.hadoop.hbase.replication.TestMasterReplication.testCyclicReplication
org.apache.hadoop.hbase.replication.TestMasterReplication.testSimplePutDelete
org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication
org.apache.hadoop.hbase.util.TestFSUtils.testcomputeHDFSBlocksDistribution
--
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-8470) Data file used by TestReference should be excluded from Apache Rat check
[ https://issues.apache.org/jira/browse/HBASE-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-8470: -- Description: The following was discovered by Matteo: hbase-server/src/test/data/a6a6562b777440fd9c34885428f5cb61.21e75333ada3d5bafb34bb918f29576c is used by TestReference to verify the format compatibility. We should exclude this file from Apache Rat check. was: hbase-server/src/test/data/a6a6562b777440fd9c34885428f5cb61.21e75333ada3d5bafb34bb918f29576c is used by TestReference to verify the format compatibility. We should exclude this file from Apache Rat check. Data file used by TestReference should be excluded from Apache Rat check Key: HBASE-8470 URL: https://issues.apache.org/jira/browse/HBASE-8470 Project: HBase Issue Type: Improvement Reporter: Ted Yu Assignee: Ted Yu Attachments: 8470.txt The following was discovered by Matteo: hbase-server/src/test/data/a6a6562b777440fd9c34885428f5cb61.21e75333ada3d5bafb34bb918f29576c is used by TestReference to verify the format compatibility. We should exclude this file from Apache Rat check. -- 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-8470) Data file used by TestReference should be excluded from Apache Rat check
[ https://issues.apache.org/jira/browse/HBASE-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-8470: -- Fix Version/s: 0.95.1 0.98.0 Hadoop Flags: Reviewed Data file used by TestReference should be excluded from Apache Rat check Key: HBASE-8470 URL: https://issues.apache.org/jira/browse/HBASE-8470 Project: HBase Issue Type: Improvement Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.98.0, 0.95.1 Attachments: 8470.txt The following was discovered by Matteo: hbase-server/src/test/data/a6a6562b777440fd9c34885428f5cb61.21e75333ada3d5bafb34bb918f29576c is used by TestReference to verify the format compatibility. We should exclude this file from Apache Rat check. -- 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-8369) MapReduce over snapshot files
[ https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646295#comment-13646295 ] Enis Soztutar commented on HBASE-8369: -- Thanks for looking. This will correspond to the skeleton of the final patch. I want to add more testing and address the TODO's in the patch. But reviews are always welcome in any phase. MapReduce over snapshot files - Key: HBASE-8369 URL: https://issues.apache.org/jira/browse/HBASE-8369 Project: HBase Issue Type: New Feature Components: mapreduce, snapshots Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 0.98.0, 0.95.2 Attachments: hbase-8369_v0.patch The idea is to add an InputFormat, which can run the mapreduce job over snapshot files directly bypassing hbase server layer. The IF is similar in usage to TableInputFormat, taking a Scan object from the user, but instead of running from an online table, it runs from a table snapshot. We do one split per region in the snapshot, and open an HRegion inside the RecordReader. A RegionScanner is used internally for doing the scan without any HRegionServer bits. Users have been asking and searching for ways to run MR jobs by reading directly from hfiles, so this allows new use cases if reading from stale data is ok: - Take snapshots periodically, and run MR jobs only on snapshots. - Export snapshots to remote hdfs cluster, run the MR jobs at that cluster without HBase cluster. - (Future use case) Combine snapshot data with online hbase data: Scan from yesterday's snapshot, but read today's data from online hbase cluster. -- 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-8338) Latency Resilience; umbrella list of issues that will help us ride over bad disk, bad region, ec2, etc.
[ https://issues.apache.org/jira/browse/HBASE-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646296#comment-13646296 ] Enis Soztutar commented on HBASE-8338: -- Related, there is this idea of opening two wal writers, and switching to the other one, if we run into slowness, which is mentioned in the Bigtable paper. Do we have a jira for something similar? It might be addressed at multi-wal as well. Latency Resilience; umbrella list of issues that will help us ride over bad disk, bad region, ec2, etc. --- Key: HBASE-8338 URL: https://issues.apache.org/jira/browse/HBASE-8338 Project: HBase Issue Type: Umbrella Components: LatencyResilience Reporter: stack Priority: Critical Chatting w/ Elliott, we started listing out items to fix that would help keep hbase latency approximately constant as disks went bad, were saturated by a neighbour (ec2), etc. I must made a new LatencyResilience issue category to tag issues that contribute to this project. I have to go at moment but when I get back I'll start to link in existing issues that help this project along and I'll file new ones. Here is what we chatted about: + Multiple WALs effort will help keep write latency roughly constant. + Figuring how to get a new read started over dfsclient if current replica read is taking too long would help keep reads about constant (maybe could exploit the nkeywal hackery messing w/ replicas order). + There is an issue where client can currently pile up on a single region because of the way we do client queues by regionserver. This needs fixing. The above are few ideas worth further exploration at least. Idea is to try and bring down our 95percentiles and to make us more robust in the face of dying disks, etc. I see this issue rising to the fore now there has been good progress on the MTTR project. -- 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-8460) [replication] Fix the three TODOs in TestReplicationStateBasic.testReplicationQueues
[
https://issues.apache.org/jira/browse/HBASE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646316#comment-13646316
]
Hadoop QA commented on HBASE-8460:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581281/HBASE-8460-trunk-v2.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 6 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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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/5513//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5513//console
This message is automatically generated.
[replication] Fix the three TODOs in
TestReplicationStateBasic.testReplicationQueues
Key: HBASE-8460
URL: https://issues.apache.org/jira/browse/HBASE-8460
Project: HBase
Issue Type: Bug
Components: Replication
Reporter: Chris Trezzo
Assignee: Chris Trezzo
Priority: Minor
Fix For: 0.95.1
Attachments: HBASE-8460-trunk-v1.patch, HBASE-8460-trunk-v2.patch
There are three TODO's in TestReplicationStateBasic.testReplicationQueues.
1. Possible NPE when getLogPosition is called on a Bogus HLog file.
2. The assertion that tested setting a log position on a bogus file was
commented out.
3. When claimQueues is given the regionserver znode for itself, it will try
to copy its own queues.
--
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-8468) IntegrationTestImportTsv fails on a cluster
[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646324#comment-13646324
]
Hudson commented on HBASE-8468:
---
Integrated in hbase-0.95 #170 (See
[https://builds.apache.org/job/hbase-0.95/170/])
HBASE-8468 IntegrationTestImportTsv fails on a cluster (Revision 1477878)
Result = SUCCESS
eclark :
Files :
*
/hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestImportTsv.java
IntegrationTestImportTsv fails on a cluster
---
Key: HBASE-8468
URL: https://issues.apache.org/jira/browse/HBASE-8468
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 0.98.0, 0.95.1
Attachments: HBASE-8468-0.patch, HBASE-8468-1.patch
It appears that the JobLaunchingOuputCommitter is not properly picking up the
configuration.
the quorum is set in the job conf when I look at it in the yarn mr history
manager. However as you can see below the zk session is still defaulting to
127.0.0.1
{code}
2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
org.apache.zookeeper.ClientCnxn: Opening socket connection to server
/127.0.0.1:2181
2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
this process is hconnection-0x1704de3e
2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
ZooKeeper, quorum=localhost:2181,
exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
2013-04-30 10:18:54,847 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.util.RetryCounter: Sleeping 2000ms before retry #1...
2013-04-30 10:18:54,882 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before
Scheduling: PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0
AssignedReds:1 CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0
HostLocal:0 RackLocal:1
2013-04-30 10:18:55,839 INFO [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Opening
socket connection to server localhost/127.0.0.1:2181
2013-04-30 10:18:55,840 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:55,887 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Received
completed container container_1367340870656_0004_01_03
2013-04-30 10:18:55,888 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: After Scheduling:
PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0 AssignedReds:0
CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0 HostLocal:0 RackLocal:1
2013-04-30 10:18:55,888 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics
report from attempt_1367340870656_0004_r_00_0: Container killed by the
ApplicationMaster.
{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-7413) Convert WAL to pb
[ https://issues.apache.org/jira/browse/HBASE-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646325#comment-13646325 ] Hudson commented on HBASE-7413: --- Integrated in hbase-0.95 #170 (See [https://builds.apache.org/job/hbase-0.95/170/]) HBASE-7413 Convert WAL to pb (Revision 1477762) Result = SUCCESS sershe : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/codec/KeyValueCodec.java * /hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/AdminProtos.java * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/HBaseProtos.java * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/WAL.java * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/WALProtos.java * /hbase/branches/0.95/hbase-protocol/src/main/protobuf/Admin.proto * /hbase/branches/0.95/hbase-protocol/src/main/protobuf/WAL.proto * /hbase/branches/0.95/hbase-protocol/src/main/protobuf/hbase.proto * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/ReplicationProtbufUtil.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/HStore.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/Compressor.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/regionserver/wal/HLog.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogFactory.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogKey.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogUtil.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/KeyValueCompression.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogReader.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogWriter.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ReaderBase.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogReader.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALCellCodec.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALEdit.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHLogRecordReader.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/FaultySequenceFileLogReader.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/InstrumentedSequenceFileLogWriter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLogSplit.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestWALActionsListener.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestWALReplay.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java Convert WAL to pb - Key: HBASE-7413 URL: https://issues.apache.org/jira/browse/HBASE-7413 Project: HBase Issue Type: Sub-task Components: wal Reporter: stack
[jira] [Commented] (HBASE-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646338#comment-13646338
]
Enis Soztutar commented on HBASE-8472:
--
This worked for me. +1.
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-7567) [replication] Create an interface for replication peers
[ https://issues.apache.org/jira/browse/HBASE-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated HBASE-7567: Attachment: HBASE-7567-trunk-95-v3.patch V3 patch posted addressing [~jdcryans]'s comments on RB. Updated review posted as well. [replication] Create an interface for replication peers --- Key: HBASE-7567 URL: https://issues.apache.org/jira/browse/HBASE-7567 Project: HBase Issue Type: Improvement Components: Replication Reporter: Chris Trezzo Assignee: Chris Trezzo Fix For: 0.95.1 Attachments: HBASE-7567-trunk-95-v1.patch, HBASE-7567-trunk-95-v2.patch, HBASE-7567-trunk-95-v3.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-8468) IntegrationTestImportTsv fails on a cluster
[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646344#comment-13646344
]
Hudson commented on HBASE-8468:
---
Integrated in HBase-TRUNK #4088 (See
[https://builds.apache.org/job/HBase-TRUNK/4088/])
HBASE-8468 IntegrationTestImportTsv fails on a cluster (Revision 1477877)
Result = FAILURE
eclark :
Files :
*
/hbase/trunk/hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestImportTsv.java
IntegrationTestImportTsv fails on a cluster
---
Key: HBASE-8468
URL: https://issues.apache.org/jira/browse/HBASE-8468
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 0.98.0, 0.95.1
Attachments: HBASE-8468-0.patch, HBASE-8468-1.patch
It appears that the JobLaunchingOuputCommitter is not properly picking up the
configuration.
the quorum is set in the job conf when I look at it in the yarn mr history
manager. However as you can see below the zk session is still defaulting to
127.0.0.1
{code}
2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
org.apache.zookeeper.ClientCnxn: Opening socket connection to server
/127.0.0.1:2181
2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
this process is hconnection-0x1704de3e
2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
ZooKeeper, quorum=localhost:2181,
exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
2013-04-30 10:18:54,847 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.util.RetryCounter: Sleeping 2000ms before retry #1...
2013-04-30 10:18:54,882 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before
Scheduling: PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0
AssignedReds:1 CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0
HostLocal:0 RackLocal:1
2013-04-30 10:18:55,839 INFO [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Opening
socket connection to server localhost/127.0.0.1:2181
2013-04-30 10:18:55,840 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:55,887 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Received
completed container container_1367340870656_0004_01_03
2013-04-30 10:18:55,888 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: After Scheduling:
PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0 AssignedReds:0
CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0 HostLocal:0 RackLocal:1
2013-04-30 10:18:55,888 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics
report from attempt_1367340870656_0004_r_00_0: Container killed by the
ApplicationMaster.
{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-7413) Convert WAL to pb
[ https://issues.apache.org/jira/browse/HBASE-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646345#comment-13646345 ] Hudson commented on HBASE-7413: --- Integrated in HBase-TRUNK #4088 (See [https://builds.apache.org/job/HBase-TRUNK/4088/]) HBASE-7413 Convert WAL to pb (Revision 1477761) Result = FAILURE sershe : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/codec/KeyValueCodec.java * /hbase/trunk/hbase-common/src/main/resources/hbase-default.xml * /hbase/trunk/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/AdminProtos.java * /hbase/trunk/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/HBaseProtos.java * /hbase/trunk/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/WAL.java * /hbase/trunk/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/WALProtos.java * /hbase/trunk/hbase-protocol/src/main/protobuf/Admin.proto * /hbase/trunk/hbase-protocol/src/main/protobuf/WAL.proto * /hbase/trunk/hbase-protocol/src/main/protobuf/hbase.proto * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/ReplicationProtbufUtil.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/HStore.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/Compressor.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/regionserver/wal/HLog.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogFactory.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogKey.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogUtil.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/KeyValueCompression.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogReader.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogWriter.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ReaderBase.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogReader.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALCellCodec.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALEdit.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHLogRecordReader.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/FaultySequenceFileLogReader.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/InstrumentedSequenceFileLogWriter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLogSplit.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestWALActionsListener.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestWALReplay.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java Convert WAL to pb - Key: HBASE-7413 URL: https://issues.apache.org/jira/browse/HBASE-7413 Project: HBase Issue Type: Sub-task Components: wal Reporter: stack Assignee: Sergey Shelukhin Priority: Critical Fix For: 0.95.1 Attachments: HBASE-7413-v0.patch, HBASE-7413-v1.patch, HBASE-7413-v2.patch, HBASE-7413-v3.patch, HBASE-7413-v4.patch, HBASE-7413-v5.patch From HBASE-7201 -- This message is automatically generated by JIRA. If you think
[jira] [Commented] (HBASE-8474) there are dups in hadoop2 pom
[
https://issues.apache.org/jira/browse/HBASE-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646355#comment-13646355
]
Hadoop QA commented on HBASE-8474:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581319/HBASE-8474-v0.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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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:
org.apache.hadoop.hbase.util.TestHBaseFsck
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5514//console
This message is automatically generated.
there are dups in hadoop2 pom
-
Key: HBASE-8474
URL: https://issues.apache.org/jira/browse/HBASE-8474
Project: HBase
Issue Type: Bug
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
Priority: Trivial
Attachments: HBASE-8474-v0.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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-8472:
--
Resolution: Fixed
Fix Version/s: 0.95.1
0.98.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.98.0, 0.95.1
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646366#comment-13646366
]
Jonathan Hsieh commented on HBASE-8472:
---
Thanks for trying enis + sergey. Committed to 0.95 and trunk. 0.94 branch
didn't need it.
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646370#comment-13646370
]
Hadoop QA commented on HBASE-8472:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581310/hbase-8472.v2.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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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 2 zombie test(s):
at
org.apache.hadoop.hbase.master.handler.TestCreateTableHandler.testMasterRestartAfterEnablingNodeIsCreated(TestCreateTableHandler.java:113)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5515//console
This message is automatically generated.
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.98.0, 0.95.1
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{code}
[jira] [Commented] (HBASE-8469) [hadoop2] Several tests break because of HDFS-4305
[
https://issues.apache.org/jira/browse/HBASE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646380#comment-13646380
]
Hadoop QA commented on HBASE-8469:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581317/hbase-8469.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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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:
org.apache.hadoop.hbase.util.TestHBaseFsck
org.apache.hadoop.hbase.master.TestOpenedRegionHandler
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5516//console
This message is automatically generated.
[hadoop2] Several tests break because of HDFS-4305
--
Key: HBASE-8469
URL: https://issues.apache.org/jira/browse/HBASE-8469
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.98.0, 0.94.6.1, 0.95.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: hbase-8469.patch
Several unit tests will break due to HDFS-4305 (which enforces a min block
size) because apprently, we set our block size smaller in these tests.
{code}
Specified block size is less than configured minimum value
(dfs.namenode.fs-limits.min-block-size): 1024 1048576
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1816)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1795)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:418)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:205)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44134)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1696)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1692)
at java.security.AccessController.doPrivileged(Native Method)
at
[jira] [Commented] (HBASE-8468) IntegrationTestImportTsv fails on a cluster
[
https://issues.apache.org/jira/browse/HBASE-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646384#comment-13646384
]
Hudson commented on HBASE-8468:
---
Integrated in hbase-0.95-on-hadoop2 #86 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/86/])
HBASE-8468 IntegrationTestImportTsv fails on a cluster (Revision 1477878)
Result = FAILURE
eclark :
Files :
*
/hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestImportTsv.java
IntegrationTestImportTsv fails on a cluster
---
Key: HBASE-8468
URL: https://issues.apache.org/jira/browse/HBASE-8468
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 0.95.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 0.98.0, 0.95.1
Attachments: HBASE-8468-0.patch, HBASE-8468-1.patch
It appears that the JobLaunchingOuputCommitter is not properly picking up the
configuration.
the quorum is set in the job conf when I look at it in the yarn mr history
manager. However as you can see below the zk session is still defaulting to
127.0.0.1
{code}
2013-04-30 10:18:54,728 INFO [CommitterEvent Processor #1-SendThread()]
org.apache.zookeeper.ClientCnxn: Opening socket connection to server
/127.0.0.1:2181
2013-04-30 10:18:54,729 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of
this process is hconnection-0x1704de3e
2013-04-30 10:18:54,731 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:54,847 WARN [CommitterEvent Processor #1]
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient
ZooKeeper, quorum=localhost:2181,
exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
2013-04-30 10:18:54,847 INFO [CommitterEvent Processor #1]
org.apache.hadoop.hbase.util.RetryCounter: Sleeping 2000ms before retry #1...
2013-04-30 10:18:54,882 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before
Scheduling: PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0
AssignedReds:1 CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0
HostLocal:0 RackLocal:1
2013-04-30 10:18:55,839 INFO [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Opening
socket connection to server localhost/127.0.0.1:2181
2013-04-30 10:18:55,840 WARN [CommitterEvent Processor
#1-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn: Session 0x0
for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1041)
2013-04-30 10:18:55,887 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Received
completed container container_1367340870656_0004_01_03
2013-04-30 10:18:55,888 INFO [RMCommunicator Allocator]
org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: After Scheduling:
PendingReds:0 ScheduledMaps:0 ScheduledReds:0 AssignedMaps:0 AssignedReds:0
CompletedMaps:1 CompletedReds:1 ContAlloc:2 ContRel:0 HostLocal:0 RackLocal:1
2013-04-30 10:18:55,888 INFO [AsyncDispatcher event handler]
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics
report from attempt_1367340870656_0004_r_00_0: Container killed by the
ApplicationMaster.
{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-8472) mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of Undef Class error wrt o.a.h.IdGenerator
[
https://issues.apache.org/jira/browse/HBASE-8472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646385#comment-13646385
]
Hudson commented on HBASE-8472:
---
Integrated in hbase-0.95-on-hadoop2 #86 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/86/])
HBASE-8472 mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT
fails because of Undef Class error wrt o.a.h.IdGenerator (Revision 1477909)
Result = FAILURE
jmhsieh :
Files :
* /hbase/branches/0.95/pom.xml
mvn -Dhadoop.profile=2.0 -Dhadoop-two.version=2.0.5-SNAPSHOT fails because of
Undef Class error wrt o.a.h.IdGenerator
-
Key: HBASE-8472
URL: https://issues.apache.org/jira/browse/HBASE-8472
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.98.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.98.0, 0.95.1
Attachments: hbase-8472.patch, hbase-8472.v2.patch
{code}
testcase time=1.009
classname=org.apache.hadoop.hbase.replication.TestMasterReplication
name=testCyclicReplication
error message=org/apache/hadoop/util/IdGenerator
type=java.lang.NoClassDefFoundErrorjava.lang.NoClassDefFoundError:
org/apache/hadoop/util/IdGenerator
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:752)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:261)
at
org.apache.hadoop.hdfs.DFSTestUtil.formatNameNode(DFSTestUtil.java:146)
at
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:775)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:642)
at
org.apache.hadoop.hdfs.MiniDFSCluster.lt;initgt;(MiniDFSCluster.java:585)
{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-7413) Convert WAL to pb
[ https://issues.apache.org/jira/browse/HBASE-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646386#comment-13646386 ] Hudson commented on HBASE-7413: --- Integrated in hbase-0.95-on-hadoop2 #86 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/86/]) HBASE-7413 Convert WAL to pb (Revision 1477762) Result = FAILURE sershe : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/codec/KeyValueCodec.java * /hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/AdminProtos.java * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/HBaseProtos.java * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/WAL.java * /hbase/branches/0.95/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/WALProtos.java * /hbase/branches/0.95/hbase-protocol/src/main/protobuf/Admin.proto * /hbase/branches/0.95/hbase-protocol/src/main/protobuf/WAL.proto * /hbase/branches/0.95/hbase-protocol/src/main/protobuf/hbase.proto * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/ReplicationProtbufUtil.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/HStore.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/Compressor.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/regionserver/wal/HLog.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogFactory.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogKey.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogUtil.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/KeyValueCompression.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogReader.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogWriter.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ReaderBase.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogReader.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALCellCodec.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALEdit.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/Replication.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHLogRecordReader.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/FaultySequenceFileLogReader.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/InstrumentedSequenceFileLogWriter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLogSplit.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestWALActionsListener.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestWALReplay.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSourceManager.java Convert WAL to pb - Key: HBASE-7413 URL: https://issues.apache.org/jira/browse/HBASE-7413 Project: HBase Issue Type: Sub-task Components: wal Reporter: stack
[jira] [Commented] (HBASE-7567) [replication] Create an interface for replication peers
[
https://issues.apache.org/jira/browse/HBASE-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646388#comment-13646388
]
Hadoop QA commented on HBASE-7567:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581329/HBASE-7567-trunk-95-v3.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 12 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:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any 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:
org.apache.hadoop.hbase.security.token.TestZKSecretWatcher
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5517//console
This message is automatically generated.
[replication] Create an interface for replication peers
---
Key: HBASE-7567
URL: https://issues.apache.org/jira/browse/HBASE-7567
Project: HBase
Issue Type: Improvement
Components: Replication
Reporter: Chris Trezzo
Assignee: Chris Trezzo
Fix For: 0.95.1
Attachments: HBASE-7567-trunk-95-v1.patch,
HBASE-7567-trunk-95-v2.patch, HBASE-7567-trunk-95-v3.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-5995) Fix and reenable TestLogRolling.testLogRollOnPipelineRestart
[ https://issues.apache.org/jira/browse/HBASE-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646390#comment-13646390 ] Enis Soztutar commented on HBASE-5995: -- This still fails with 2.0.4-alpha. It seems that all the replicas are in state RWR, and we cannot get the length of the block while the replicas are waiting to be recovered. Will inspect more and share the results. Fix and reenable TestLogRolling.testLogRollOnPipelineRestart Key: HBASE-5995 URL: https://issues.apache.org/jira/browse/HBASE-5995 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 0.95.2 Reporter: stack Assignee: Enis Soztutar Priority: Blocker Fix For: 0.95.1 HBASE-5984 disabled this flakey test (See the issue for more). This issue is about getting it enabled again. Made a blocker on 0.96.0 so it gets attention. -- 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-4811) Support reverse Scan
[ https://issues.apache.org/jira/browse/HBASE-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646393#comment-13646393 ] Lars Hofhansl commented on HBASE-4811: -- If we wanted to have this backward compatible in 0.94 we would need to encode the reversed bit in the Scan's attributes... Or use a new scan version only reversed is true (so that an old regionserver would fail the scan request). Support reverse Scan Key: HBASE-4811 URL: https://issues.apache.org/jira/browse/HBASE-4811 Project: HBase Issue Type: Improvement Components: Client Affects Versions: 0.20.6 Reporter: John Carrino Attachments: HBase-4811-0.94.3modified.txt All the documentation I find about HBase says that if you want forward and reverse scans you should just build 2 tables and one be ascending and one descending. Is there a fundamental reason that HBase only supports forward Scan? It seems like a lot of extra space overhead and coding overhead (to keep them in sync) to support 2 tables. I am assuming this has been discussed before, but I can't find the discussions anywhere about it or why it would be infeasible. -- 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-7755) Experiment with LAB in BlockEndcoding
[ https://issues.apache.org/jira/browse/HBASE-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved HBASE-7755. -- Resolution: Won't Fix Marking as Won't fix as I have been unable to find a general heuristic that always improves performance. Experiment with LAB in BlockEndcoding - Key: HBASE-7755 URL: https://issues.apache.org/jira/browse/HBASE-7755 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Attachments: 7755-0.94-W_I_P_v1.txt, 7755-0.94-WORK_IN_PROGRESS.txt I was looking at and profiling the BlockEncoding code to figure out how to make it faster. One issue that jumped out was we call ByteBuffer.allocate(...) for each single KV. As an experiment I tried using the MemStoreLAB code to allocate those buffers. Here are some preliminary numbers, all scanning 10m rows (all in cache): * no encoding: 5.2s * FAST_DIFF without patch: 7.3s * FAST_DIFF with patch and small LAB: 4.1s * FAST_DIFF with patch and large LAB: 11s So this is very sensitive to the right sizing of the LAB. Need to do a bit more testing, but it seems that there is a chance to actually make scanning with block encoding faster than without! -- 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-6116) Allow parallel HDFS writes for HLogs.
[ https://issues.apache.org/jira/browse/HBASE-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-6116: - Assignee: (was: Lars Hofhansl) Allow parallel HDFS writes for HLogs. - Key: HBASE-6116 URL: https://issues.apache.org/jira/browse/HBASE-6116 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Attachments: 6116-v1.txt, apurtell-patches.zip, pipelined-vs-parallel-comparison.zip In HDFS-1783 I adapted Dhrubas changes to be used in Hadoop trunk. This issue will include the necessary reflection changes to optionally enable this for the WALs in HBase. -- 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-6116) Allow parallel HDFS writes for HLogs.
[ https://issues.apache.org/jira/browse/HBASE-6116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved HBASE-6116. -- Resolution: Won't Fix Closing. Feel free to reopen if you think there is merit in this. Allow parallel HDFS writes for HLogs. - Key: HBASE-6116 URL: https://issues.apache.org/jira/browse/HBASE-6116 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Attachments: 6116-v1.txt, apurtell-patches.zip, pipelined-vs-parallel-comparison.zip In HDFS-1783 I adapted Dhrubas changes to be used in Hadoop trunk. This issue will include the necessary reflection changes to optionally enable this for the WALs in HBase. -- 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-5930) Limits the amount of time an edit can live in the memstore.
[ https://issues.apache.org/jira/browse/HBASE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646397#comment-13646397 ] Lars Hofhansl commented on HBASE-5930: -- Should I close this one and open a 0.94 backport patch? Limits the amount of time an edit can live in the memstore. --- Key: HBASE-5930 URL: https://issues.apache.org/jira/browse/HBASE-5930 Project: HBase Issue Type: Improvement Reporter: Lars Hofhansl Assignee: Devaraj Das Fix For: 0.98.0, 0.94.8, 0.95.1 Attachments: 5930-0.94.txt, 5930-1.patch, 5930-2.1.patch, 5930-2.2.patch, 5930-2.3.patch, 5930-2.4.patch, 5930-track-oldest-sample.txt, 5930-wip.patch, HBASE-5930-ADD-0.patch, hbase-5930-addendum2.patch, hbase-5930-test-execution.log A colleague of mine ran into an interesting issue. He inserted some data with the WAL disabled, which happened to fit in the aggregate Memstores memory. Two weeks later he a had problem with the HDFS cluster, which caused the region servers to abort. He found that his data was lost. Looking at the log we found that the Memstores were not flushed at all during these two weeks. Should we have an option to flush memstores periodically. There are obvious downsides to this, like many small storefiles, etc. -- 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-5622) Improve efficiency of mapred vesion of RowCounter
[ https://issues.apache.org/jira/browse/HBASE-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved HBASE-5622. -- Resolution: Won't Fix Closing. Nobody seems to care. Improve efficiency of mapred vesion of RowCounter - Key: HBASE-5622 URL: https://issues.apache.org/jira/browse/HBASE-5622 Project: HBase Issue Type: Sub-task Reporter: Lars Hofhansl Priority: Minor -- 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-5923) Cleanup checkAndXXX logic
[
https://issues.apache.org/jira/browse/HBASE-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-5923:
-
Assignee: (was: Lars Hofhansl)
Removing myself for now.
Cleanup checkAndXXX logic
-
Key: HBASE-5923
URL: https://issues.apache.org/jira/browse/HBASE-5923
Project: HBase
Issue Type: Improvement
Components: Client, regionserver
Reporter: Lars Hofhansl
Priority: Critical
Fix For: 0.95.1
Attachments: 5923-0.94.txt, 5923-trunk.txt
1. the checkAnd{Put|Delete} method that takes a CompareOP is not exposed via
HTable[Interface].
2. there is unnecessary duplicate code in the check{Put|Delete} code in
HRegionServer.
--
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-7709) Infinite loop possible in Master/Master replication
[ https://issues.apache.org/jira/browse/HBASE-7709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646400#comment-13646400 ] Lars Hofhansl commented on HBASE-7709: -- The proposal sounds good. Are you still planning to work on this [~jeffreyz]? Infinite loop possible in Master/Master replication --- Key: HBASE-7709 URL: https://issues.apache.org/jira/browse/HBASE-7709 Project: HBase Issue Type: Bug Components: Replication Affects Versions: 0.94.6, 0.95.1 Reporter: Lars Hofhansl Fix For: 0.98.0, 0.94.8, 0.95.1 We just discovered the following scenario: # Cluster A and B are setup in master/master replication # By accident we had Cluster C replicate to Cluster A. Now all edit originating from C will be bouncing between A and B. Forever! The reason is that when the edit come in from C the cluster ID is already set and won't be reset. We have a couple of options here: # Optionally only support master/master (not cycles of more than two clusters). In that case we can always reset the cluster ID in the ReplicationSource. That means that now cycles 2 will have the data cycle forever. This is the only option that requires no changes in the HLog format. # Instead of a single cluster id per edit maintain a (unordered) set of cluster id that have seen this edit. Then in ReplicationSource we drop any edit that the sink has seen already. The is the cleanest approach, but it might need a lot of data stored per edit if there are many clusters involved. # Maintain a configurable counter of the maximum cycle side we want to support. Could default to 10 (even maybe even just). Store a hop-count in the WAL and the ReplicationSource increases that hop-count on each hop. If we're over the max, just drop the edit. -- 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-4811) Support reverse Scan
[ https://issues.apache.org/jira/browse/HBASE-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13646401#comment-13646401 ] Liang Xie commented on HBASE-4811: -- right, [~lhofhansl]. we had introduced a new field in Scan and bumped a higher scan version in internal version before. And we fixed several bugs during adding more test cases. It's still unstable and we have a plan to improve and enable reverse scan in our product cluster. I'll give a updated patch if the production env shows great. Support reverse Scan Key: HBASE-4811 URL: https://issues.apache.org/jira/browse/HBASE-4811 Project: HBase Issue Type: Improvement Components: Client Affects Versions: 0.20.6 Reporter: John Carrino Attachments: HBase-4811-0.94.3modified.txt All the documentation I find about HBase says that if you want forward and reverse scans you should just build 2 tables and one be ascending and one descending. Is there a fundamental reason that HBase only supports forward Scan? It seems like a lot of extra space overhead and coding overhead (to keep them in sync) to support 2 tables. I am assuming this has been discussed before, but I can't find the discussions anywhere about it or why it would be infeasible. -- 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-8464) FastDiffEncoder - valueLength calculation is incorrect
ramkrishna.s.vasudevan created HBASE-8464:
-
Summary: FastDiffEncoder - valueLength calculation is incorrect
Key: HBASE-8464
URL: https://issues.apache.org/jira/browse/HBASE-8464
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.94.7
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 0.98.0, 0.94.8, 0.95.1
In FastDiffEncoder
Inside compressSingleKeyValue()
{code}
currentState.prevOffset = in.position();
int keyLength = in.getInt();
int valueOffset =
currentState.prevOffset + keyLength + KeyValue.ROW_OFFSET;
int valueLength = in.getInt();
byte flag = 0;
{code}
Before seeing the bug, whenever we write something into encoders, we take the
ByteBuffer that is created by Writer.append().
This basically writes
keyLength, valueLength, keyarray, valuearray, memstoreTS
Now consider a case where the keyarray size is 20 and valuearray size is 20.
As per the above code for the first KV
Read keyLength (4 bytes), value length (4 bytes).
First time the prevOffset is 0 so our value Offset is - 0+20+8 =28.
This is correct.
After the first KV is read when we take up the next KV,
Now the currentState.prevOffset = 28+20 = 48 (the value is also read)
The above calculation will give us
28+20+8 = 56.
But the bytebuffer has only 48 bytes in it.
Why our testcases did not catch this bug?
It is because in the TestDataBlockEncoders we create a ByteBuffer directly from
the KVs and we do not create the way the HFileWriterV2 does it.
See RedundantKVGenerator.convertKvToByteBuffer().
Pls correct me if am wrong. I can provide a patch for the same if my above
analysis is correct.
--
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-8464) FastDiffEncoder - valueOffset calculation is incorrect
[
https://issues.apache.org/jira/browse/HBASE-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-8464:
--
Summary: FastDiffEncoder - valueOffset calculation is incorrect (was:
FastDiffEncoder - valueLength calculation is incorrect)
FastDiffEncoder - valueOffset calculation is incorrect
--
Key: HBASE-8464
URL: https://issues.apache.org/jira/browse/HBASE-8464
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.7, 0.95.0
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 0.98.0, 0.94.8, 0.95.1
In FastDiffEncoder
Inside compressSingleKeyValue()
{code}
currentState.prevOffset = in.position();
int keyLength = in.getInt();
int valueOffset =
currentState.prevOffset + keyLength + KeyValue.ROW_OFFSET;
int valueLength = in.getInt();
byte flag = 0;
{code}
Before seeing the bug, whenever we write something into encoders, we take the
ByteBuffer that is created by Writer.append().
This basically writes
keyLength, valueLength, keyarray, valuearray, memstoreTS
Now consider a case where the keyarray size is 20 and valuearray size is 20.
As per the above code for the first KV
Read keyLength (4 bytes), value length (4 bytes).
First time the prevOffset is 0 so our value Offset is - 0+20+8 =28.
This is correct.
After the first KV is read when we take up the next KV,
Now the currentState.prevOffset = 28+20 = 48 (the value is also read)
The above calculation will give us
28+20+8 = 56.
But the bytebuffer has only 48 bytes in it.
Why our testcases did not catch this bug?
It is because in the TestDataBlockEncoders we create a ByteBuffer directly
from the KVs and we do not create the way the HFileWriterV2 does it.
See RedundantKVGenerator.convertKvToByteBuffer().
Pls correct me if am wrong. I can provide a patch for the same if my above
analysis is correct.
--
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-8448) RatioBasedCompactionPolicy (and derived ones) can select already-compacting files for compaction
[ https://issues.apache.org/jira/browse/HBASE-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645358#comment-13645358 ] Hudson commented on HBASE-8448: --- Integrated in hbase-0.95-on-hadoop2 #85 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/]) HBASE-8448 RatioBasedCompactionPolicy (and derived ones) can select already-compacting files for compaction (Revision 1477392) Result = FAILURE sershe : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/ExploringCompactionPolicy.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/RatioBasedCompactionPolicy.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/compactions/EverythingPolicy.java RatioBasedCompactionPolicy (and derived ones) can select already-compacting files for compaction Key: HBASE-8448 URL: https://issues.apache.org/jira/browse/HBASE-8448 Project: HBase Issue Type: Bug Components: Compaction Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Attachments: HBASE-8448-v0.patch, HBASE-8448-v1.patch The code added to make sure it doesn't get stuck, doesn't take into account filesCompacting. This is the cause of recent TestHFileArchiving failures... -- 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-8456) HBase Windows scripts fail when there's a blank space in JAVA_HOME
[ https://issues.apache.org/jira/browse/HBASE-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645357#comment-13645357 ] Hudson commented on HBASE-8456: --- Integrated in hbase-0.95-on-hadoop2 #85 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/]) HBASE-8456 HBase Windows scripts fail when there's a blank space in JAVA_HOME (Mostafa Elhemali) (Revision 1477353) Result = FAILURE enis : Files : * /hbase/branches/0.95/bin/hbase-config.cmd * /hbase/branches/0.95/bin/hbase.cmd HBase Windows scripts fail when there's a blank space in JAVA_HOME -- Key: HBASE-8456 URL: https://issues.apache.org/jira/browse/HBASE-8456 Project: HBase Issue Type: Bug Components: scripts Environment: Windows Reporter: Mostafa Elhemali Priority: Minor Fix For: 0.98.0, 0.95.1 Attachments: HBASE-8456.patch If JAVA_HOME is set to a directory with a space in it (e.g. C:\Program Files\Java\...), the scripts fail because some of the commands don't properly quote 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-8407) Remove Async HBase from 0.95 and trunk.
[ https://issues.apache.org/jira/browse/HBASE-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645359#comment-13645359 ] Hudson commented on HBASE-8407: --- Integrated in hbase-0.95-on-hadoop2 #85 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/]) HBASE-8407 Remove Async HBase (Revision 1477250) Result = FAILURE eclark : Files : * /hbase/branches/0.95/hbase-server/pom.xml * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java Remove Async HBase from 0.95 and trunk. --- Key: HBASE-8407 URL: https://issues.apache.org/jira/browse/HBASE-8407 Project: HBase Issue Type: Bug Components: Performance Affects Versions: 0.98.0, 0.95.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 0.98.0, 0.95.1 Attachments: HBASE-8407-0.patch Async HBase won't work on a protobuf'd server for quite a while. We should remove that code from perf evaluation until it async hbase is working 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-8425) Per-region memstore size is missing in the new RS web UI
[ https://issues.apache.org/jira/browse/HBASE-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645360#comment-13645360 ] Hudson commented on HBASE-8425: --- Integrated in hbase-0.95-on-hadoop2 #85 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/]) HBASE-8425 Per-region memstore size is missing in the new RS web UI (Revision 1477328) Result = FAILURE eclark : Files : * /hbase/branches/0.95/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/RegionListTmpl.jamon Per-region memstore size is missing in the new RS web UI Key: HBASE-8425 URL: https://issues.apache.org/jira/browse/HBASE-8425 Project: HBase Issue Type: Bug Affects Versions: 0.95.0 Reporter: Jean-Daniel Cryans Assignee: Elliott Clark Fix For: 0.98.0, 0.95.1 Attachments: HBASE-8425-0.patch I like that metric, right now all we have is the whole memstore size in bytes. -- 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-8426) Opening a region failed on Metrics source RegionServer,sub=Regions already exists!
[
https://issues.apache.org/jira/browse/HBASE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645361#comment-13645361
]
Hudson commented on HBASE-8426:
---
Integrated in hbase-0.95-on-hadoop2 #85 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/])
HBASE-8426 Opening a region failed on Metrics source
RegionServer,sub=Regions already exists (Revision 1477246)
Result = FAILURE
eclark :
Files :
*
/hbase/branches/0.95/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/CompatibilitySingletonFactory.java
*
/hbase/branches/0.95/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionServerSourceFactoryImpl.java
*
/hbase/branches/0.95/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionServerSourceFactoryImpl.java
Opening a region failed on Metrics source RegionServer,sub=Regions already
exists!
Key: HBASE-8426
URL: https://issues.apache.org/jira/browse/HBASE-8426
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0
Reporter: Jean-Daniel Cryans
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.98.0, 0.95.1
Attachments: HBASE-8426-0.patch, HBASE-8426-1.patch,
metrics_already_exist.txt
I restarted a cluster on 0.95 (1ecd4c7e0b22bba75c76f2fc2ce369541502b6df) and
some regions failed to open on their first assignment on an exception like:
{noformat}
Caused by: org.apache.hadoop.metrics2.MetricsException: Metrics source
RegionServer,sub=Regions already exists!
at
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.newSourceName(DefaultMetricsSystem.java:126)
at
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.sourceName(DefaultMetricsSystem.java:107)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.register(MetricsSystemImpl.java:217)
at
org.apache.hadoop.hbase.metrics.BaseSourceImpl.init(BaseSourceImpl.java:75)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionAggregateSourceImpl.init(MetricsRegionAggregateSourceImpl.java:49)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionAggregateSourceImpl.init(MetricsRegionAggregateSourceImpl.java:41)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionServerSourceFactoryImpl.getAggregate(MetricsRegionServerSourceFactoryImpl.java:33)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionServerSourceFactoryImpl.createRegion(MetricsRegionServerSourceFactoryImpl.java:50)
at
org.apache.hadoop.hbase.regionserver.MetricsRegion.init(MetricsRegion.java:35)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:488)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:400)
{noformat}
I'm attaching a bigger log.
--
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-8453) TestImportExport failing again due to configuration issues
[
https://issues.apache.org/jira/browse/HBASE-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645362#comment-13645362
]
Hudson commented on HBASE-8453:
---
Integrated in hbase-0.95-on-hadoop2 #85 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/])
Revert HBASE-8453, HBASE-8454. (Revision 1477449)
HBASE-8453. TestImportExport failing again due to configuration issues
(Revision 1477374)
Result = FAILURE
apurtell :
Files :
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
apurtell :
Files :
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java
TestImportExport failing again due to configuration issues
--
Key: HBASE-8453
URL: https://issues.apache.org/jira/browse/HBASE-8453
Project: HBase
Issue Type: Sub-task
Components: mapreduce, test
Affects Versions: 0.98.0, 0.94.8, 0.95.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: 8453.patch, 8453-v1-0.94.patch
TestImportExport fails for me with a connection refused exception:
{noformat}
java.lang.reflect.UndeclaredThrowableException
at
org.apache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPBImpl.unwrapAndThrowException(YarnRemoteExceptionPBImpl.java:135)
at
org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getNewApplication(ClientRMProtocolPBClientImpl.java:162)
at
org.apache.hadoop.yarn.client.YarnClientImpl.getNewApplication(YarnClientImpl.java:121)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.getNewJobID(ResourceMgrDelegate.java:107)
at org.apache.hadoop.mapred.YARNRunner.getNewJobID(YARNRunner.java:231)
at
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:352)
[...]
Caused by: com.google.protobuf.ServiceException: java.net.ConnectException:
Call From ip-10-174-75-236/10.174.75.236 to 0.0.0.0:8032 failed on connection
exception: java.net.ConnectException: Connection refused; For more details
see: http://wiki.apache.org/hadoop/ConnectionRefused
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:212)
at com.sun.proxy.$Proxy89.getNewApplication(Unknown Source)
at
org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getNewApplication(ClientRMProtocolPBClientImpl.java:159)
... 42 more
{noformat}
Settings in the MiniMRCluster configuration are not properly propagated in
this test.
--
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-8272) make compaction checker frequency configurable per table/cf
[ https://issues.apache.org/jira/browse/HBASE-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645363#comment-13645363 ] Hudson commented on HBASE-8272: --- Integrated in hbase-0.95-on-hadoop2 #85 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/]) HBASE-8272 make compaction checker frequency configurable per table/cf (Revision 1477426) Result = FAILURE sershe : Files : * /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/HStore.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreConfigInformation.java make compaction checker frequency configurable per table/cf --- Key: HBASE-8272 URL: https://issues.apache.org/jira/browse/HBASE-8272 Project: HBase Issue Type: Improvement Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Minor Attachments: HBASE-8272-v0.patch, HBASE-8272-v1.patch, HBASE-8272-v2.patch, HBASE-8272-v2.patch, HBASE-8272-v3.patch Makes the compaction checker frequency configurable per table/cf; that is useful for compaction schemes where many compactions can be available at any time, so the default checks/requests that HBase performs may be insufficient. -- 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-8454) TestImportTsv failing due to configuration issues
[
https://issues.apache.org/jira/browse/HBASE-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645364#comment-13645364
]
Hudson commented on HBASE-8454:
---
Integrated in hbase-0.95-on-hadoop2 #85 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/85/])
Revert HBASE-8453, HBASE-8454. (Revision 1477449)
HBASE-8454. TestImportTsv failing due to configuration issues (Revision 1477378)
Result = FAILURE
apurtell :
Files :
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
apurtell :
Files :
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
TestImportTsv failing due to configuration issues
-
Key: HBASE-8454
URL: https://issues.apache.org/jira/browse/HBASE-8454
Project: HBase
Issue Type: Sub-task
Components: mapreduce, test
Affects Versions: 0.98.0, 0.94.8, 0.95.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: 8454-branch-0.94.patch, 8454.patch
It looks like TestImportTsv can be fixed once HBASE-8453 is applied with this
additional delta:
{noformat}
diff --git
a/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
b/src/test/java/org/
index 77d044b..0da6f0a 100644
--- a/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
+++ b/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
@@ -26,6 +26,7 @@ import java.util.ArrayList;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.apache.hadoop.hbase.*;
+import org.apache.hadoop.mapred.JobConf;
import org.apache.hadoop.mapreduce.Job;
import org.apache.hadoop.fs.FSDataOutputStream;
import org.apache.hadoop.fs.Path;
@@ -289,7 +290,10 @@ public class TestImportTsv {
LOG.info(set the hbaseAdmin);
ImportTsv.createHbaseAdmin(conf);
}
- Job job = ImportTsv.createSubmittableJob(conf, args);
+
+ JobConf jobConf = htu1.getMRCluster().createJobConf();
+ HBaseConfiguration.merge(jobConf, conf);
+ Job job = ImportTsv.createSubmittableJob(jobConf, args);
job.waitForCompletion(false);
assertTrue(job.isSuccessful());
{noformat}
Tested with Hadoop 2.0.4 + HBase 0.94.7.
--
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-8456) HBase Windows scripts fail when there's a blank space in JAVA_HOME
[ https://issues.apache.org/jira/browse/HBASE-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645386#comment-13645386 ] Hudson commented on HBASE-8456: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #515 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/515/]) HBASE-8456 HBase Windows scripts fail when there's a blank space in JAVA_HOME (Mostafa Elhemali) (Revision 1477351) Result = FAILURE enis : Files : * /hbase/trunk/bin/hbase-config.cmd * /hbase/trunk/bin/hbase.cmd HBase Windows scripts fail when there's a blank space in JAVA_HOME -- Key: HBASE-8456 URL: https://issues.apache.org/jira/browse/HBASE-8456 Project: HBase Issue Type: Bug Components: scripts Environment: Windows Reporter: Mostafa Elhemali Priority: Minor Fix For: 0.98.0, 0.95.1 Attachments: HBASE-8456.patch If JAVA_HOME is set to a directory with a space in it (e.g. C:\Program Files\Java\...), the scripts fail because some of the commands don't properly quote 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-8448) RatioBasedCompactionPolicy (and derived ones) can select already-compacting files for compaction
[ https://issues.apache.org/jira/browse/HBASE-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645387#comment-13645387 ] Hudson commented on HBASE-8448: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #515 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/515/]) HBASE-8448 RatioBasedCompactionPolicy (and derived ones) can select already-compacting files for compaction (Revision 1477391) Result = FAILURE sershe : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/ExploringCompactionPolicy.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/RatioBasedCompactionPolicy.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/compactions/EverythingPolicy.java RatioBasedCompactionPolicy (and derived ones) can select already-compacting files for compaction Key: HBASE-8448 URL: https://issues.apache.org/jira/browse/HBASE-8448 Project: HBase Issue Type: Bug Components: Compaction Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Attachments: HBASE-8448-v0.patch, HBASE-8448-v1.patch The code added to make sure it doesn't get stuck, doesn't take into account filesCompacting. This is the cause of recent TestHFileArchiving failures... -- 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-8407) Remove Async HBase from 0.95 and trunk.
[ https://issues.apache.org/jira/browse/HBASE-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645388#comment-13645388 ] Hudson commented on HBASE-8407: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #515 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/515/]) HBASE-8407 Remove Async HBase (Revision 1477251) Result = FAILURE eclark : Files : * /hbase/trunk/hbase-server/pom.xml * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java Remove Async HBase from 0.95 and trunk. --- Key: HBASE-8407 URL: https://issues.apache.org/jira/browse/HBASE-8407 Project: HBase Issue Type: Bug Components: Performance Affects Versions: 0.98.0, 0.95.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 0.98.0, 0.95.1 Attachments: HBASE-8407-0.patch Async HBase won't work on a protobuf'd server for quite a while. We should remove that code from perf evaluation until it async hbase is working 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-8425) Per-region memstore size is missing in the new RS web UI
[ https://issues.apache.org/jira/browse/HBASE-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645389#comment-13645389 ] Hudson commented on HBASE-8425: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #515 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/515/]) HBASE-8425 Per-region memstore size is missing in the new RS web UI (Revision 1477330) Result = FAILURE eclark : Files : * /hbase/trunk/hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/RegionListTmpl.jamon Per-region memstore size is missing in the new RS web UI Key: HBASE-8425 URL: https://issues.apache.org/jira/browse/HBASE-8425 Project: HBase Issue Type: Bug Affects Versions: 0.95.0 Reporter: Jean-Daniel Cryans Assignee: Elliott Clark Fix For: 0.98.0, 0.95.1 Attachments: HBASE-8425-0.patch I like that metric, right now all we have is the whole memstore size in bytes. -- 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-8426) Opening a region failed on Metrics source RegionServer,sub=Regions already exists!
[
https://issues.apache.org/jira/browse/HBASE-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645390#comment-13645390
]
Hudson commented on HBASE-8426:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #515 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/515/])
HBASE-8426 Opening a region failed on Metrics source
RegionServer,sub=Regions already exists (Revision 1477247)
Result = FAILURE
eclark :
Files :
*
/hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/CompatibilitySingletonFactory.java
*
/hbase/trunk/hbase-hadoop1-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionServerSourceFactoryImpl.java
*
/hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionServerSourceFactoryImpl.java
Opening a region failed on Metrics source RegionServer,sub=Regions already
exists!
Key: HBASE-8426
URL: https://issues.apache.org/jira/browse/HBASE-8426
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0
Reporter: Jean-Daniel Cryans
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.98.0, 0.95.1
Attachments: HBASE-8426-0.patch, HBASE-8426-1.patch,
metrics_already_exist.txt
I restarted a cluster on 0.95 (1ecd4c7e0b22bba75c76f2fc2ce369541502b6df) and
some regions failed to open on their first assignment on an exception like:
{noformat}
Caused by: org.apache.hadoop.metrics2.MetricsException: Metrics source
RegionServer,sub=Regions already exists!
at
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.newSourceName(DefaultMetricsSystem.java:126)
at
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.sourceName(DefaultMetricsSystem.java:107)
at
org.apache.hadoop.metrics2.impl.MetricsSystemImpl.register(MetricsSystemImpl.java:217)
at
org.apache.hadoop.hbase.metrics.BaseSourceImpl.init(BaseSourceImpl.java:75)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionAggregateSourceImpl.init(MetricsRegionAggregateSourceImpl.java:49)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionAggregateSourceImpl.init(MetricsRegionAggregateSourceImpl.java:41)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionServerSourceFactoryImpl.getAggregate(MetricsRegionServerSourceFactoryImpl.java:33)
at
org.apache.hadoop.hbase.regionserver.MetricsRegionServerSourceFactoryImpl.createRegion(MetricsRegionServerSourceFactoryImpl.java:50)
at
org.apache.hadoop.hbase.regionserver.MetricsRegion.init(MetricsRegion.java:35)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:488)
at org.apache.hadoop.hbase.regionserver.HRegion.init(HRegion.java:400)
{noformat}
I'm attaching a bigger log.
--
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-8453) TestImportExport failing again due to configuration issues
[
https://issues.apache.org/jira/browse/HBASE-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645391#comment-13645391
]
Hudson commented on HBASE-8453:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #515 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/515/])
Revert HBASE-8453, HBASE-8454. (Revision 1477448)
HBASE-8453. TestImportExport failing again due to configuration issues
(Revision 1477373)
Result = FAILURE
apurtell :
Files :
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
apurtell :
Files :
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java
TestImportExport failing again due to configuration issues
--
Key: HBASE-8453
URL: https://issues.apache.org/jira/browse/HBASE-8453
Project: HBase
Issue Type: Sub-task
Components: mapreduce, test
Affects Versions: 0.98.0, 0.94.8, 0.95.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.98.0, 0.94.8, 0.95.1
Attachments: 8453.patch, 8453-v1-0.94.patch
TestImportExport fails for me with a connection refused exception:
{noformat}
java.lang.reflect.UndeclaredThrowableException
at
org.apache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPBImpl.unwrapAndThrowException(YarnRemoteExceptionPBImpl.java:135)
at
org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getNewApplication(ClientRMProtocolPBClientImpl.java:162)
at
org.apache.hadoop.yarn.client.YarnClientImpl.getNewApplication(YarnClientImpl.java:121)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.getNewJobID(ResourceMgrDelegate.java:107)
at org.apache.hadoop.mapred.YARNRunner.getNewJobID(YARNRunner.java:231)
at
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:352)
[...]
Caused by: com.google.protobuf.ServiceException: java.net.ConnectException:
Call From ip-10-174-75-236/10.174.75.236 to 0.0.0.0:8032 failed on connection
exception: java.net.ConnectException: Connection refused; For more details
see: http://wiki.apache.org/hadoop/ConnectionRefused
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:212)
at com.sun.proxy.$Proxy89.getNewApplication(Unknown Source)
at
org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getNewApplication(ClientRMProtocolPBClientImpl.java:159)
... 42 more
{noformat}
Settings in the MiniMRCluster configuration are not properly propagated in
this test.
--
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-8272) make compaction checker frequency configurable per table/cf
[ https://issues.apache.org/jira/browse/HBASE-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645392#comment-13645392 ] Hudson commented on HBASE-8272: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #515 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/515/]) HBASE-8272 make compaction checker frequency configurable per table/cf (Revision 1477425) Result = FAILURE sershe : Files : * /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/HStore.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreConfigInformation.java make compaction checker frequency configurable per table/cf --- Key: HBASE-8272 URL: https://issues.apache.org/jira/browse/HBASE-8272 Project: HBase Issue Type: Improvement Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Priority: Minor Attachments: HBASE-8272-v0.patch, HBASE-8272-v1.patch, HBASE-8272-v2.patch, HBASE-8272-v2.patch, HBASE-8272-v3.patch Makes the compaction checker frequency configurable per table/cf; that is useful for compaction schemes where many compactions can be available at any time, so the default checks/requests that HBase performs may be insufficient. -- 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
