[jira] [Commented] (HBASE-8021) TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently
[
https://issues.apache.org/jira/browse/HBASE-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595663#comment-13595663
]
Hadoop QA commented on HBASE-8021:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572494/HBASE-8021_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 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:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.security.access.TestAccessController
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4711//console
This message is automatically generated.
TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback()
fails consistently
---
Key: HBASE-8021
URL: https://issues.apache.org/jira/browse/HBASE-8021
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Critical
Fix For: 0.95.0, 0.96.0, 0.98.0
Attachments: HBASE-8021_1.patch, HBASE-8021_1.patch
Uploaded the patch in the JIRA HBASE-7981.
Raised this so that we have a corresponding JIRA for this specific testcase.
--
This message is automatically generated by JIRA.
If 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-7876) Got exception when manually triggers a split on an empty region
[ https://issues.apache.org/jira/browse/HBASE-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595662#comment-13595662 ] Maryann Xue commented on HBASE-7876: agree with clockfly. @ramakrishna to me it makes no sense for the user to configure to get such an exception for this reasonable and no harm operation. and as clockfly said, splitting an empty region with no midkey specifies still behaves as before. Got exception when manually triggers a split on an empty region --- Key: HBASE-7876 URL: https://issues.apache.org/jira/browse/HBASE-7876 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 0.94.5 Reporter: Maryann Xue Assignee: Maryann Xue Priority: Minor Attachments: HBASE-7876-0.94.patch We should allow a region to split successfully even if it does not yet have storefiles. -- This message is automatically generated by JIRA. If 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-7876) Got exception when manually triggers a split on an empty region
[ https://issues.apache.org/jira/browse/HBASE-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595677#comment-13595677 ] ramkrishna.s.vasudevan commented on HBASE-7876: --- Ya Maryann. Pls carry on with the patch. Infact your arg makes sense. Got exception when manually triggers a split on an empty region --- Key: HBASE-7876 URL: https://issues.apache.org/jira/browse/HBASE-7876 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 0.94.5 Reporter: Maryann Xue Assignee: Maryann Xue Priority: Minor Attachments: HBASE-7876-0.94.patch We should allow a region to split successfully even if it does not yet have storefiles. -- This message is automatically generated by JIRA. If 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-8006) use FSUtils to get/set hbase.rootdir
[
https://issues.apache.org/jira/browse/HBASE-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-8006:
---
Resolution: Fixed
Fix Version/s: 0.98.0
Status: Resolved (was: Patch Available)
use FSUtils to get/set hbase.rootdir
Key: HBASE-8006
URL: https://issues.apache.org/jira/browse/HBASE-8006
Project: HBase
Issue Type: Sub-task
Components: regionserver
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
Labels: noob
Fix For: 0.98.0
Attachments: HBASE-8006-v0.patch
We have different ways around the code to get the root dir
{code}
this.conf.get(hbase.rootdir)
new Path(conf.get(HConstants.HBASE_DIR));
fs.makeQualified(new Path(this.c.get(HConstants.HBASE_DIR)));
FSUtils.getRootDir(conf)
{code}
also we have lots of places where we have this set fs.default
{code}
this.conf.set(fs.default.name, fs.getUri().toString());
this.conf.set(fs.defaultFS, fs.getUri().toString());
{code}
replace everything to use the FSUtils and have one single way to do this stuff
--
This message is automatically generated by JIRA.
If 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-7996) Clean up resource leak in MultiTableInputFormat
[
https://issues.apache.org/jira/browse/HBASE-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595683#comment-13595683
]
Hudson commented on HBASE-7996:
---
Integrated in hbase-0.95 #34 (See
[https://builds.apache.org/job/hbase-0.95/34/])
HBASE-7996 Clean up resource leak in MultiTableInputFormat (Revision
1453719)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/MultiTableInputFormatBase.java
Clean up resource leak in MultiTableInputFormat
---
Key: HBASE-7996
URL: https://issues.apache.org/jira/browse/HBASE-7996
Project: HBase
Issue Type: Improvement
Components: mapreduce
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
Priority: Minor
Fix For: 0.95.0
Attachments: 0001-HBASE-7996-Avoid-leaking-table-handle.patch
MultiTableInputFormatBase#getSplits() will always leak an open HTable
instance when {{throw new IOException(Expecting at least one region for
table ...)}} is called. It can potentially leak throughout that method body.
--
This message is automatically generated by JIRA.
If 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-7982) TestReplicationQueueFailover* runs for a minute, spews 3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
[
https://issues.apache.org/jira/browse/HBASE-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595684#comment-13595684
]
Hudson commented on HBASE-7982:
---
Integrated in hbase-0.95 #34 (See
[https://builds.apache.org/job/hbase-0.95/34/])
HBASE-7982 TestReplicationQueueFailover* runs for a minute, spews
3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
(Revision 1453713)
Result = FAILURE
stack :
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/wal/HLogSplitter.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestFSUtils.java
TestReplicationQueueFailover* runs for a minute, spews 3/4million lines
complaining 'Filesystem closed', has an NPE, and still passes?
--
Key: HBASE-7982
URL: https://issues.apache.org/jira/browse/HBASE-7982
Project: HBase
Issue Type: Bug
Components: build
Reporter: stack
Assignee: Jeffrey Zhong
Priority: Blocker
Fix For: 0.95.0
Attachments: 7982v3.txt, 7982v4.txt, hbase-7982-combined_1.patch,
hbase-7982-combined.patch, hbase-7982-huge-logging.patch,
hbase-7982-NPE_2.patch, hbase-7982-NPE.patch,
hbase-7982-with-Stack-changes-02.patch
I was trying to look at why the odd time Hudson OOMEs trying to make a report
on 0.95 build #4 https://builds.apache.org/job/hbase-0.95/4/console:
{code}
ERROR: Failed to archive test reports
hudson.util.IOException2: remote file operation failed:
/home/jenkins/jenkins-slave/workspace/hbase-0.95 at
hudson.remoting.Channel@151a4e3e:ubuntu3
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
at
...
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.nio.HeapCharBuffer.init(HeapCharBuffer.java:57)
at java.nio.CharBuffer.allocate(CharBuffer.java:329)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:792)
at java.nio.charset.Charset.decode(Charset.java:791)
at hudson.tasks.junit.SuiteResult.init(SuiteResult.java:215)
...
{code}
We are trying to allocate a big buffer and failing.
Looking at reports being generated, we have quite a few that are 10MB in
size:
{code}
durruti:0.95 stack$ find hbase-* -type f -size +1k -exec ls -la {} \;
-rw-r--r--@ 1 stack staff 11126492 Feb 27 06:14
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.backup.TestHFileArchiving-output.txt
-rw-r--r--@ 1 stack staff 13296009 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestFromClientSide3-output.txt
-rw-r--r--@ 1 stack staff 10541898 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestMultiParallel-output.txt
-rw-r--r--@ 1 stack staff 25344601 Feb 27 05:51
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient-output.txt
-rw-r--r--@ 1 stack staff 17966969 Feb 27 06:12
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.TestEndToEndSplitTransaction-output.txt
-rw-r--r--@ 1 stack staff 17699068 Feb 27 06:09
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplit-output.txt
-rw-r--r--@ 1 stack staff 17701832 Feb 27 06:07
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplitCompressed-output.txt
-rw-r--r--@ 1 stack staff 717853709 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailover-output.txt
-rw-r--r--@ 1 stack staff 563616793 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed-output.txt
{code}
... with TestReplicationQueueFailover* being order of magnitude bigger than
the others.
Looking in the test I see both spewing between 800 and 900 thousand lines in
about a minute. Here is their fixation:
{code}
8908998 2013-02-27 06:17:48,176 ERROR
[RegionServer:1;hemera.apache.org,35712,1361945801803.logSyncer]
wal.FSHLog$LogSyncer(1012): Error while syncing, requesting close of hlog.
8908999 java.io.IOException: Filesystem closed
8909000 ,...at org.apache.hadoop.hdfs.DFSClient.checkOpen(DFSClient.java:319)
8909001 ,...at org.apache.hadoop.hdfs.DFSClient.access$1200(DFSClient.java:78)
8909002 ,...at
[jira] [Commented] (HBASE-8021) TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently
[ https://issues.apache.org/jira/browse/HBASE-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595685#comment-13595685 ] Hudson commented on HBASE-8021: --- Integrated in hbase-0.95 #34 (See [https://builds.apache.org/job/hbase-0.95/34/]) HBASE-8021 TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently (Revision 1453718) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently --- Key: HBASE-8021 URL: https://issues.apache.org/jira/browse/HBASE-8021 Project: HBase Issue Type: Bug Affects Versions: 0.95.0 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.95.0, 0.96.0, 0.98.0 Attachments: HBASE-8021_1.patch, HBASE-8021_1.patch Uploaded the patch in the JIRA HBASE-7981. Raised this so that we have a corresponding JIRA for this specific testcase. -- This message is automatically generated by JIRA. If 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-7845) optimize hfile index key
[ https://issues.apache.org/jira/browse/HBASE-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liang Xie updated HBASE-7845: - Attachment: HBASE-7845-v4.txt v4 fixed the javadoc warnings, and avoid an unnecessary byte array new. optimize hfile index key Key: HBASE-7845 URL: https://issues.apache.org/jira/browse/HBASE-7845 Project: HBase Issue Type: Improvement Components: HFile Affects Versions: 0.96.0 Reporter: Liang Xie Assignee: Liang Xie Fix For: 0.98.0 Attachments: HBASE-7845.txt, HBASE-7845-v2.txt, HBASE-7845-v3.txt, HBASE-7845-v4.txt Leveldb uses ByteWiseComparatorImpl::FindShortestSeparator() FindShortSuccessor() to reduce index key size, it would be helpful under special conditions. -- This message is automatically generated by JIRA. If 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-7996) Clean up resource leak in MultiTableInputFormat
[
https://issues.apache.org/jira/browse/HBASE-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595709#comment-13595709
]
Hudson commented on HBASE-7996:
---
Integrated in HBase-TRUNK #3923 (See
[https://builds.apache.org/job/HBase-TRUNK/3923/])
HBASE-7996 Clean up resource leak in MultiTableInputFormat (Revision
1453720)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/MultiTableInputFormatBase.java
Clean up resource leak in MultiTableInputFormat
---
Key: HBASE-7996
URL: https://issues.apache.org/jira/browse/HBASE-7996
Project: HBase
Issue Type: Improvement
Components: mapreduce
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
Priority: Minor
Fix For: 0.95.0
Attachments: 0001-HBASE-7996-Avoid-leaking-table-handle.patch
MultiTableInputFormatBase#getSplits() will always leak an open HTable
instance when {{throw new IOException(Expecting at least one region for
table ...)}} is called. It can potentially leak throughout that method body.
--
This message is automatically generated by JIRA.
If 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-7982) TestReplicationQueueFailover* runs for a minute, spews 3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
[
https://issues.apache.org/jira/browse/HBASE-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595710#comment-13595710
]
Hudson commented on HBASE-7982:
---
Integrated in HBase-TRUNK #3923 (See
[https://builds.apache.org/job/HBase-TRUNK/3923/])
HBASE-7982 TestReplicationQueueFailover* runs for a minute, spews
3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
(Revision 1453712)
Result = FAILURE
stack :
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/wal/HLogSplitter.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestFSUtils.java
TestReplicationQueueFailover* runs for a minute, spews 3/4million lines
complaining 'Filesystem closed', has an NPE, and still passes?
--
Key: HBASE-7982
URL: https://issues.apache.org/jira/browse/HBASE-7982
Project: HBase
Issue Type: Bug
Components: build
Reporter: stack
Assignee: Jeffrey Zhong
Priority: Blocker
Fix For: 0.95.0
Attachments: 7982v3.txt, 7982v4.txt, hbase-7982-combined_1.patch,
hbase-7982-combined.patch, hbase-7982-huge-logging.patch,
hbase-7982-NPE_2.patch, hbase-7982-NPE.patch,
hbase-7982-with-Stack-changes-02.patch
I was trying to look at why the odd time Hudson OOMEs trying to make a report
on 0.95 build #4 https://builds.apache.org/job/hbase-0.95/4/console:
{code}
ERROR: Failed to archive test reports
hudson.util.IOException2: remote file operation failed:
/home/jenkins/jenkins-slave/workspace/hbase-0.95 at
hudson.remoting.Channel@151a4e3e:ubuntu3
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
at
...
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.nio.HeapCharBuffer.init(HeapCharBuffer.java:57)
at java.nio.CharBuffer.allocate(CharBuffer.java:329)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:792)
at java.nio.charset.Charset.decode(Charset.java:791)
at hudson.tasks.junit.SuiteResult.init(SuiteResult.java:215)
...
{code}
We are trying to allocate a big buffer and failing.
Looking at reports being generated, we have quite a few that are 10MB in
size:
{code}
durruti:0.95 stack$ find hbase-* -type f -size +1k -exec ls -la {} \;
-rw-r--r--@ 1 stack staff 11126492 Feb 27 06:14
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.backup.TestHFileArchiving-output.txt
-rw-r--r--@ 1 stack staff 13296009 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestFromClientSide3-output.txt
-rw-r--r--@ 1 stack staff 10541898 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestMultiParallel-output.txt
-rw-r--r--@ 1 stack staff 25344601 Feb 27 05:51
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient-output.txt
-rw-r--r--@ 1 stack staff 17966969 Feb 27 06:12
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.TestEndToEndSplitTransaction-output.txt
-rw-r--r--@ 1 stack staff 17699068 Feb 27 06:09
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplit-output.txt
-rw-r--r--@ 1 stack staff 17701832 Feb 27 06:07
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplitCompressed-output.txt
-rw-r--r--@ 1 stack staff 717853709 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailover-output.txt
-rw-r--r--@ 1 stack staff 563616793 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed-output.txt
{code}
... with TestReplicationQueueFailover* being order of magnitude bigger than
the others.
Looking in the test I see both spewing between 800 and 900 thousand lines in
about a minute. Here is their fixation:
{code}
8908998 2013-02-27 06:17:48,176 ERROR
[RegionServer:1;hemera.apache.org,35712,1361945801803.logSyncer]
wal.FSHLog$LogSyncer(1012): Error while syncing, requesting close of hlog.
8908999 java.io.IOException: Filesystem closed
8909000 ,...at org.apache.hadoop.hdfs.DFSClient.checkOpen(DFSClient.java:319)
8909001 ,...at org.apache.hadoop.hdfs.DFSClient.access$1200(DFSClient.java:78)
8909002 ,...at
[jira] [Commented] (HBASE-8021) TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently
[ https://issues.apache.org/jira/browse/HBASE-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595711#comment-13595711 ] Hudson commented on HBASE-8021: --- Integrated in HBase-TRUNK #3923 (See [https://builds.apache.org/job/HBase-TRUNK/3923/]) HBASE-8021 TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently (Revision 1453717) Result = FAILURE stack : Files : * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently --- Key: HBASE-8021 URL: https://issues.apache.org/jira/browse/HBASE-8021 Project: HBase Issue Type: Bug Affects Versions: 0.95.0 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.95.0, 0.96.0, 0.98.0 Attachments: HBASE-8021_1.patch, HBASE-8021_1.patch Uploaded the patch in the JIRA HBASE-7981. Raised this so that we have a corresponding JIRA for this specific testcase. -- This message is automatically generated by JIRA. If 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-8004) Creating an existing table from Shell does not throw TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595717#comment-13595717
]
ramkrishna.s.vasudevan commented on HBASE-8004:
---
@Jean
The list and scan and even put works fine.
As Andrew suggesteed i think the relocation of the exception package has caused
this.
Creating an existing table from Shell does not throw TableExistsException
-
Key: HBASE-8004
URL: https://issues.apache.org/jira/browse/HBASE-8004
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
When i try to create a same table from shell i don't get TableExistsException
instead i get
{code}
ERROR: cannot load Java class org.apache.hadoop.hbase.TableNotFoundException
Here is some help for this command:
Creates a table. Pass a table name, and a set of column family
specifications (at least one), and, optionally, table configuration.
Column specification can be a simple string (name), or a dictionary
(dictionaries are described below in main help output), necessarily
including NAME attribute.
Examples:
hbase create 't1', {NAME = 'f1', VERSIONS = 5}
hbase create 't1', {NAME = 'f1'}, {NAME = 'f2'}, {NAME = 'f3'}
hbase # The above in shorthand would be the following:
{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-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-8002: --- Attachment: 8002.v4.patch Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-7244) Provide a command or argument to startup, that formats znodes if provided
[
https://issues.apache.org/jira/browse/HBASE-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rajeshbabu updated HBASE-7244:
--
Attachment: HBASE-7244.patch
@Harsh
Here is the patch we are using in our cluster. We have also same requirements
as you said in description. Instread of changing startup script we have written
seperate cleanup script which cleans zookeeper and hdfs data related to hbase
if no hbase process like master,regionserver,backupmaster is alive.
Please review.
Provide a command or argument to startup, that formats znodes if provided
-
Key: HBASE-7244
URL: https://issues.apache.org/jira/browse/HBASE-7244
Project: HBase
Issue Type: New Feature
Components: Zookeeper
Affects Versions: 0.94.0
Reporter: Harsh J
Priority: Minor
Attachments: HBASE-7244.patch
Many a times I've had to, and have seen instructions being thrown, to stop
cluster, clear out ZK and restart.
While this is only a quick (and painful to master) fix, it is certainly nifty
to some smaller cluster users but the process is far too long, roughly:
1. Stop HBase
2. Start zkCli.sh and connect to the right quorum
3. Find and ensure the HBase parent znode from the configs (/hbase only by
default)
4. Run an rmr /hbase in the zkCli.sh shell, or manually delete each znode
if on a lower version of ZK.
5. Quit zkCli.sh and start HBase again
Perhaps it may be useful, if the start-hbase.sh itself accepted a formatZK
parameter. Such that, when you do a {{start-hbase.sh -formatZK}}, it does
steps 2-4 automatically for you.
For safety, we could make the formatter code ensure that no HBase instance is
actually active, and skip the format process if it is. Similar to a HDFS
NameNode's format, which would disallow if the name directories are locked.
Would this be a useful addition for administrators? Bigtop too can provide a
service subcommand that could do this.
--
This message is automatically generated by JIRA.
If 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-7845) optimize hfile index key
[
https://issues.apache.org/jira/browse/HBASE-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595733#comment-13595733
]
Hadoop QA commented on HBASE-7845:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572508/HBASE-7845-v4.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 9 new
or modified tests.
{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:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4712//console
This message is automatically generated.
optimize hfile index key
Key: HBASE-7845
URL: https://issues.apache.org/jira/browse/HBASE-7845
Project: HBase
Issue Type: Improvement
Components: HFile
Affects Versions: 0.96.0
Reporter: Liang Xie
Assignee: Liang Xie
Fix For: 0.98.0
Attachments: HBASE-7845.txt, HBASE-7845-v2.txt, HBASE-7845-v3.txt,
HBASE-7845-v4.txt
Leveldb uses ByteWiseComparatorImpl::FindShortestSeparator()
FindShortSuccessor() to reduce index key size, it would be helpful under
special conditions.
--
This message is automatically generated by JIRA.
If 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-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595736#comment-13595736 ] nkeywal commented on HBASE-8002: v4 is what I committed on trunk 0.95 Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595737#comment-13595737 ] nkeywal commented on HBASE-8002: And thanks for the review! Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-8002: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-8004) Creating an existing table from Shell does not throw TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595738#comment-13595738
]
ramkrishna.s.vasudevan commented on HBASE-8004:
---
I tried using this
{code}
include_package org.apache.hadoop.hbase.exceptions
{code}
I added this in admin.rb
{code}
module Hbase
include_package org.apache.hadoop.hbase.exceptions
class Admin
{code}
I think this does not load the package. Checking out.
Creating an existing table from Shell does not throw TableExistsException
-
Key: HBASE-8004
URL: https://issues.apache.org/jira/browse/HBASE-8004
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
When i try to create a same table from shell i don't get TableExistsException
instead i get
{code}
ERROR: cannot load Java class org.apache.hadoop.hbase.TableNotFoundException
Here is some help for this command:
Creates a table. Pass a table name, and a set of column family
specifications (at least one), and, optionally, table configuration.
Column specification can be a simple string (name), or a dictionary
(dictionaries are described below in main help output), necessarily
including NAME attribute.
Examples:
hbase create 't1', {NAME = 'f1', VERSIONS = 5}
hbase create 't1', {NAME = 'f1'}, {NAME = 'f2'}, {NAME = 'f3'}
hbase # The above in shorthand would be the following:
{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-7482) Port HBASE-7442 HBase remote CopyTable not working when security enabled to trunk
[
https://issues.apache.org/jira/browse/HBASE-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595772#comment-13595772
]
James Kinley commented on HBASE-7482:
-
+1
It's better not having to muck around with the configuration. V2 patch looks
good and copytable works on my secure clusters.
Port HBASE-7442 HBase remote CopyTable not working when security enabled to
trunk
-
Key: HBASE-7482
URL: https://issues.apache.org/jira/browse/HBASE-7482
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: James Kinley
Priority: Critical
Fix For: 0.95.0
Attachments: HBASE-7482-trunk.patch, HBASE-7482-v2.patch
Excerpt about the choice of solution from :
The first option was actually quite messy to implement. {{clusterId}} and
{{conf}} are fixed in *{{HBaseClient}}* when it's created and cached by
*{{SecureRpcEngine}}*, so to implement the fix here I would have had to pass
the different cluster {{confs}} up through *{{HConnectionManager}}* and
*{{HBaseRPC}}* in order to override the clusterId in
*{{SecureClient#SecureConnection}}*.
I've gone with the second option of creating and caching different
*{{SecureClients}}* for the local and remote clusters in
*{{SecureRpcEngine}}* - keyed off of the {{clusterId}} instead of the default
*{{SocketFactory}}*. I think this is a cleaner solution.
--
This message is automatically generated by JIRA.
If 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-7482) Port HBASE-7442 HBase remote CopyTable not working when security enabled to trunk
[
https://issues.apache.org/jira/browse/HBASE-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Kinley reassigned HBASE-7482:
---
Assignee: Gary Helmling (was: James Kinley)
Port HBASE-7442 HBase remote CopyTable not working when security enabled to
trunk
-
Key: HBASE-7482
URL: https://issues.apache.org/jira/browse/HBASE-7482
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Gary Helmling
Priority: Critical
Fix For: 0.95.0
Attachments: HBASE-7482-trunk.patch, HBASE-7482-v2.patch
Excerpt about the choice of solution from :
The first option was actually quite messy to implement. {{clusterId}} and
{{conf}} are fixed in *{{HBaseClient}}* when it's created and cached by
*{{SecureRpcEngine}}*, so to implement the fix here I would have had to pass
the different cluster {{confs}} up through *{{HConnectionManager}}* and
*{{HBaseRPC}}* in order to override the clusterId in
*{{SecureClient#SecureConnection}}*.
I've gone with the second option of creating and caching different
*{{SecureClients}}* for the local and remote clusters in
*{{SecureRpcEngine}}* - keyed off of the {{clusterId}} instead of the default
*{{SocketFactory}}*. I think this is a cleaner solution.
--
This message is automatically generated by JIRA.
If 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-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595795#comment-13595795 ] Hudson commented on HBASE-8002: --- Integrated in HBase-TRUNK #3924 (See [https://builds.apache.org/job/HBase-TRUNK/3924/]) HBASE-8002 Make TimeOut Management for Assignment optional in master and regionservers (Revision 1453755) Result = FAILURE nkeywal : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-7996) Clean up resource leak in MultiTableInputFormat
[
https://issues.apache.org/jira/browse/HBASE-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595810#comment-13595810
]
Hudson commented on HBASE-7996:
---
Integrated in hbase-0.95-on-hadoop2 #15 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/15/])
HBASE-7996 Clean up resource leak in MultiTableInputFormat (Revision
1453719)
Result = FAILURE
stack :
Files :
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/MultiTableInputFormatBase.java
Clean up resource leak in MultiTableInputFormat
---
Key: HBASE-7996
URL: https://issues.apache.org/jira/browse/HBASE-7996
Project: HBase
Issue Type: Improvement
Components: mapreduce
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
Priority: Minor
Fix For: 0.95.0
Attachments: 0001-HBASE-7996-Avoid-leaking-table-handle.patch
MultiTableInputFormatBase#getSplits() will always leak an open HTable
instance when {{throw new IOException(Expecting at least one region for
table ...)}} is called. It can potentially leak throughout that method body.
--
This message is automatically generated by JIRA.
If 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-7982) TestReplicationQueueFailover* runs for a minute, spews 3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
[
https://issues.apache.org/jira/browse/HBASE-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595811#comment-13595811
]
Hudson commented on HBASE-7982:
---
Integrated in hbase-0.95-on-hadoop2 #15 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/15/])
HBASE-7982 TestReplicationQueueFailover* runs for a minute, spews
3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
(Revision 1453713)
Result = FAILURE
stack :
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/wal/HLogSplitter.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestFSUtils.java
TestReplicationQueueFailover* runs for a minute, spews 3/4million lines
complaining 'Filesystem closed', has an NPE, and still passes?
--
Key: HBASE-7982
URL: https://issues.apache.org/jira/browse/HBASE-7982
Project: HBase
Issue Type: Bug
Components: build
Reporter: stack
Assignee: Jeffrey Zhong
Priority: Blocker
Fix For: 0.95.0
Attachments: 7982v3.txt, 7982v4.txt, hbase-7982-combined_1.patch,
hbase-7982-combined.patch, hbase-7982-huge-logging.patch,
hbase-7982-NPE_2.patch, hbase-7982-NPE.patch,
hbase-7982-with-Stack-changes-02.patch
I was trying to look at why the odd time Hudson OOMEs trying to make a report
on 0.95 build #4 https://builds.apache.org/job/hbase-0.95/4/console:
{code}
ERROR: Failed to archive test reports
hudson.util.IOException2: remote file operation failed:
/home/jenkins/jenkins-slave/workspace/hbase-0.95 at
hudson.remoting.Channel@151a4e3e:ubuntu3
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
at
...
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.nio.HeapCharBuffer.init(HeapCharBuffer.java:57)
at java.nio.CharBuffer.allocate(CharBuffer.java:329)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:792)
at java.nio.charset.Charset.decode(Charset.java:791)
at hudson.tasks.junit.SuiteResult.init(SuiteResult.java:215)
...
{code}
We are trying to allocate a big buffer and failing.
Looking at reports being generated, we have quite a few that are 10MB in
size:
{code}
durruti:0.95 stack$ find hbase-* -type f -size +1k -exec ls -la {} \;
-rw-r--r--@ 1 stack staff 11126492 Feb 27 06:14
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.backup.TestHFileArchiving-output.txt
-rw-r--r--@ 1 stack staff 13296009 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestFromClientSide3-output.txt
-rw-r--r--@ 1 stack staff 10541898 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestMultiParallel-output.txt
-rw-r--r--@ 1 stack staff 25344601 Feb 27 05:51
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient-output.txt
-rw-r--r--@ 1 stack staff 17966969 Feb 27 06:12
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.TestEndToEndSplitTransaction-output.txt
-rw-r--r--@ 1 stack staff 17699068 Feb 27 06:09
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplit-output.txt
-rw-r--r--@ 1 stack staff 17701832 Feb 27 06:07
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplitCompressed-output.txt
-rw-r--r--@ 1 stack staff 717853709 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailover-output.txt
-rw-r--r--@ 1 stack staff 563616793 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed-output.txt
{code}
... with TestReplicationQueueFailover* being order of magnitude bigger than
the others.
Looking in the test I see both spewing between 800 and 900 thousand lines in
about a minute. Here is their fixation:
{code}
8908998 2013-02-27 06:17:48,176 ERROR
[RegionServer:1;hemera.apache.org,35712,1361945801803.logSyncer]
wal.FSHLog$LogSyncer(1012): Error while syncing, requesting close of hlog.
8908999 java.io.IOException: Filesystem closed
8909000 ,...at org.apache.hadoop.hdfs.DFSClient.checkOpen(DFSClient.java:319)
8909001 ,...at
[jira] [Commented] (HBASE-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595812#comment-13595812 ] Hudson commented on HBASE-8002: --- Integrated in hbase-0.95-on-hadoop2 #15 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/15/]) HBASE-8002 Make TimeOut Management for Assignment optional in master and regionservers (Revision 1453757) Result = FAILURE nkeywal : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-8021) TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently
[ https://issues.apache.org/jira/browse/HBASE-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595813#comment-13595813 ] Hudson commented on HBASE-8021: --- Integrated in hbase-0.95-on-hadoop2 #15 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/15/]) HBASE-8021 TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently (Revision 1453718) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently --- Key: HBASE-8021 URL: https://issues.apache.org/jira/browse/HBASE-8021 Project: HBase Issue Type: Bug Affects Versions: 0.95.0 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.95.0, 0.96.0, 0.98.0 Attachments: HBASE-8021_1.patch, HBASE-8021_1.patch Uploaded the patch in the JIRA HBASE-7981. Raised this so that we have a corresponding JIRA for this specific testcase. -- This message is automatically generated by JIRA. If 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-7153) print gc option in hbase-env.sh affects hbase zkcli
[ https://issues.apache.org/jira/browse/HBASE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595814#comment-13595814 ] Hudson commented on HBASE-7153: --- Integrated in hbase-0.95-on-hadoop2 #15 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/15/]) HBASE-7153 print gc option in hbase-env.sh affects hbase zkcli (Dave Latham and LarsH) (Revision 1453685) Result = FAILURE larsh : Files : * /hbase/branches/0.95/bin/hbase print gc option in hbase-env.sh affects hbase zkcli --- Key: HBASE-7153 URL: https://issues.apache.org/jira/browse/HBASE-7153 Project: HBase Issue Type: Bug Components: scripts Affects Versions: 0.94.0 Reporter: wonderyl Assignee: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.6 Attachments: 7153-0.94.txt, HBASE-7153-0.94.patch I un-commented the -verbose:gc option in hbase-env.sh, which print out the gc info. but when I use hbase zkcli to check zk, it can not connect to the server. the problem is zkcli uses hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to get the server_arg in the script hbase. when gc verbose option is open, the output of ZooKeeperMainServerArg is with gc info, which masses up with server_arg. and this is the reason stop zkcli working. I think the easiest way to fix this is to trim the gc info out of server_arg in the hbase script. -- This message is automatically generated by JIRA. If 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-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595824#comment-13595824 ] Hudson commented on HBASE-8002: --- Integrated in hbase-0.95 #35 (See [https://builds.apache.org/job/hbase-0.95/35/]) HBASE-8002 Make TimeOut Management for Assignment optional in master and regionservers (Revision 1453757) Result = FAILURE nkeywal : Files : * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-7996) Clean up resource leak in MultiTableInputFormat
[
https://issues.apache.org/jira/browse/HBASE-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595856#comment-13595856
]
Hudson commented on HBASE-7996:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #434 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/434/])
HBASE-7996 Clean up resource leak in MultiTableInputFormat (Revision
1453720)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/MultiTableInputFormatBase.java
Clean up resource leak in MultiTableInputFormat
---
Key: HBASE-7996
URL: https://issues.apache.org/jira/browse/HBASE-7996
Project: HBase
Issue Type: Improvement
Components: mapreduce
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
Priority: Minor
Fix For: 0.95.0
Attachments: 0001-HBASE-7996-Avoid-leaking-table-handle.patch
MultiTableInputFormatBase#getSplits() will always leak an open HTable
instance when {{throw new IOException(Expecting at least one region for
table ...)}} is called. It can potentially leak throughout that method body.
--
This message is automatically generated by JIRA.
If 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-7982) TestReplicationQueueFailover* runs for a minute, spews 3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
[
https://issues.apache.org/jira/browse/HBASE-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595857#comment-13595857
]
Hudson commented on HBASE-7982:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #434 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/434/])
HBASE-7982 TestReplicationQueueFailover* runs for a minute, spews
3/4million lines complaining 'Filesystem closed', has an NPE, and still passes?
(Revision 1453712)
Result = FAILURE
stack :
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/wal/HLogSplitter.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestFSUtils.java
TestReplicationQueueFailover* runs for a minute, spews 3/4million lines
complaining 'Filesystem closed', has an NPE, and still passes?
--
Key: HBASE-7982
URL: https://issues.apache.org/jira/browse/HBASE-7982
Project: HBase
Issue Type: Bug
Components: build
Reporter: stack
Assignee: Jeffrey Zhong
Priority: Blocker
Fix For: 0.95.0
Attachments: 7982v3.txt, 7982v4.txt, hbase-7982-combined_1.patch,
hbase-7982-combined.patch, hbase-7982-huge-logging.patch,
hbase-7982-NPE_2.patch, hbase-7982-NPE.patch,
hbase-7982-with-Stack-changes-02.patch
I was trying to look at why the odd time Hudson OOMEs trying to make a report
on 0.95 build #4 https://builds.apache.org/job/hbase-0.95/4/console:
{code}
ERROR: Failed to archive test reports
hudson.util.IOException2: remote file operation failed:
/home/jenkins/jenkins-slave/workspace/hbase-0.95 at
hudson.remoting.Channel@151a4e3e:ubuntu3
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
at
...
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.nio.HeapCharBuffer.init(HeapCharBuffer.java:57)
at java.nio.CharBuffer.allocate(CharBuffer.java:329)
at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:792)
at java.nio.charset.Charset.decode(Charset.java:791)
at hudson.tasks.junit.SuiteResult.init(SuiteResult.java:215)
...
{code}
We are trying to allocate a big buffer and failing.
Looking at reports being generated, we have quite a few that are 10MB in
size:
{code}
durruti:0.95 stack$ find hbase-* -type f -size +1k -exec ls -la {} \;
-rw-r--r--@ 1 stack staff 11126492 Feb 27 06:14
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.backup.TestHFileArchiving-output.txt
-rw-r--r--@ 1 stack staff 13296009 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestFromClientSide3-output.txt
-rw-r--r--@ 1 stack staff 10541898 Feb 27 05:47
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestMultiParallel-output.txt
-rw-r--r--@ 1 stack staff 25344601 Feb 27 05:51
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient-output.txt
-rw-r--r--@ 1 stack staff 17966969 Feb 27 06:12
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.TestEndToEndSplitTransaction-output.txt
-rw-r--r--@ 1 stack staff 17699068 Feb 27 06:09
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplit-output.txt
-rw-r--r--@ 1 stack staff 17701832 Feb 27 06:07
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestHLogSplitCompressed-output.txt
-rw-r--r--@ 1 stack staff 717853709 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailover-output.txt
-rw-r--r--@ 1 stack staff 563616793 Feb 27 06:17
hbase-server/target/surefire-reports/org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed-output.txt
{code}
... with TestReplicationQueueFailover* being order of magnitude bigger than
the others.
Looking in the test I see both spewing between 800 and 900 thousand lines in
about a minute. Here is their fixation:
{code}
8908998 2013-02-27 06:17:48,176 ERROR
[RegionServer:1;hemera.apache.org,35712,1361945801803.logSyncer]
wal.FSHLog$LogSyncer(1012): Error while syncing, requesting close of hlog.
8908999 java.io.IOException: Filesystem closed
8909000 ,...at org.apache.hadoop.hdfs.DFSClient.checkOpen(DFSClient.java:319)
8909001 ,...at org.apache.hadoop.hdfs.DFSClient.access$1200(DFSClient.java:78)
8909002
[jira] [Commented] (HBASE-8021) TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently
[ https://issues.apache.org/jira/browse/HBASE-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595859#comment-13595859 ] Hudson commented on HBASE-8021: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #434 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/434/]) HBASE-8021 TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently (Revision 1453717) Result = FAILURE stack : Files : * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java TestSplitTransactionOnCluster.testShouldThrowIOExceptionIfStoreFileSizeIsEmptyAndShouldSuccessfullyExecuteRollback() fails consistently --- Key: HBASE-8021 URL: https://issues.apache.org/jira/browse/HBASE-8021 Project: HBase Issue Type: Bug Affects Versions: 0.95.0 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Priority: Critical Fix For: 0.95.0, 0.96.0, 0.98.0 Attachments: HBASE-8021_1.patch, HBASE-8021_1.patch Uploaded the patch in the JIRA HBASE-7981. Raised this so that we have a corresponding JIRA for this specific testcase. -- This message is automatically generated by JIRA. If 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-7153) print gc option in hbase-env.sh affects hbase zkcli
[ https://issues.apache.org/jira/browse/HBASE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595860#comment-13595860 ] Hudson commented on HBASE-7153: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #434 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/434/]) HBASE-7153 print gc option in hbase-env.sh affects hbase zkcli (Dave Latham and LarsH) (Revision 1453686) Result = FAILURE larsh : Files : * /hbase/trunk/bin/hbase print gc option in hbase-env.sh affects hbase zkcli --- Key: HBASE-7153 URL: https://issues.apache.org/jira/browse/HBASE-7153 Project: HBase Issue Type: Bug Components: scripts Affects Versions: 0.94.0 Reporter: wonderyl Assignee: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.6 Attachments: 7153-0.94.txt, HBASE-7153-0.94.patch I un-commented the -verbose:gc option in hbase-env.sh, which print out the gc info. but when I use hbase zkcli to check zk, it can not connect to the server. the problem is zkcli uses hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to get the server_arg in the script hbase. when gc verbose option is open, the output of ZooKeeperMainServerArg is with gc info, which masses up with server_arg. and this is the reason stop zkcli working. I think the easiest way to fix this is to trim the gc info out of server_arg in the hbase script. -- This message is automatically generated by JIRA. If 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-8002) Make TimeOut Management for Assignment optional in master and regionservers
[ https://issues.apache.org/jira/browse/HBASE-8002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595858#comment-13595858 ] Hudson commented on HBASE-8002: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #434 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/434/]) HBASE-8002 Make TimeOut Management for Assignment optional in master and regionservers (Revision 1453755) Result = FAILURE nkeywal : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java Make TimeOut Management for Assignment optional in master and regionservers --- Key: HBASE-8002 URL: https://issues.apache.org/jira/browse/HBASE-8002 Project: HBase Issue Type: Bug Components: Client, master, Region Assignment Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Assignee: nkeywal Fix For: 0.95.0, 0.98.0 Attachments: 8002.v3.patch, 8002.v4.patch See HBASE-7327 -- This message is automatically generated by JIRA. If 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-8022) Site target fails
Andrew Purtell created HBASE-8022:
-
Summary: Site target fails
Key: HBASE-8022
URL: https://issues.apache.org/jira/browse/HBASE-8022
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
Recoverable error
org.xml.sax.SAXParseException: Include operation failed, reverting to fallback.
Resource error reading file as XML
(href='../../target/site/hbase-default.xml'). Reason:
/usr/src/Hadoop/hbase/target/site/hbase-default.xml (No such file or directory)
Error on line 672 column 52 of
file:///usr/src/Hadoop/hbase/src/docbkx/configuration.xml:
Error reported by XML parser: An 'include' failed, and no 'fallback' element
was found.
[INFO]
[INFO]
[INFO] Skipping HBase
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [5:34.980s]
[INFO] HBase - Common SKIPPED
[INFO] HBase - Protocol .. SKIPPED
[INFO] HBase - Client SKIPPED
[INFO] HBase - Prefix Tree ... SKIPPED
[INFO] HBase - Hadoop Compatibility .. SKIPPED
[INFO] HBase - Hadoop Two Compatibility .. SKIPPED
[INFO] HBase - Server SKIPPED
[INFO] HBase - Integration Tests . SKIPPED
[INFO] HBase - Examples .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5:36.029s
[INFO] Finished at: Thu Mar 07 21:59:14 CST 2013
[INFO] Final Memory: 29M/297M
[INFO]
[ERROR] Failed to execute goal
com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html (multipage) on
project hbase: Failed to transform configuration.xml.
org.xml.sax.SAXParseException: An 'include' failed, and no 'fallback' element
was found. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-8022) Site target fails
[
https://issues.apache.org/jira/browse/HBASE-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-8022:
--
Attachment: HBASE-8022.patch
Site target fails
-
Key: HBASE-8022
URL: https://issues.apache.org/jira/browse/HBASE-8022
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
Attachments: HBASE-8022.patch
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
Recoverable error
org.xml.sax.SAXParseException: Include operation failed, reverting to
fallback. Resource error reading file as XML
(href='../../target/site/hbase-default.xml'). Reason:
/usr/src/Hadoop/hbase/target/site/hbase-default.xml (No such file or
directory)
Error on line 672 column 52 of
file:///usr/src/Hadoop/hbase/src/docbkx/configuration.xml:
Error reported by XML parser: An 'include' failed, and no 'fallback'
element was found.
[INFO]
[INFO]
[INFO] Skipping HBase
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [5:34.980s]
[INFO] HBase - Common SKIPPED
[INFO] HBase - Protocol .. SKIPPED
[INFO] HBase - Client SKIPPED
[INFO] HBase - Prefix Tree ... SKIPPED
[INFO] HBase - Hadoop Compatibility .. SKIPPED
[INFO] HBase - Hadoop Two Compatibility .. SKIPPED
[INFO] HBase - Server SKIPPED
[INFO] HBase - Integration Tests . SKIPPED
[INFO] HBase - Examples .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5:36.029s
[INFO] Finished at: Thu Mar 07 21:59:14 CST 2013
[INFO] Final Memory: 29M/297M
[INFO]
[ERROR] Failed to execute goal
com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html (multipage) on
project hbase: Failed to transform configuration.xml.
org.xml.sax.SAXParseException: An 'include' failed, and no 'fallback' element
was found. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-8023) Assembly target fails
Andrew Purtell created HBASE-8023:
-
Summary: Assembly target fails
Key: HBASE-8023
URL: https://issues.apache.org/jira/browse/HBASE-8023
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
The assembly target fails when using the 2.0 Hadoop profile (at least).
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
[INFO] --- maven-assembly-plugin:2.3:assembly (default-cli) @ hbase ---
[INFO] Reading assembly descriptor: src/assembly/hadoop-two-compat.xml
[WARNING] [DEPRECATION] moduleSet/binaries section detected in root-project
assembly.
MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY!
To refactor, move this assembly into a child project and use the flag
useAllReactorProjectstrue/useAllReactorProjects in each moduleSet.
[INFO] Processing sources for module project:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-protocol:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-client:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-prefix-tree:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop2-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-server:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-it:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-examples:jar:0.97-SNAPSHOT
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [15.877s]
[INFO] HBase - Common SUCCESS [4.633s]
[INFO] HBase - Protocol .. SUCCESS [2.629s]
[INFO] HBase - Client SUCCESS [2.901s]
[INFO] HBase - Prefix Tree ... SUCCESS [3.085s]
[INFO] HBase - Hadoop Compatibility .. SUCCESS [2.647s]
[INFO] HBase - Hadoop Two Compatibility .. SUCCESS [2.005s]
[INFO] HBase - Server SUCCESS [1.888s]
[INFO] HBase - Integration Tests . SUCCESS [6.917s]
[INFO] HBase - Examples .. SUCCESS [2.815s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6:41.503s
[INFO] Finished at: Thu Mar 07 22:14:08 CST 2013
[INFO] Final Memory: 67M/448M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.3:assembly (default-cli) on
project hbase: Failed to create assembly: Artifact:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT (included by module) does not
have an artifact with a file. Please ensure the package phase is run before the
assembly is generated. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-8024) Make Store flush algorithm pluggable
Maryann Xue created HBASE-8024: -- Summary: Make Store flush algorithm pluggable Key: HBASE-8024 URL: https://issues.apache.org/jira/browse/HBASE-8024 Project: HBase Issue Type: Sub-task Components: regionserver Affects Versions: 0.94.5 Reporter: Maryann Xue The idea is to make StoreFlusher an interface instead of an implementation class, and have the original StoreFlusher as the default store flush impl. -- This message is automatically generated by JIRA. If 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-7153) print gc option in hbase-env.sh affects hbase zkcli
[ https://issues.apache.org/jira/browse/HBASE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595918#comment-13595918 ] Dave Latham commented on HBASE-7153: Thanks guys for taking a look. Fixing the array syntax alone is not enough. When you invoke hbase zkcli it turns around and first invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg which will then pick up the server options, cause GC output to appear in standard out, which then gets picked up on the command line for zkcli causing it to fail. Also, there are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. print gc option in hbase-env.sh affects hbase zkcli --- Key: HBASE-7153 URL: https://issues.apache.org/jira/browse/HBASE-7153 Project: HBase Issue Type: Bug Components: scripts Affects Versions: 0.94.0 Reporter: wonderyl Assignee: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.6 Attachments: 7153-0.94.txt, HBASE-7153-0.94.patch I un-commented the -verbose:gc option in hbase-env.sh, which print out the gc info. but when I use hbase zkcli to check zk, it can not connect to the server. the problem is zkcli uses hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to get the server_arg in the script hbase. when gc verbose option is open, the output of ZooKeeperMainServerArg is with gc info, which masses up with server_arg. and this is the reason stop zkcli working. I think the easiest way to fix this is to trim the gc info out of server_arg in the hbase script. -- This message is automatically generated by JIRA. If 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-8025) zkcli fails when SERVER_GC_OPTS is enabled
Dave Latham created HBASE-8025: -- Summary: zkcli fails when SERVER_GC_OPTS is enabled Key: HBASE-8025 URL: https://issues.apache.org/jira/browse/HBASE-8025 Project: HBase Issue Type: Bug Affects Versions: 0.94.4 Reporter: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.7 HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-1753 addressed this but the fix only solved the array syntax - not the white list. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. -- This message is automatically generated by JIRA. If 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-7904) Upgrade hadoop 2.0 dependency to 2.0.4-alpha
[ https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595931#comment-13595931 ] Ted Yu commented on HBASE-7904: --- Suppose 2.0.4-ALPHA makes our mapreduce jobs pass in 0.95, can we entertain building trunk on top of 2.0.4-SNAPSHOT now that Bobby helped published hadoop 2.0 snapshot to maven ? This way, we can quickly detect issue if some change in hadoop 2.0 breaks our mapreduce jobs. Upgrade hadoop 2.0 dependency to 2.0.4-alpha Key: HBASE-7904 URL: https://issues.apache.org/jira/browse/HBASE-7904 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.95.0 Attachments: 7904.txt, 7904-v2.txt, hbase-7904-v3.txt 2.0.3-alpha has been released. We should upgrade the dependency. -- This message is automatically generated by JIRA. If 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-8017) Upgrade hadoop 1 dependency to 1.1.2
[ https://issues.apache.org/jira/browse/HBASE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-8017: -- Attachment: 8017.txt Upgrade hadoop 1 dependency to 1.1.2 Key: HBASE-8017 URL: https://issues.apache.org/jira/browse/HBASE-8017 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.98.0 Attachments: 8017.txt, 8017.txt Hadoop 1.1.2 has been released. From Matt: This release includes 24 bug fixes and backward-compatible enhancements, compared to Hadoop 1.1.1. Improvements include: - bug fixes in use of Kerberos security and SPNEGO - a couple potential deadlock situations - fixes for IBM JDK compatibility - several unit test failure cleanups - other useful improvements For details, please see http://hadoop.apache.org/docs/r1.1.2/releasenotes.html. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (HBASE-7904) Upgrade hadoop 2.0 dependency to 2.0.4-alpha
[ https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595931#comment-13595931 ] Ted Yu edited comment on HBASE-7904 at 3/7/13 2:47 PM: --- Suppose 2.0.4-ALPHA makes our mapreduce jobs pass in 0.95, can we entertain building trunk on top of 2.0.4-SNAPSHOT now that Bobby helped publish hadoop 2.0 snapshot to maven ? This way, we can quickly detect issue if some change in hadoop 2.0 breaks our mapreduce jobs. was (Author: yuzhih...@gmail.com): Suppose 2.0.4-ALPHA makes our mapreduce jobs pass in 0.95, can we entertain building trunk on top of 2.0.4-SNAPSHOT now that Bobby helped published hadoop 2.0 snapshot to maven ? This way, we can quickly detect issue if some change in hadoop 2.0 breaks our mapreduce jobs. Upgrade hadoop 2.0 dependency to 2.0.4-alpha Key: HBASE-7904 URL: https://issues.apache.org/jira/browse/HBASE-7904 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.95.0 Attachments: 7904.txt, 7904-v2.txt, hbase-7904-v3.txt 2.0.3-alpha has been released. We should upgrade the dependency. -- This message is automatically generated by JIRA. If 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-8025) zkcli fails when SERVER_GC_OPTS is enabled
[ https://issues.apache.org/jira/browse/HBASE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Latham updated HBASE-8025: --- Attachment: HBASE-8025-0.94.patch Patch that changes to a server list so that org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg and many other client commands won't have the GC logging options enabled for them zkcli fails when SERVER_GC_OPTS is enabled -- Key: HBASE-8025 URL: https://issues.apache.org/jira/browse/HBASE-8025 Project: HBase Issue Type: Bug Affects Versions: 0.94.4 Reporter: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.7 Attachments: HBASE-8025-0.94.patch HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-1753 addressed this but the fix only solved the array syntax - not the white list. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. -- This message is automatically generated by JIRA. If 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-8025) zkcli fails when SERVER_GC_OPTS is enabled
[ https://issues.apache.org/jira/browse/HBASE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Latham updated HBASE-8025: --- Status: Patch Available (was: Open) zkcli fails when SERVER_GC_OPTS is enabled -- Key: HBASE-8025 URL: https://issues.apache.org/jira/browse/HBASE-8025 Project: HBase Issue Type: Bug Affects Versions: 0.94.4 Reporter: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.7 Attachments: HBASE-8025-0.94.patch HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-1753 addressed this but the fix only solved the array syntax - not the white list. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. -- This message is automatically generated by JIRA. If 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-8023) Assembly target fails
[
https://issues.apache.org/jira/browse/HBASE-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595941#comment-13595941
]
Andrew Purtell commented on HBASE-8023:
---
Running {{clean install site package assembly:assembly}} produces the same
result. (RE: Please ensure the package phase is run before the assembly is
generated.)
Assembly target fails
-
Key: HBASE-8023
URL: https://issues.apache.org/jira/browse/HBASE-8023
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
The assembly target fails when using the 2.0 Hadoop profile (at least).
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
[INFO] --- maven-assembly-plugin:2.3:assembly (default-cli) @ hbase ---
[INFO] Reading assembly descriptor: src/assembly/hadoop-two-compat.xml
[WARNING] [DEPRECATION] moduleSet/binaries section detected in root-project
assembly.
MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY!
To refactor, move this assembly into a child project and use the flag
useAllReactorProjectstrue/useAllReactorProjects in each moduleSet.
[INFO] Processing sources for module project:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-protocol:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-client:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-prefix-tree:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop2-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-server:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-it:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-examples:jar:0.97-SNAPSHOT
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [15.877s]
[INFO] HBase - Common SUCCESS [4.633s]
[INFO] HBase - Protocol .. SUCCESS [2.629s]
[INFO] HBase - Client SUCCESS [2.901s]
[INFO] HBase - Prefix Tree ... SUCCESS [3.085s]
[INFO] HBase - Hadoop Compatibility .. SUCCESS [2.647s]
[INFO] HBase - Hadoop Two Compatibility .. SUCCESS [2.005s]
[INFO] HBase - Server SUCCESS [1.888s]
[INFO] HBase - Integration Tests . SUCCESS [6.917s]
[INFO] HBase - Examples .. SUCCESS [2.815s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6:41.503s
[INFO] Finished at: Thu Mar 07 22:14:08 CST 2013
[INFO] Final Memory: 67M/448M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.3:assembly (default-cli) on
project hbase: Failed to create assembly: Artifact:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-8025) zkcli fails when SERVER_GC_OPTS is enabled
[ https://issues.apache.org/jira/browse/HBASE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Latham updated HBASE-8025: --- Description: HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-7153 addressed this but the fix only solved the array syntax - not the white list. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. was: HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-1753 addressed this but the fix only solved the array syntax - not the white list. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. zkcli fails when SERVER_GC_OPTS is enabled -- Key: HBASE-8025 URL: https://issues.apache.org/jira/browse/HBASE-8025 Project: HBase Issue Type: Bug Affects Versions: 0.94.4 Reporter: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.7 Attachments: HBASE-8025-0.94.patch HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-7153 addressed this but the fix only solved the array syntax - not the white list. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. -- This message is automatically generated by JIRA. If 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-8025) zkcli fails when SERVER_GC_OPTS is enabled
[ https://issues.apache.org/jira/browse/HBASE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Latham updated HBASE-8025: --- Description: HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-7153 addressed this but the fix only solved the array syntax - not the white list, so the zkcli command still fails. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. was: HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-7153 addressed this but the fix only solved the array syntax - not the white list. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. zkcli fails when SERVER_GC_OPTS is enabled -- Key: HBASE-8025 URL: https://issues.apache.org/jira/browse/HBASE-8025 Project: HBase Issue Type: Bug Affects Versions: 0.94.4 Reporter: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.7 Attachments: HBASE-8025-0.94.patch HBASE-7091 added logic to separate GC logging options for some client commands versus server commands. It uses a list of known client commands (shell hbck hlog hfile zkcli) and uses the server GC logging options for all other invocations of bin/hbase. When zkcli is invoked, it in turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to gather the server command line arguments, but because org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white list it enables server GC logging, which causes extra output that causes the zkcli invocation to break. HBASE-7153 addressed this but the fix only solved the array syntax - not the white list, so the zkcli command still fails. There are many other tools you can invoke that are more likely to client than server options. For example, bin/hbase org.jruby.Main region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable or bin/hbase version or bin/hbase org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands is shorter and easier to maintain than a whitelist of client commands. -- This message is automatically generated by JIRA. If 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-7904) Upgrade hadoop 2.0 dependency to 2.0.4-alpha
[ https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595943#comment-13595943 ] Andrew Purtell commented on HBASE-7904: --- [~yuzhih...@gmail.com] Consider putting up a patch on this jira that hacks the pom to specify 2.0.4-SNAPSHOT and activate the 2.0 profile by default. If all tests pass then I will change my vote to -0. Upgrade hadoop 2.0 dependency to 2.0.4-alpha Key: HBASE-7904 URL: https://issues.apache.org/jira/browse/HBASE-7904 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.95.0 Attachments: 7904.txt, 7904-v2.txt, hbase-7904-v3.txt 2.0.3-alpha has been released. We should upgrade the dependency. -- This message is automatically generated by JIRA. If 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-7904) Upgrade hadoop 2.0 dependency to 2.0.4-alpha
[ https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-7904: -- Priority: Critical (was: Major) Upgrade hadoop 2.0 dependency to 2.0.4-alpha Key: HBASE-7904 URL: https://issues.apache.org/jira/browse/HBASE-7904 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Ted Yu Priority: Critical Fix For: 0.95.0 Attachments: 7904.txt, 7904-v2.txt, hbase-7904-v3.txt 2.0.3-alpha has been released. We should upgrade the dependency. -- This message is automatically generated by JIRA. If 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-8017) Upgrade hadoop 1 dependency to 1.1.2
[ https://issues.apache.org/jira/browse/HBASE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595949#comment-13595949 ] Ted Yu commented on HBASE-8017: --- TestMasterFailover fails locally with hadoop 1.1.2 but not 1.1.1 Will investigate. Upgrade hadoop 1 dependency to 1.1.2 Key: HBASE-8017 URL: https://issues.apache.org/jira/browse/HBASE-8017 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.98.0 Attachments: 8017.txt, 8017.txt Hadoop 1.1.2 has been released. From Matt: This release includes 24 bug fixes and backward-compatible enhancements, compared to Hadoop 1.1.1. Improvements include: - bug fixes in use of Kerberos security and SPNEGO - a couple potential deadlock situations - fixes for IBM JDK compatibility - several unit test failure cleanups - other useful improvements For details, please see http://hadoop.apache.org/docs/r1.1.2/releasenotes.html. -- This message is automatically generated by JIRA. If 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-7845) optimize hfile index key
[
https://issues.apache.org/jira/browse/HBASE-7845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595985#comment-13595985
]
Ted Yu commented on HBASE-7845:
---
{code}
return 0; // indicate exact match
-}
-
-if (comp 0) {
+} else if (comp 0) {
{code}
There is no need to introduce 'else' above
{code}
+if (comparator instanceof KeyComparator
blockEncoder.getEncodingOnDisk() ==
+DataBlockEncoding.NONE blockEncoder.getEncodingInCache() ==
DataBlockEncoding.NONE) {
{code}
This limits the scenarios where the optimization applies. Can we do better ?
{code}
+ byte[] shortestSeparator = ((KeyComparator) comparator).getFakedKey(
{code}
Suggest aligning variable name with method name: how about fakeKey ?
{code}
+ if (comparator.compare(shortestSeparator, firstKeyInBlock) 0) {
+throw new IOException(Unexpected getFakedKey result,
shortestSeparator: +
+ shortestSeparator + , firstKeyInBlock: + firstKeyInBlock);
{code}
Can we log an error message and fall back to adding firstKeyInBlock ?
optimize hfile index key
Key: HBASE-7845
URL: https://issues.apache.org/jira/browse/HBASE-7845
Project: HBase
Issue Type: Improvement
Components: HFile
Affects Versions: 0.96.0
Reporter: Liang Xie
Assignee: Liang Xie
Fix For: 0.98.0
Attachments: HBASE-7845.txt, HBASE-7845-v2.txt, HBASE-7845-v3.txt,
HBASE-7845-v4.txt
Leveldb uses ByteWiseComparatorImpl::FindShortestSeparator()
FindShortSuccessor() to reduce index key size, it would be helpful under
special conditions.
--
This message is automatically generated by JIRA.
If 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-8025) zkcli fails when SERVER_GC_OPTS is enabled
[
https://issues.apache.org/jira/browse/HBASE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595988#comment-13595988
]
Hadoop QA commented on HBASE-8025:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572542/HBASE-8025-0.94.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color: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:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//console
This message is automatically generated.
zkcli fails when SERVER_GC_OPTS is enabled
--
Key: HBASE-8025
URL: https://issues.apache.org/jira/browse/HBASE-8025
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.4
Reporter: Dave Latham
Fix For: 0.95.0, 0.98.0, 0.94.7
Attachments: HBASE-8025-0.94.patch
HBASE-7091 added logic to separate GC logging options for some client
commands versus server commands. It uses a list of known client commands
(shell hbck hlog hfile zkcli) and uses the server GC logging
options for all other invocations of bin/hbase. When zkcli is invoked, it in
turn invokes hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg
to gather the server command line arguments, but because
org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white
list it enables server GC logging, which causes extra output that causes the
zkcli invocation to break. HBASE-7153 addressed this but the fix only solved
the array syntax - not the white list, so the zkcli command still fails.
There are many other tools you can invoke that are more likely to client
than server options. For example, bin/hbase org.jruby.Main
region_mover.rb or bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable
or bin/hbase version or bin/hbase
org.apache.hadoop.hbase.mapreduce.Export. The whitelist of server commands
is shorter and easier to maintain than a whitelist of client commands.
--
This message is automatically generated by JIRA.
If 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-8017) Upgrade hadoop 1 dependency to 1.1.2
[
https://issues.apache.org/jira/browse/HBASE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595993#comment-13595993
]
Hadoop QA commented on HBASE-8017:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572541/8017.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 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:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.procedure.TestZKProcedureControllers
org.apache.hadoop.hbase.regionserver.wal.TestHLog
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.util.TestHBaseFsck.testValidLingeringSplitParent(TestHBaseFsck.java:1314)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4714//console
This message is automatically generated.
Upgrade hadoop 1 dependency to 1.1.2
Key: HBASE-8017
URL: https://issues.apache.org/jira/browse/HBASE-8017
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.98.0
Attachments: 8017.txt, 8017.txt
Hadoop 1.1.2 has been released.
From Matt:
This release includes 24 bug fixes and backward-compatible enhancements,
compared to Hadoop 1.1.1. Improvements include:
- bug fixes in use of Kerberos security and SPNEGO
- a couple potential deadlock situations
- fixes for IBM JDK compatibility
- several unit test failure cleanups
- other useful improvements
For details, please see
http://hadoop.apache.org/docs/r1.1.2/releasenotes.html.
--
This message is automatically generated by JIRA.
If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595995#comment-13595995 ] Richard Ding commented on HBASE-8019: - Thanks Lars. We tried HBASE-7779 and it fixed the shutdown issue. The original problem occurs even if you just start and then stop HBase. Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-8023) Assembly target fails
[
https://issues.apache.org/jira/browse/HBASE-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595996#comment-13595996
]
nkeywal commented on HBASE-8023:
mvn clean package -DskipTests assembly:assembly -Dhadoop.profile=2.0
works here.
but
mvn clean package site -DskipTests assembly:assembly -Dhadoop.profile=2.0
does not
[INFO] Processing input file: book.xml
[INFO] Applying customization parameters
[INFO] Chunking output.
Recoverable error
org.xml.sax.SAXParseException: Include operation failed, reverting to fallback.
Resource error reading file as XML
(href='../../target/site/hbase-default.xml'). Reason:
/home/liochon/dev/hbase/target/site/hbase-default.xml (No such file or
directory)
Error on line 672 column 52 of
file:///home/liochon/dev/hbase/src/docbkx/configuration.xml:
Error reported by XML parser: An 'include' failed, and no 'fallback' element
was found.
Error on line 70 column 85 of
file:///home/liochon/dev/hbase/src/docbkx/book.xml:
Error reported by XML parser: Error attempting to parse XML file
(href='configuration.xml').
[INFO]
I'm testing but I think it's not related to the 2.0 profile, just site.
Assembly target fails
-
Key: HBASE-8023
URL: https://issues.apache.org/jira/browse/HBASE-8023
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
The assembly target fails when using the 2.0 Hadoop profile (at least).
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
[INFO] --- maven-assembly-plugin:2.3:assembly (default-cli) @ hbase ---
[INFO] Reading assembly descriptor: src/assembly/hadoop-two-compat.xml
[WARNING] [DEPRECATION] moduleSet/binaries section detected in root-project
assembly.
MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY!
To refactor, move this assembly into a child project and use the flag
useAllReactorProjectstrue/useAllReactorProjects in each moduleSet.
[INFO] Processing sources for module project:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-protocol:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-client:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-prefix-tree:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop2-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-server:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-it:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-examples:jar:0.97-SNAPSHOT
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [15.877s]
[INFO] HBase - Common SUCCESS [4.633s]
[INFO] HBase - Protocol .. SUCCESS [2.629s]
[INFO] HBase - Client SUCCESS [2.901s]
[INFO] HBase - Prefix Tree ... SUCCESS [3.085s]
[INFO] HBase - Hadoop Compatibility .. SUCCESS [2.647s]
[INFO] HBase - Hadoop Two Compatibility .. SUCCESS [2.005s]
[INFO] HBase - Server SUCCESS [1.888s]
[INFO] HBase - Integration Tests . SUCCESS [6.917s]
[INFO] HBase - Examples .. SUCCESS [2.815s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6:41.503s
[INFO] Finished at: Thu Mar 07 22:14:08 CST 2013
[INFO] Final Memory: 67M/448M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.3:assembly (default-cli) on
project hbase: Failed to create assembly: Artifact:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-8023) Assembly target fails
[
https://issues.apache.org/jira/browse/HBASE-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596012#comment-13596012
]
nkeywal commented on HBASE-8023:
Ah, I'm just seeing that you created HBASE-8022 for the site part. I confirm
assembly w/o the site works here.
If the assembly w/o the site still fails for you, it's worth doing a mvn clean
install -DskipTests first.
Assembly target fails
-
Key: HBASE-8023
URL: https://issues.apache.org/jira/browse/HBASE-8023
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
The assembly target fails when using the 2.0 Hadoop profile (at least).
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
[INFO] --- maven-assembly-plugin:2.3:assembly (default-cli) @ hbase ---
[INFO] Reading assembly descriptor: src/assembly/hadoop-two-compat.xml
[WARNING] [DEPRECATION] moduleSet/binaries section detected in root-project
assembly.
MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY!
To refactor, move this assembly into a child project and use the flag
useAllReactorProjectstrue/useAllReactorProjects in each moduleSet.
[INFO] Processing sources for module project:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-protocol:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-client:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-prefix-tree:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-hadoop2-compat:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-server:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-it:jar:0.97-SNAPSHOT
[INFO] Processing sources for module project:
org.apache.hbase:hbase-examples:jar:0.97-SNAPSHOT
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [15.877s]
[INFO] HBase - Common SUCCESS [4.633s]
[INFO] HBase - Protocol .. SUCCESS [2.629s]
[INFO] HBase - Client SUCCESS [2.901s]
[INFO] HBase - Prefix Tree ... SUCCESS [3.085s]
[INFO] HBase - Hadoop Compatibility .. SUCCESS [2.647s]
[INFO] HBase - Hadoop Two Compatibility .. SUCCESS [2.005s]
[INFO] HBase - Server SUCCESS [1.888s]
[INFO] HBase - Integration Tests . SUCCESS [6.917s]
[INFO] HBase - Examples .. SUCCESS [2.815s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6:41.503s
[INFO] Finished at: Thu Mar 07 22:14:08 CST 2013
[INFO] Final Memory: 67M/448M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.3:assembly (default-cli) on
project hbase: Failed to create assembly: Artifact:
org.apache.hbase:hbase-common:jar:0.97-SNAPSHOT (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596020#comment-13596020 ] Lars Hofhansl commented on HBASE-8019: -- Unfortunately this seems to prevent TestRestoreSnapshotFromClient fro finishing. Since this commit the test has not finished in the following 4 runs. Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (HBASE-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reopened HBASE-8019: -- Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-7244) Provide a command or argument to startup, that formats znodes if provided
[
https://issues.apache.org/jira/browse/HBASE-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rajeshbabu updated HBASE-7244:
--
Assignee: rajeshbabu
Provide a command or argument to startup, that formats znodes if provided
-
Key: HBASE-7244
URL: https://issues.apache.org/jira/browse/HBASE-7244
Project: HBase
Issue Type: New Feature
Components: Zookeeper
Affects Versions: 0.94.0
Reporter: Harsh J
Assignee: rajeshbabu
Priority: Minor
Attachments: HBASE-7244.patch
Many a times I've had to, and have seen instructions being thrown, to stop
cluster, clear out ZK and restart.
While this is only a quick (and painful to master) fix, it is certainly nifty
to some smaller cluster users but the process is far too long, roughly:
1. Stop HBase
2. Start zkCli.sh and connect to the right quorum
3. Find and ensure the HBase parent znode from the configs (/hbase only by
default)
4. Run an rmr /hbase in the zkCli.sh shell, or manually delete each znode
if on a lower version of ZK.
5. Quit zkCli.sh and start HBase again
Perhaps it may be useful, if the start-hbase.sh itself accepted a formatZK
parameter. Such that, when you do a {{start-hbase.sh -formatZK}}, it does
steps 2-4 automatically for you.
For safety, we could make the formatter code ensure that no HBase instance is
actually active, and skip the format process if it is. Similar to a HDFS
NameNode's format, which would disallow if the name directories are locked.
Would this be a useful addition for administrators? Bigtop too can provide a
service subcommand that could do this.
--
This message is automatically generated by JIRA.
If 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-7153) print gc option in hbase-env.sh affects hbase zkcli
[ https://issues.apache.org/jira/browse/HBASE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596032#comment-13596032 ] Lars Hofhansl commented on HBASE-7153: -- Thanks Dave. I see, you're right. Since this is wrong, we can it here or in HBASE-8025. print gc option in hbase-env.sh affects hbase zkcli --- Key: HBASE-7153 URL: https://issues.apache.org/jira/browse/HBASE-7153 Project: HBase Issue Type: Bug Components: scripts Affects Versions: 0.94.0 Reporter: wonderyl Assignee: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.6 Attachments: 7153-0.94.txt, HBASE-7153-0.94.patch I un-commented the -verbose:gc option in hbase-env.sh, which print out the gc info. but when I use hbase zkcli to check zk, it can not connect to the server. the problem is zkcli uses hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to get the server_arg in the script hbase. when gc verbose option is open, the output of ZooKeeperMainServerArg is with gc info, which masses up with server_arg. and this is the reason stop zkcli working. I think the easiest way to fix this is to trim the gc info out of server_arg in the hbase script. -- This message is automatically generated by JIRA. If 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-7153) print gc option in hbase-env.sh affects hbase zkcli
[ https://issues.apache.org/jira/browse/HBASE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596034#comment-13596034 ] Dave Latham commented on HBASE-7153: Since this one is committed, let's continue in HBASE-8025. print gc option in hbase-env.sh affects hbase zkcli --- Key: HBASE-7153 URL: https://issues.apache.org/jira/browse/HBASE-7153 Project: HBase Issue Type: Bug Components: scripts Affects Versions: 0.94.0 Reporter: wonderyl Assignee: Dave Latham Fix For: 0.95.0, 0.98.0, 0.94.6 Attachments: 7153-0.94.txt, HBASE-7153-0.94.patch I un-commented the -verbose:gc option in hbase-env.sh, which print out the gc info. but when I use hbase zkcli to check zk, it can not connect to the server. the problem is zkcli uses hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to get the server_arg in the script hbase. when gc verbose option is open, the output of ZooKeeperMainServerArg is with gc info, which masses up with server_arg. and this is the reason stop zkcli working. I think the easiest way to fix this is to trim the gc info out of server_arg in the hbase script. -- This message is automatically generated by JIRA. If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596045#comment-13596045 ] Lars Hofhansl commented on HBASE-8019: -- This doesn't appear to happen locally. Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[
https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596059#comment-13596059
]
Ted Yu commented on HBASE-8019:
---
The HBase-0.94-security build passed.
On Linux with security profile:
{code}
Tests run: 1377, Failures: 0, Errors: 0, Skipped: 13
[INFO]
[INFO] BUILD SUCCESS
{code}
I am running test suite without security profile
On Mac, the test passes.
Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
---
Key: HBASE-8019
URL: https://issues.apache.org/jira/browse/HBASE-8019
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.94.6
Attachments: 8019-94.txt
Richard Ding reported long delay in shutting down RegionServerSnapshotManager
Looks like HBASE-7779 wasn't included in the backport
--
This message is automatically generated by JIRA.
If 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-8011) Refactor ImportTsv
[ https://issues.apache.org/jira/browse/HBASE-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-8011: Attachment: 0001-HBASE-8011-Refactor-ImportTsv.patch Ha! Fixed and fixed. Thanks. Refactor ImportTsv -- Key: HBASE-8011 URL: https://issues.apache.org/jira/browse/HBASE-8011 Project: HBase Issue Type: Improvement Components: mapreduce, Usability Reporter: Nick Dimiduk Assignee: Nick Dimiduk Priority: Minor Attachments: 0001-HBASE-8011-Refactor-ImportTsv.patch, 0001-HBASE-8011-Refactor-ImportTsv.patch ImportTsv is a little goofy. - It doesn't use the Tool,Configured interfaces like a mapreduce job should. - It has a static HBaseAdmin field that must be initialized before the intended API of createSubmittableJob can be invoked. - TsvParser is critical to the default mapper implementation but is unavailable to user custom mapper implementations without forcing them into the o.a.h.h.mapreduce namespace. - The configuration key constants are not public. -- This message is automatically generated by JIRA. If 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-8011) Refactor ImportTsv
[ https://issues.apache.org/jira/browse/HBASE-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-8011: Status: Open (was: Patch Available) Refactor ImportTsv -- Key: HBASE-8011 URL: https://issues.apache.org/jira/browse/HBASE-8011 Project: HBase Issue Type: Improvement Components: mapreduce, Usability Reporter: Nick Dimiduk Assignee: Nick Dimiduk Priority: Minor Attachments: 0001-HBASE-8011-Refactor-ImportTsv.patch, 0001-HBASE-8011-Refactor-ImportTsv.patch ImportTsv is a little goofy. - It doesn't use the Tool,Configured interfaces like a mapreduce job should. - It has a static HBaseAdmin field that must be initialized before the intended API of createSubmittableJob can be invoked. - TsvParser is critical to the default mapper implementation but is unavailable to user custom mapper implementations without forcing them into the o.a.h.h.mapreduce namespace. - The configuration key constants are not public. -- This message is automatically generated by JIRA. If 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-8011) Refactor ImportTsv
[ https://issues.apache.org/jira/browse/HBASE-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-8011: Status: Patch Available (was: Open) Refactor ImportTsv -- Key: HBASE-8011 URL: https://issues.apache.org/jira/browse/HBASE-8011 Project: HBase Issue Type: Improvement Components: mapreduce, Usability Reporter: Nick Dimiduk Assignee: Nick Dimiduk Priority: Minor Attachments: 0001-HBASE-8011-Refactor-ImportTsv.patch, 0001-HBASE-8011-Refactor-ImportTsv.patch ImportTsv is a little goofy. - It doesn't use the Tool,Configured interfaces like a mapreduce job should. - It has a static HBaseAdmin field that must be initialized before the intended API of createSubmittableJob can be invoked. - TsvParser is critical to the default mapper implementation but is unavailable to user custom mapper implementations without forcing them into the o.a.h.h.mapreduce namespace. - The configuration key constants are not public. -- This message is automatically generated by JIRA. If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596077#comment-13596077 ] Lars Hofhansl commented on HBASE-8019: -- TestRestoreSnapshotFromClient is not part of the tests run by the -security suite. If you look at the 0.94 tests you see that org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient is there in build #883 and none of the following build. This was committed in #884. I still have not been able to produce this locally. Will try another machine now with a different JVM now. Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-8022) Site target fails
[
https://issues.apache.org/jira/browse/HBASE-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596078#comment-13596078
]
Nick Dimiduk commented on HBASE-8022:
-
+1
Site target fails
-
Key: HBASE-8022
URL: https://issues.apache.org/jira/browse/HBASE-8022
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
Attachments: HBASE-8022.patch
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
Recoverable error
org.xml.sax.SAXParseException: Include operation failed, reverting to
fallback. Resource error reading file as XML
(href='../../target/site/hbase-default.xml'). Reason:
/usr/src/Hadoop/hbase/target/site/hbase-default.xml (No such file or
directory)
Error on line 672 column 52 of
file:///usr/src/Hadoop/hbase/src/docbkx/configuration.xml:
Error reported by XML parser: An 'include' failed, and no 'fallback'
element was found.
[INFO]
[INFO]
[INFO] Skipping HBase
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [5:34.980s]
[INFO] HBase - Common SKIPPED
[INFO] HBase - Protocol .. SKIPPED
[INFO] HBase - Client SKIPPED
[INFO] HBase - Prefix Tree ... SKIPPED
[INFO] HBase - Hadoop Compatibility .. SKIPPED
[INFO] HBase - Hadoop Two Compatibility .. SKIPPED
[INFO] HBase - Server SKIPPED
[INFO] HBase - Integration Tests . SKIPPED
[INFO] HBase - Examples .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5:36.029s
[INFO] Finished at: Thu Mar 07 21:59:14 CST 2013
[INFO] Final Memory: 29M/297M
[INFO]
[ERROR] Failed to execute goal
com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html (multipage) on
project hbase: Failed to transform configuration.xml.
org.xml.sax.SAXParseException: An 'include' failed, and no 'fallback' element
was found. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596087#comment-13596087 ] Ted Yu commented on HBASE-8019: --- Strange, I see other snapshot test(s) in secure build: Running org.apache.hadoop.hbase.snapshot.TestExportSnapshot Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 30.168 sec Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[
https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596084#comment-13596084
]
Lars Hofhansl commented on HBASE-8019:
--
From the log I see this:
{code}
---
Test set: org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient
---
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 438.4 sec
{code}
So only 5 of the 6 tests ran. Can't tell which one didn't, though.
Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
---
Key: HBASE-8019
URL: https://issues.apache.org/jira/browse/HBASE-8019
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Fix For: 0.94.6
Attachments: 8019-94.txt
Richard Ding reported long delay in shutting down RegionServerSnapshotManager
Looks like HBASE-7779 wasn't included in the backport
--
This message is automatically generated by JIRA.
If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596089#comment-13596089 ] Lars Hofhansl commented on HBASE-8019: -- Oops wrong test. There are no logs for TestRestoreSnapshotFromClient :( Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-8022) Site target fails
[
https://issues.apache.org/jira/browse/HBASE-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596091#comment-13596091
]
stack commented on HBASE-8022:
--
+1
Site target fails
-
Key: HBASE-8022
URL: https://issues.apache.org/jira/browse/HBASE-8022
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
Attachments: HBASE-8022.patch
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
Recoverable error
org.xml.sax.SAXParseException: Include operation failed, reverting to
fallback. Resource error reading file as XML
(href='../../target/site/hbase-default.xml'). Reason:
/usr/src/Hadoop/hbase/target/site/hbase-default.xml (No such file or
directory)
Error on line 672 column 52 of
file:///usr/src/Hadoop/hbase/src/docbkx/configuration.xml:
Error reported by XML parser: An 'include' failed, and no 'fallback'
element was found.
[INFO]
[INFO]
[INFO] Skipping HBase
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [5:34.980s]
[INFO] HBase - Common SKIPPED
[INFO] HBase - Protocol .. SKIPPED
[INFO] HBase - Client SKIPPED
[INFO] HBase - Prefix Tree ... SKIPPED
[INFO] HBase - Hadoop Compatibility .. SKIPPED
[INFO] HBase - Hadoop Two Compatibility .. SKIPPED
[INFO] HBase - Server SKIPPED
[INFO] HBase - Integration Tests . SKIPPED
[INFO] HBase - Examples .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5:36.029s
[INFO] Finished at: Thu Mar 07 21:59:14 CST 2013
[INFO] Final Memory: 29M/297M
[INFO]
[ERROR] Failed to execute goal
com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html (multipage) on
project hbase: Failed to transform configuration.xml.
org.xml.sax.SAXParseException: An 'include' failed, and no 'fallback' element
was found. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-8026) HBase Shell docs for scan command don't reference VERSIONS
Jonathan Natkins created HBASE-8026: --- Summary: HBase Shell docs for scan command don't reference VERSIONS Key: HBASE-8026 URL: https://issues.apache.org/jira/browse/HBASE-8026 Project: HBase Issue Type: Bug Reporter: Jonathan Natkins hbase(main):046:0 help 'scan' Scan a table; pass table name and optionally a dictionary of scanner specifications. Scanner specifications may include one or more of: TIMERANGE, FILTER, LIMIT, STARTROW, STOPROW, TIMESTAMP, MAXLENGTH, or COLUMNS, CACHE VERSIONS should be mentioned somewhere here. -- This message is automatically generated by JIRA. If 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-8026) HBase Shell docs for scan command don't reference VERSIONS
[ https://issues.apache.org/jira/browse/HBASE-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David S. Wang updated HBASE-8026: - Labels: noob (was: ) HBase Shell docs for scan command don't reference VERSIONS -- Key: HBASE-8026 URL: https://issues.apache.org/jira/browse/HBASE-8026 Project: HBase Issue Type: Bug Reporter: Jonathan Natkins Labels: noob hbase(main):046:0 help 'scan' Scan a table; pass table name and optionally a dictionary of scanner specifications. Scanner specifications may include one or more of: TIMERANGE, FILTER, LIMIT, STARTROW, STOPROW, TIMESTAMP, MAXLENGTH, or COLUMNS, CACHE VERSIONS should be mentioned somewhere here. -- This message is automatically generated by JIRA. If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596111#comment-13596111 ] Lars Hofhansl commented on HBASE-8019: -- Does not happen on other machine/jvm either. Hmm... Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-7904) Upgrade hadoop 2.0 dependency to 2.0.4-alpha
[ https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596116#comment-13596116 ] stack commented on HBASE-7904: -- I would be +1 on our building against a 2.0.4-SNAPSHOT. Will help with us with pushing incompatibility feedback upstream. Upgrade hadoop 2.0 dependency to 2.0.4-alpha Key: HBASE-7904 URL: https://issues.apache.org/jira/browse/HBASE-7904 Project: HBase Issue Type: Task Reporter: Ted Yu Assignee: Ted Yu Priority: Critical Fix For: 0.95.0 Attachments: 7904.txt, 7904-v2.txt, hbase-7904-v3.txt 2.0.3-alpha has been released. We should upgrade the dependency. -- This message is automatically generated by JIRA. If 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-8027) hbase-7994 redux; shutdown hbase-example unit tests
stack created HBASE-8027: Summary: hbase-7994 redux; shutdown hbase-example unit tests Key: HBASE-8027 URL: https://issues.apache.org/jira/browse/HBASE-8027 Project: HBase Issue Type: Bug Reporter: stack My patch on hbase-7994 did not stop clusters starting though no test to run (adding the @Ignore in front of the @before and @after class). All tests passed on build #34 but for the failed hbase-examples cluster startups: https://builds.apache.org/job/hbase-0.95/34/ -- This message is automatically generated by JIRA. If 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-8027) hbase-7994 redux; shutdown hbase-example unit tests
[ https://issues.apache.org/jira/browse/HBASE-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-8027. -- Resolution: Fixed Resolving. hbase-7994 redux; shutdown hbase-example unit tests --- Key: HBASE-8027 URL: https://issues.apache.org/jira/browse/HBASE-8027 Project: HBase Issue Type: Bug Reporter: stack Attachments: 8027.txt My patch on hbase-7994 did not stop clusters starting though no test to run (adding the @Ignore in front of the @before and @after class). All tests passed on build #34 but for the failed hbase-examples cluster startups: https://builds.apache.org/job/hbase-0.95/34/ -- This message is automatically generated by JIRA. If 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-8027) hbase-7994 redux; shutdown hbase-example unit tests
[ https://issues.apache.org/jira/browse/HBASE-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8027: - Component/s: test Fix Version/s: 0.95.0 Assignee: stack hbase-7994 redux; shutdown hbase-example unit tests --- Key: HBASE-8027 URL: https://issues.apache.org/jira/browse/HBASE-8027 Project: HBase Issue Type: Bug Components: test Reporter: stack Assignee: stack Fix For: 0.95.0 Attachments: 8027.txt My patch on hbase-7994 did not stop clusters starting though no test to run (adding the @Ignore in front of the @before and @after class). All tests passed on build #34 but for the failed hbase-examples cluster startups: https://builds.apache.org/job/hbase-0.95/34/ -- This message is automatically generated by JIRA. If 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-8027) hbase-7994 redux; shutdown hbase-example unit tests
[ https://issues.apache.org/jira/browse/HBASE-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8027: - Attachment: 8027.txt What I applied to 0.95 and trunk. I commented out all junit annotations. hbase-7994 redux; shutdown hbase-example unit tests --- Key: HBASE-8027 URL: https://issues.apache.org/jira/browse/HBASE-8027 Project: HBase Issue Type: Bug Reporter: stack Attachments: 8027.txt My patch on hbase-7994 did not stop clusters starting though no test to run (adding the @Ignore in front of the @before and @after class). All tests passed on build #34 but for the failed hbase-examples cluster startups: https://builds.apache.org/job/hbase-0.95/34/ -- This message is automatically generated by JIRA. If 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-8011) Refactor ImportTsv
[ https://issues.apache.org/jira/browse/HBASE-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596135#comment-13596135 ] Sergey Shelukhin commented on HBASE-8011: - +1 Refactor ImportTsv -- Key: HBASE-8011 URL: https://issues.apache.org/jira/browse/HBASE-8011 Project: HBase Issue Type: Improvement Components: mapreduce, Usability Reporter: Nick Dimiduk Assignee: Nick Dimiduk Priority: Minor Attachments: 0001-HBASE-8011-Refactor-ImportTsv.patch, 0001-HBASE-8011-Refactor-ImportTsv.patch ImportTsv is a little goofy. - It doesn't use the Tool,Configured interfaces like a mapreduce job should. - It has a static HBaseAdmin field that must be initialized before the intended API of createSubmittableJob can be invoked. - TsvParser is critical to the default mapper implementation but is unavailable to user custom mapper implementations without forcing them into the o.a.h.h.mapreduce namespace. - The configuration key constants are not public. -- This message is automatically generated by JIRA. If 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-8011) Refactor ImportTsv
[
https://issues.apache.org/jira/browse/HBASE-8011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596143#comment-13596143
]
Hadoop QA commented on HBASE-8011:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572560/0001-HBASE-8011-Refactor-ImportTsv.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 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:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestHTableMultiplexer
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4715//console
This message is automatically generated.
Refactor ImportTsv
--
Key: HBASE-8011
URL: https://issues.apache.org/jira/browse/HBASE-8011
Project: HBase
Issue Type: Improvement
Components: mapreduce, Usability
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
Priority: Minor
Attachments: 0001-HBASE-8011-Refactor-ImportTsv.patch,
0001-HBASE-8011-Refactor-ImportTsv.patch
ImportTsv is a little goofy.
- It doesn't use the Tool,Configured interfaces like a mapreduce job should.
- It has a static HBaseAdmin field that must be initialized before the
intended API of createSubmittableJob can be invoked.
- TsvParser is critical to the default mapper implementation but is
unavailable to user custom mapper implementations without forcing them into
the o.a.h.h.mapreduce namespace.
- The configuration key constants are not public.
--
This message is automatically generated by JIRA.
If 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-7948) client doesn't need to refresh meta while the region is opening
[ https://issues.apache.org/jira/browse/HBASE-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596148#comment-13596148 ] Sergey Shelukhin commented on HBASE-7948: - The patch addresses the condition where RegionMovedException and slow region open causes the client to go back and forth between old and new server, hitting meta every other time. In HBASE-7649 I also want to make timeout server-dependent, so going to new server earlier will be more prevalent. client doesn't need to refresh meta while the region is opening --- Key: HBASE-7948 URL: https://issues.apache.org/jira/browse/HBASE-7948 Project: HBase Issue Type: Improvement Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Attachments: HBASE-7948-v0.patch, HBASE-7948-v1.patch, HBASE-7948-v1.patch, HBASE-7948-v2.patch, HBASE-7948-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] [Created] (HBASE-8028) Append, Increment doesn't handle wall-sync exceptions correctly
Himanshu Vashishtha created HBASE-8028: -- Summary: Append, Increment doesn't handle wall-sync exceptions correctly Key: HBASE-8028 URL: https://issues.apache.org/jira/browse/HBASE-8028 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 0.94.5 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Fix For: 0.95.0 In case there is an exception while doing the log-sync, the memstore is not rollbacked, while the mvcc is _always_ forwarded to the writeentry created at the beginning of the operation. This may lead to scanners seeing results which are not synched to the fs. -- This message is automatically generated by JIRA. If 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-8028) Append, Increment don't handle wall-sync exceptions correctly
[ https://issues.apache.org/jira/browse/HBASE-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Vashishtha updated HBASE-8028: --- Summary: Append, Increment don't handle wall-sync exceptions correctly (was: Append, Increment doesn't handle wall-sync exceptions correctly) Append, Increment don't handle wall-sync exceptions correctly - Key: HBASE-8028 URL: https://issues.apache.org/jira/browse/HBASE-8028 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 0.94.5 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Fix For: 0.95.0 In case there is an exception while doing the log-sync, the memstore is not rollbacked, while the mvcc is _always_ forwarded to the writeentry created at the beginning of the operation. This may lead to scanners seeing results which are not synched to the fs. -- This message is automatically generated by JIRA. If 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-7989) Client with a cache info on a dead server will wait for 20s before trying another one.
[ https://issues.apache.org/jira/browse/HBASE-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596149#comment-13596149 ] Sergey Shelukhin commented on HBASE-7989: - Dup of HBASE-7649? Client with a cache info on a dead server will wait for 20s before trying another one. -- Key: HBASE-7989 URL: https://issues.apache.org/jira/browse/HBASE-7989 Project: HBase Issue Type: Bug Components: Client Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Scenario is: - fetch the cache in the client - a server dies - try to use a region that is on the dead server This will lead to a 20 second connect timeout. We don't have this in unit test because we have this only is the remote box does not answer. In the unit tests we have immediately a connection refused from the OS. -- This message is automatically generated by JIRA. If 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-7649) client retry timeout doesn't need to do x2 fallback when going to different server
[ https://issues.apache.org/jira/browse/HBASE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-7649: Status: Open (was: Patch Available) Need to get HBASE-7948 in to handle edge case discussed above, then will make smaller patch. client retry timeout doesn't need to do x2 fallback when going to different server -- Key: HBASE-7649 URL: https://issues.apache.org/jira/browse/HBASE-7649 Project: HBase Issue Type: Improvement Components: Client Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin Attachments: HBASE-7649-v0.patch, HBASE-7649-v1.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v2.patch, HBASE-7649-v3.patch, HBASE-7649-v4.patch, HBASE-7649-v5.patch See HBASE-7520. When we go to server A, get a bunch of failures, then finally learn the region is on B it doesn't make sense to wait for 30 seconds before going to B. -- This message is automatically generated by JIRA. If 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-8028) Append, Increment don't handle wall-sync exceptions correctly
[ https://issues.apache.org/jira/browse/HBASE-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596153#comment-13596153 ] Himanshu Vashishtha commented on HBASE-8028: I think we can make use of the local tempMemStore map variable to store the existing KVs, and rather apply the incoming appends, etc in-place (before applying them to the WAL). Those entries will not be visible for read as long as are not moving the mvcc forward, so it should be ok. Now, in case there is an exception, we can restore the previous values from the tempMemstore map. Thoughts on other approaches? Append, Increment don't handle wall-sync exceptions correctly - Key: HBASE-8028 URL: https://issues.apache.org/jira/browse/HBASE-8028 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 0.94.5 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Fix For: 0.95.0 In case there is an exception while doing the log-sync, the memstore is not rollbacked, while the mvcc is _always_ forwarded to the writeentry created at the beginning of the operation. This may lead to scanners seeing results which are not synched to the fs. -- This message is automatically generated by JIRA. If 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-7989) Client with a cache info on a dead server will wait for 20s before trying another one.
[ https://issues.apache.org/jira/browse/HBASE-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596156#comment-13596156 ] Sergey Shelukhin commented on HBASE-7989: - Hmm, nevermind, is this about TCP timeout? Client with a cache info on a dead server will wait for 20s before trying another one. -- Key: HBASE-7989 URL: https://issues.apache.org/jira/browse/HBASE-7989 Project: HBase Issue Type: Bug Components: Client Affects Versions: 0.95.0, 0.98.0 Reporter: nkeywal Scenario is: - fetch the cache in the client - a server dies - try to use a region that is on the dead server This will lead to a 20 second connect timeout. We don't have this in unit test because we have this only is the remote box does not answer. In the unit tests we have immediately a connection refused from the OS. -- This message is automatically generated by JIRA. If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596158#comment-13596158 ] Ted Yu commented on HBASE-8019: --- TestProcedureMember failed in build #888 It passed smoothly on Mac. Should we make its timeout longer ? Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-8029) delete with TS should only delete that cell, not all cells after.
Kevin Odell created HBASE-8029:
--
Summary: delete with TS should only delete that cell, not all
cells after.
Key: HBASE-8029
URL: https://issues.apache.org/jira/browse/HBASE-8029
Project: HBase
Issue Type: Bug
Components: Client, shell
Reporter: Kevin Odell
delete with TS specified will delete all older cells. I know overloading the
cells is not a great model, but sometimes it is useful and you don't want to
delete all old cells.
hbase(main):028:0 truncate 'tre'
Truncating 'tre' table (it may take a while):
- Disabling table...
- Dropping table...
- Creating table...
0 row(s) in 4.6060 seconds
hbase(main):029:0 put 'tre', 'row1', 'cf1:c1', 'abc', 111
0 row(s) in 0.0220 seconds
hbase(main):030:0 put 'tre', 'row1', 'cf1:c1', 'abcd', 112
0 row(s) in 0.0060 seconds
hbase(main):031:0 put 'tre', 'row1', 'cf1:c1', 'abce', 113
0 row(s) in 0.0120 seconds
hbase(main):032:0 scan 'tre', {NAME = 'cf1:c1', VERSIONS = 4}
ROW COLUMN+CELL
row1column=cf1:c1,
timestamp=113, value=abce
row1column=cf1:c1,
timestamp=112, value=abcd
row1column=cf1:c1,
timestamp=111, value=abc
hbase(main):033:0 delete 'tre', 'row1', 'cf1:c1', 112
0 row(s) in 0.0110 seconds
hbase(main):034:0 scan 'tre', {NAME = 'cf1:c1', VERSIONS = 4}
ROW COLUMN+CELL
row1column=cf1:c1,
timestamp=113, value=abce
1 row(s) in 0.0290 seconds
--
This message is automatically generated by JIRA.
If 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-8029) delete with TS should only delete that cell, not all cells after.
[
https://issues.apache.org/jira/browse/HBASE-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596166#comment-13596166
]
Ted Yu commented on HBASE-8029:
---
This was filed as a Bug.
Should this be a feature ?
delete with TS should only delete that cell, not all cells after.
-
Key: HBASE-8029
URL: https://issues.apache.org/jira/browse/HBASE-8029
Project: HBase
Issue Type: Bug
Components: Client, shell
Reporter: Kevin Odell
delete with TS specified will delete all older cells. I know overloading the
cells is not a great model, but sometimes it is useful and you don't want to
delete all old cells.
hbase(main):028:0 truncate 'tre'
Truncating 'tre' table (it may take a while):
- Disabling table...
- Dropping table...
- Creating table...
0 row(s) in 4.6060 seconds
hbase(main):029:0 put 'tre', 'row1', 'cf1:c1', 'abc', 111
0 row(s) in 0.0220 seconds
hbase(main):030:0 put 'tre', 'row1', 'cf1:c1', 'abcd', 112
0 row(s) in 0.0060 seconds
hbase(main):031:0 put 'tre', 'row1', 'cf1:c1', 'abce', 113
0 row(s) in 0.0120 seconds
hbase(main):032:0 scan 'tre', {NAME = 'cf1:c1', VERSIONS = 4}
ROW COLUMN+CELL
row1column=cf1:c1,
timestamp=113, value=abce
row1column=cf1:c1,
timestamp=112, value=abcd
row1column=cf1:c1,
timestamp=111, value=abc
hbase(main):033:0 delete 'tre', 'row1', 'cf1:c1', 112
0 row(s) in 0.0110 seconds
hbase(main):034:0 scan 'tre', {NAME = 'cf1:c1', VERSIONS = 4}
ROW COLUMN+CELL
row1column=cf1:c1,
timestamp=113, value=abce
1 row(s) in 0.0290 seconds
--
This message is automatically generated by JIRA.
If 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-8028) Append, Increment don't handle wal-sync exceptions correctly
[ https://issues.apache.org/jira/browse/HBASE-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-8028: -- Summary: Append, Increment don't handle wal-sync exceptions correctly (was: Append, Increment don't handle wall-sync exceptions correctly) Append, Increment don't handle wal-sync exceptions correctly Key: HBASE-8028 URL: https://issues.apache.org/jira/browse/HBASE-8028 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 0.94.5 Reporter: Himanshu Vashishtha Assignee: Himanshu Vashishtha Fix For: 0.95.0 In case there is an exception while doing the log-sync, the memstore is not rollbacked, while the mvcc is _always_ forwarded to the writeentry created at the beginning of the operation. This may lead to scanners seeing results which are not synched to the fs. -- This message is automatically generated by JIRA. If 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-7819) consider split improvements for stripe compactions
[ https://issues.apache.org/jira/browse/HBASE-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-7819: Assignee: (was: Sergey Shelukhin) consider split improvements for stripe compactions -- Key: HBASE-7819 URL: https://issues.apache.org/jira/browse/HBASE-7819 Project: HBase Issue Type: Sub-task Components: Compaction Reporter: Sergey Shelukhin From discussions in HBASE-7667, and in person. Files cannot be just moved to new regions because of snapshot reliance on that not happening (correct me if I'm wrong). However, obviously we don't need compaction after split if we have files with specific ranges, so we could handle this somehow. On the other hand, if you have 6 fixed stripes, and split into 3 and 3, you'd want to go back to 6 stripes, so when you do compaction in one of the 3 you will want special handling to do 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-8015) Support for Namespaces
[ https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596171#comment-13596171 ] Francis Liu commented on HBASE-8015: [~jesse_yates] I'm hoping to get an dev drop (0.94) by end of next week. I'll try to squeeze in a trunk patch. Does that work for you? Support for Namespaces -- Key: HBASE-8015 URL: https://issues.apache.org/jira/browse/HBASE-8015 Project: HBase Issue Type: New Feature Reporter: Francis Liu Assignee: Francis Liu Attachments: NamespaceDesign.pdf -- This message is automatically generated by JIRA. If 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-8022) Site target fails
[
https://issues.apache.org/jira/browse/HBASE-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596174#comment-13596174
]
nkeywal commented on HBASE-8022:
+1. We should add this to our precommit tests imho.
Site target fails
-
Key: HBASE-8022
URL: https://issues.apache.org/jira/browse/HBASE-8022
Project: HBase
Issue Type: Bug
Affects Versions: 0.95.0, 0.96.0
Reporter: Andrew Purtell
Attachments: HBASE-8022.patch
{noformat}
mvn -DskipTests -Dhadoop.profile=2.0 clean install site assembly:assembly
[...]
Recoverable error
org.xml.sax.SAXParseException: Include operation failed, reverting to
fallback. Resource error reading file as XML
(href='../../target/site/hbase-default.xml'). Reason:
/usr/src/Hadoop/hbase/target/site/hbase-default.xml (No such file or
directory)
Error on line 672 column 52 of
file:///usr/src/Hadoop/hbase/src/docbkx/configuration.xml:
Error reported by XML parser: An 'include' failed, and no 'fallback'
element was found.
[INFO]
[INFO]
[INFO] Skipping HBase
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] HBase . FAILURE [5:34.980s]
[INFO] HBase - Common SKIPPED
[INFO] HBase - Protocol .. SKIPPED
[INFO] HBase - Client SKIPPED
[INFO] HBase - Prefix Tree ... SKIPPED
[INFO] HBase - Hadoop Compatibility .. SKIPPED
[INFO] HBase - Hadoop Two Compatibility .. SKIPPED
[INFO] HBase - Server SKIPPED
[INFO] HBase - Integration Tests . SKIPPED
[INFO] HBase - Examples .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5:36.029s
[INFO] Finished at: Thu Mar 07 21:59:14 CST 2013
[INFO] Final Memory: 29M/297M
[INFO]
[ERROR] Failed to execute goal
com.agilejava.docbkx:docbkx-maven-plugin:2.0.14:generate-html (multipage) on
project hbase: Failed to transform configuration.xml.
org.xml.sax.SAXParseException: An 'include' failed, and no 'fallback' element
was found. - [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-8015) Support for Namespaces
[ https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596175#comment-13596175 ] Jesse Yates commented on HBASE-8015: Yeah, that would be great! Thanks Francis Support for Namespaces -- Key: HBASE-8015 URL: https://issues.apache.org/jira/browse/HBASE-8015 Project: HBase Issue Type: New Feature Reporter: Francis Liu Assignee: Francis Liu Attachments: NamespaceDesign.pdf -- This message is automatically generated by JIRA. If 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-8015) Support for Namespaces
[ https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596177#comment-13596177 ] Ted Yu commented on HBASE-8015: --- @Francis: Can you work on the trunk patch first ? If it gets ready before 0.95 RC0, it can go into 0.95 Thanks Support for Namespaces -- Key: HBASE-8015 URL: https://issues.apache.org/jira/browse/HBASE-8015 Project: HBase Issue Type: New Feature Reporter: Francis Liu Assignee: Francis Liu Attachments: NamespaceDesign.pdf -- This message is automatically generated by JIRA. If 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-8019) Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94
[ https://issues.apache.org/jira/browse/HBASE-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596180#comment-13596180 ] Lars Hofhansl commented on HBASE-8019: -- sure... but that is a different problem. I have not seen a single after this patch where TestRestoreSnapshotFromClient passes. Port HBASE-7779 '[snapshot 130201 merge] Fix TestMultiParallel' to 0.94 --- Key: HBASE-8019 URL: https://issues.apache.org/jira/browse/HBASE-8019 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.94.6 Attachments: 8019-94.txt Richard Ding reported long delay in shutting down RegionServerSnapshotManager Looks like HBASE-7779 wasn't included in the backport -- This message is automatically generated by JIRA. If 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-8015) Support for Namespaces
[ https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Liu updated HBASE-8015: --- Attachment: HBASE-8015_94.patch So it seems we're fine providing a migration script. So I've gone ahead and produced a rough patch with the change. The general idea is to have a TableName class which encapsulates both namespace and tableQualifier (AKA the old table name). And this will be what gets passed around as much as possible internally. Table names are referenced fully qualified otherwise. I've also changed the tableDir on hdfs to include namespace as the parent directory. This will enable us to set HDFS quotas by namespace. I skipped the CRUD related stuff since that seems pretty straightforward. Let me know if this approach is acceptable. Support for Namespaces -- Key: HBASE-8015 URL: https://issues.apache.org/jira/browse/HBASE-8015 Project: HBase Issue Type: New Feature Reporter: Francis Liu Assignee: Francis Liu Attachments: NamespaceDesign.pdf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
