[jira] [Commented] (HBASE-12118) Explain how to grant permission to a namespace in grant command usage
[ https://issues.apache.org/jira/browse/HBASE-12118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152831#comment-14152831 ] Srikanth Srungarapu commented on HBASE-12118: - Thanks, Ashish for working on this issue. I'm oblivious of this usage till a few days back. +1 (non-binding) Explain how to grant permission to a namespace in grant command usage - Key: HBASE-12118 URL: https://issues.apache.org/jira/browse/HBASE-12118 Project: HBase Issue Type: Improvement Components: documentation, shell Affects Versions: 0.98.6.1 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Attachments: HBASE-12118-1.patch, HBASE-12118.patch In the grant command usage, How to grant permission to a namespace is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[ https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152853#comment-14152853 ] Elliott Clark commented on HBASE-12115: --- +1 Fix NumberFormat Exception in TableInputFormatBase. --- Key: HBASE-12115 URL: https://issues.apache.org/jira/browse/HBASE-12115 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Minor Fix For: 1.0.0 Attachments: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Original Estimate: 24h Remaining Estimate: 24h DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12117) Constructors that use Configuration may be harmful
[ https://issues.apache.org/jira/browse/HBASE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152856#comment-14152856 ] stack commented on HBASE-12117: --- Nice graph [~apurtell] How did you make the traces.client.c.svg graph, what loading produced it, and how does it relate to traces.client.c.svg? I see in the latter we spend most CPU reading and writing. Is the former a portion of this latter graph or another loading? Constructors that use Configuration may be harmful -- Key: HBASE-12117 URL: https://issues.apache.org/jira/browse/HBASE-12117 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Attachments: traces.client.c.svg, traces.client.getHTable.svg There's a common pattern in HBase code where in the constructor, or in an initialization method also called once per instantiation, or both, we look up values from Hadoop Configuration and store them into fields. This can be expensive if the object is frequently created. Configuration is a heavyweight registry that does a lot of string operations and regex matching. See attached example. Method calls into Configuration account for 48.25% of CPU time when creating the HTable object in 0.98. (The remainder is spent instantiating the RPC controller via reflection, a separate issue that merits followup elsewhere.) Creation of HTable instances is expected to be a lightweight operation if a client is using unmanaged HConnections; however creating HTable instances takes up about 18% of the client's total on-CPU time. This is just one example where constructors that use Configuration may be harmful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12116) Hot contention spots; writing
[ https://issues.apache.org/jira/browse/HBASE-12116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152857#comment-14152857 ] stack commented on HBASE-12116: --- [~eclark] Sample was for 5 minutes. There is a small bit of getting values from configuration which does getProperty but main culprit here is not very interesting... its stringifying exceptions (Was throwing loads of NSRE around sample time). Let me get a better sampling. This tool seems to do better job reporting CPU use, or at least, agrees that CRC is the main consumer of CPU as per our flame graph experiments. Hopefully its good reporting contention. Has a dtrace plugin. Let me see if can get that to work Hot contention spots; writing - Key: HBASE-12116 URL: https://issues.apache.org/jira/browse/HBASE-12116 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Attachments: Screen Shot 2014-09-29 at 5.12.51 PM.png Playing with flight recorder, here are some write-time contentious synchronizations/locks (picture coming) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[
https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152861#comment-14152861
]
Hadoop QA commented on HBASE-12115:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12671969/0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch
against trunk revision .
ATTACHMENT ID: 12671969
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.TestCheckTestClasses
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11136//console
This message is automatically generated.
Fix NumberFormat Exception in TableInputFormatBase.
---
Key: HBASE-12115
URL: https://issues.apache.org/jira/browse/HBASE-12115
Project: HBase
Issue Type: Sub-task
Components: test
Affects Versions: 1.0.0
Reporter: Manukranth Kolloju
Assignee: Manukranth Kolloju
Priority: Minor
Fix For: 1.0.0
Attachments:
0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch,
0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch,
0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch,
0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch,
0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch
Original Estimate: 24h
Remaining Estimate: 24h
DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix
that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[ https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152867#comment-14152867 ] stack commented on HBASE-12115: --- +1 after adding size annotation to test (copy from adjacent test. This looks like a smalltest) Fix NumberFormat Exception in TableInputFormatBase. --- Key: HBASE-12115 URL: https://issues.apache.org/jira/browse/HBASE-12115 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Minor Fix For: 1.0.0 Attachments: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Original Estimate: 24h Remaining Estimate: 24h DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[ https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152865#comment-14152865 ] Elliott Clark commented on HBASE-12115: --- Sorry missed that. You need to add the annotation to the test. Fix NumberFormat Exception in TableInputFormatBase. --- Key: HBASE-12115 URL: https://issues.apache.org/jira/browse/HBASE-12115 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Minor Fix For: 1.0.0 Attachments: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Original Estimate: 24h Remaining Estimate: 24h DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12117) Constructors that use Configuration may be harmful
[ https://issues.apache.org/jira/browse/HBASE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152868#comment-14152868 ] Andrew Purtell commented on HBASE-12117: This was YCSB running against an all localhost 0.98 cluster. The old YCSB client. This is workload C. traces.client.getHTable.svg is traces.client.c.svg with all sampled call arcs filtered out except those that go through getHTable, in effect zooming in on a portion of the full trace. Workload C is an all read workload. This is a client trace. Constructors that use Configuration may be harmful -- Key: HBASE-12117 URL: https://issues.apache.org/jira/browse/HBASE-12117 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Attachments: traces.client.c.svg, traces.client.getHTable.svg There's a common pattern in HBase code where in the constructor, or in an initialization method also called once per instantiation, or both, we look up values from Hadoop Configuration and store them into fields. This can be expensive if the object is frequently created. Configuration is a heavyweight registry that does a lot of string operations and regex matching. See attached example. Method calls into Configuration account for 48.25% of CPU time when creating the HTable object in 0.98. (The remainder is spent instantiating the RPC controller via reflection, a separate issue that merits followup elsewhere.) Creation of HTable instances is expected to be a lightweight operation if a client is using unmanaged HConnections; however creating HTable instances takes up about 18% of the client's total on-CPU time. This is just one example where constructors that use Configuration may be harmful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12117) Constructors that use Configuration may be harmful
[ https://issues.apache.org/jira/browse/HBASE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152872#comment-14152872 ] stack commented on HBASE-12117: --- So the focus is on 17% of overall CPU -- the finishSetup of HTable -- and of this most is just getting Configuration. Yuck. This is our making an HTable instance per session? We keep it around? HTable ain't that lightweight then? Any chance of caching some config in Connection for instance? Constructors that use Configuration may be harmful -- Key: HBASE-12117 URL: https://issues.apache.org/jira/browse/HBASE-12117 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Attachments: traces.client.c.svg, traces.client.getHTable.svg There's a common pattern in HBase code where in the constructor, or in an initialization method also called once per instantiation, or both, we look up values from Hadoop Configuration and store them into fields. This can be expensive if the object is frequently created. Configuration is a heavyweight registry that does a lot of string operations and regex matching. See attached example. Method calls into Configuration account for 48.25% of CPU time when creating the HTable object in 0.98. (The remainder is spent instantiating the RPC controller via reflection, a separate issue that merits followup elsewhere.) Creation of HTable instances is expected to be a lightweight operation if a client is using unmanaged HConnections; however creating HTable instances takes up about 18% of the client's total on-CPU time. This is just one example where constructors that use Configuration may be harmful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12073) Shell command user_permission fails on the table created by user if he is not global admin.
[ https://issues.apache.org/jira/browse/HBASE-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-12073: Status: Patch Available (was: Open) Shell command user_permission fails on the table created by user if he is not global admin. -- Key: HBASE-12073 URL: https://issues.apache.org/jira/browse/HBASE-12073 Project: HBase Issue Type: Bug Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-12073.patch The command fails as the changes introduced by HBASE-10892 requires user (because of newly introduced call to getTableDescriptors) to have global admin permission. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12073) Shell command user_permission fails on the table created by user if he is not global admin.
[ https://issues.apache.org/jira/browse/HBASE-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-12073: Attachment: HBASE-12073.patch Attaching the patch for master. Shell command user_permission fails on the table created by user if he is not global admin. -- Key: HBASE-12073 URL: https://issues.apache.org/jira/browse/HBASE-12073 Project: HBase Issue Type: Bug Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-12073.patch The command fails as the changes introduced by HBASE-10892 requires user (because of newly introduced call to getTableDescriptors) to have global admin permission. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12042) Replace internal uses of HTable(Configuration, String) with HTable(Configuration, TableName)
[ https://issues.apache.org/jira/browse/HBASE-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152879#comment-14152879 ] Hudson commented on HBASE-12042: FAILURE: Integrated in HBase-1.0 #246 (See [https://builds.apache.org/job/HBase-1.0/246/]) HBASE-12042 Replace internal uses of HTable(Configuration, String) with HTable(Configuration, TableName) (Solomon Duskis) (enis: rev 1e821bc02a99e9e79e89eba596a31557abbb584d) * hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestColumnRangeFilter.java * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterTransitions.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestLogRollPeriod.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestServerCustomProtocol.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTSVWithOperationAttributes.java * hbase-server/src/test/java/org/apache/hadoop/hbase/TestZooKeeper.java * hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestImportTsv.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTSVWithVisibilityLabels.java * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestMultiParallel.java * hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestLoadAndVerify.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapred/TestTableMapReduceUtil.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java * hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSink.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestCopyTable.java * hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java * hbase-server/src/test/java/org/apache/hadoop/hbase/TestHBaseTestingUtility.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestMultithreadedTableMapper.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/Import.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapred/TestTableMapReduce.java * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/RestartRsHoldingTableAction.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormat.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestWALPlayer.java * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestTimestampsFilter.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHRegionPartitioner.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/WALPlayer.java * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestClientScannerRPCTimeout.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java * hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java * hbase-server/src/test/java/org/apache/hadoop/hbase/TestInfoServers.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/HRegionPartitioner.java * hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestRegionSplitter.java * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide3.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestMultiTableInputFormat.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompactionState.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableOutputFormat.java * hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestRowCounter.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServerMetrics.java * hbase-server/src/main/java/org/apache/hadoop/hbase/tool/Canary.java * hbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityWithCheckAuths.java * hbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityLabelsWithDeletes.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServerNoMaster.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestEncryptionRandomKeying.java * hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestScannerTimeout.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestLogRolling.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/ImportTsv.java * hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestHTableWrapper.java *
[jira] [Commented] (HBASE-12096) In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation
[
https://issues.apache.org/jira/browse/HBASE-12096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152907#comment-14152907
]
Hadoop QA commented on HBASE-12096:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12671964/HBASE-12096.patch
against trunk revision .
ATTACHMENT ID: 12671964
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 2 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestEndToEndSplitTransaction
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint
org.apache.hadoop.hbase.mapreduce.TestCellCounter
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
{color:red}-1 core zombie tests{color}. There are 3 zombie test(s):
at
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles.testSimpleLoad(TestLoadIncrementalHFiles.java:100)
at
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery.testSplitWhileBulkLoadPhase(TestLoadIncrementalHFilesSplitRecovery.java:339)
at
org.apache.hadoop.hbase.client.TestReplicasClient.testSmallScanWithReplicas(TestReplicasClient.java:544)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11133//console
This message is automatically generated.
In ZKSplitLog Coordination and AggregateImplementation replace enhaced for
statements with basic for statement to avoid unnecessary object allocation
-
Key: HBASE-12096
URL: https://issues.apache.org/jira/browse/HBASE-12096
Project: HBase
Issue Type: Sub-task
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-12096.patch, HBASE-12096.patch
In ZKSplitLog Coordination classes and AggregateImplementation replace
enhanced for statements with basic for statement to avoid unnecessary object
allocation
--
This message was sent by
[jira] [Updated] (HBASE-12073) Shell command user_permission fails on the table created by user if he is not global admin.
[ https://issues.apache.org/jira/browse/HBASE-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-12073: Attachment: HBASE-12073.patch Shell command user_permission fails on the table created by user if he is not global admin. -- Key: HBASE-12073 URL: https://issues.apache.org/jira/browse/HBASE-12073 Project: HBase Issue Type: Bug Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-12073.patch The command fails as the changes introduced by HBASE-10892 requires user (because of newly introduced call to getTableDescriptors) to have global admin permission. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12073) Shell command user_permission fails on the table created by user if he is not global admin.
[ https://issues.apache.org/jira/browse/HBASE-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-12073: Attachment: (was: HBASE-12073.patch) Shell command user_permission fails on the table created by user if he is not global admin. -- Key: HBASE-12073 URL: https://issues.apache.org/jira/browse/HBASE-12073 Project: HBase Issue Type: Bug Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-12073.patch The command fails as the changes introduced by HBASE-10892 requires user (because of newly introduced call to getTableDescriptors) to have global admin permission. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12112) Avoid KeyValueUtil#ensureKeyValue some more simple cases
[ https://issues.apache.org/jira/browse/HBASE-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152908#comment-14152908 ] Anoop Sam John commented on HBASE-12112: KeyOnlyFilter exposes lenAsVal as a param. So I fear we can not remove. Avoid KeyValueUtil#ensureKeyValue some more simple cases Key: HBASE-12112 URL: https://issues.apache.org/jira/browse/HBASE-12112 Project: HBase Issue Type: Sub-task Components: regionserver Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12112.patch, HBASE-12112_V2.patch, HBASE-12112_V2.patch This include fixes with - Replace KeyValue#heapSize() with CellUtil#estimatedHeapSizeOf(Cell) - Printing the key portion of a cell (rk+cf+q+ts+type). These are in Exception messages - HFilePrettyPrinter - Avoiding ensureKeyValue() calls and calls to cell#getxxx() which involves bytes copying. This is not a hot area still we can avoid as much usage of deprecated methods as possible in core code. I believe these bytes copying methods are used in many other parts and later we can try fixing those as per area importance - Creating CellUtil#createKeyOnlyCell and using that in KeyOnlyFilter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12116) Hot contention spots; writing
[ https://issues.apache.org/jira/browse/HBASE-12116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12116: -- Attachment: 12116.stringify.and.cache.scanner.maxsize.txt Some small items of contention; cache the max row size so we don't look it up each time which is contentious when lots of threads reading and then stringify exception has us resizing backing array repeatedly. Hot contention spots; writing - Key: HBASE-12116 URL: https://issues.apache.org/jira/browse/HBASE-12116 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Attachments: 12116.stringify.and.cache.scanner.maxsize.txt, Screen Shot 2014-09-29 at 5.12.51 PM.png Playing with flight recorder, here are some write-time contentious synchronizations/locks (picture coming) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-12116) Hot contention spots; writing
[ https://issues.apache.org/jira/browse/HBASE-12116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152914#comment-14152914 ] stack edited comment on HBASE-12116 at 9/30/14 7:54 AM: Some small items of contention; cache the max row size so we don't look it up each time which is contentious when lots of threads reading and then stringify exception has us resizing backing array repeatedly which shows in the sampling window I ran because many NSREs going on. was (Author: stack): Some small items of contention; cache the max row size so we don't look it up each time which is contentious when lots of threads reading and then stringify exception has us resizing backing array repeatedly. Hot contention spots; writing - Key: HBASE-12116 URL: https://issues.apache.org/jira/browse/HBASE-12116 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Attachments: 12116.stringify.and.cache.scanner.maxsize.txt, Screen Shot 2014-09-29 at 5.12.51 PM.png Playing with flight recorder, here are some write-time contentious synchronizations/locks (picture coming) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12112) Avoid KeyValueUtil#ensureKeyValue some more simple cases
[ https://issues.apache.org/jira/browse/HBASE-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152920#comment-14152920 ] stack commented on HBASE-12112: --- Make it a noop? That filters use of the flag is odd. Avoid KeyValueUtil#ensureKeyValue some more simple cases Key: HBASE-12112 URL: https://issues.apache.org/jira/browse/HBASE-12112 Project: HBase Issue Type: Sub-task Components: regionserver Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12112.patch, HBASE-12112_V2.patch, HBASE-12112_V2.patch This include fixes with - Replace KeyValue#heapSize() with CellUtil#estimatedHeapSizeOf(Cell) - Printing the key portion of a cell (rk+cf+q+ts+type). These are in Exception messages - HFilePrettyPrinter - Avoiding ensureKeyValue() calls and calls to cell#getxxx() which involves bytes copying. This is not a hot area still we can avoid as much usage of deprecated methods as possible in core code. I believe these bytes copying methods are used in many other parts and later we can try fixing those as per area importance - Creating CellUtil#createKeyOnlyCell and using that in KeyOnlyFilter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10200) Better error message when HttpServer fails to start due to java.net.BindException
[
https://issues.apache.org/jira/browse/HBASE-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Kumar M R updated HBASE-10200:
Attachment: HBASE-10020.patch
QA build did not pickup patch.
Submitting again.
Better error message when HttpServer fails to start due to
java.net.BindException
-
Key: HBASE-10200
URL: https://issues.apache.org/jira/browse/HBASE-10200
Project: HBase
Issue Type: Task
Affects Versions: 2.0.0
Reporter: Ted Yu
Priority: Minor
Labels: beginner
Attachments: 10200.out, HBASE-10020.patch, HBASE-10020.patch
Starting HBase using Hoya, I saw the following in log:
{code}
2013-12-17 21:49:06,758 INFO [master:hor12n19:42587] http.HttpServer:
HttpServer.start() threw a non Bind IOException
java.net.BindException: Port in use: hor12n14.gq1.ygridcore.net:12432
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:742)
at org.apache.hadoop.http.HttpServer.start(HttpServer.java:686)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:586)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:344)
at sun.nio.ch.Net.bind(Net.java:336)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:738)
{code}
This was due to hbase.master.info.bindAddress giving static address but Hoya
allocates master dynamically.
Better error message should be provided: when bindAddress points another host
than local host, message should remind user to remove / adjust
hbase.master.info.bindAddress config param from hbase-site.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12112) Avoid KeyValueUtil#ensureKeyValue some more simple cases
[ https://issues.apache.org/jira/browse/HBASE-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152962#comment-14152962 ] Anoop Sam John commented on HBASE-12112: HBASE-3211 added this Filter. Any specific reason to add this boolean param? bq.Make it a noop? That filters use of the flag is odd. Any way that can be a different issue I think. There we have to deprecate the constructor taking the boolean( deprecate in 1.0 and remove in 2.0?). Also along with that I can do optimization. Now we can have Cells in read path and no need to recreate a KV and copy key part for returning from this filter transform(). If the boolean can be removed that still easier. I can have a new Cell impl (CellKey itself?) and no need for bytes copy. I can do all these in a follow on issue? Avoid KeyValueUtil#ensureKeyValue some more simple cases Key: HBASE-12112 URL: https://issues.apache.org/jira/browse/HBASE-12112 Project: HBase Issue Type: Sub-task Components: regionserver Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12112.patch, HBASE-12112_V2.patch, HBASE-12112_V2.patch This include fixes with - Replace KeyValue#heapSize() with CellUtil#estimatedHeapSizeOf(Cell) - Printing the key portion of a cell (rk+cf+q+ts+type). These are in Exception messages - HFilePrettyPrinter - Avoiding ensureKeyValue() calls and calls to cell#getxxx() which involves bytes copying. This is not a hot area still we can avoid as much usage of deprecated methods as possible in core code. I believe these bytes copying methods are used in many other parts and later we can try fixing those as per area importance - Creating CellUtil#createKeyOnlyCell and using that in KeyOnlyFilter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12112) Avoid KeyValueUtil#ensureKeyValue some more simple cases
[
https://issues.apache.org/jira/browse/HBASE-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152967#comment-14152967
]
Anoop Sam John commented on HBASE-12112:
As it may change and possibly boolean param not needed in 2.0, I will remove
below from CellUtil
public static Cell createKeyOnlyCell(Cell c, boolean lenAsVal) {
Will handle the creation in Filter class itself as of now.
Also the method and what it is doing is not always matching. CellUtil being
public exposed API, let us not mess it up.
Avoid KeyValueUtil#ensureKeyValue some more simple cases
Key: HBASE-12112
URL: https://issues.apache.org/jira/browse/HBASE-12112
Project: HBase
Issue Type: Sub-task
Components: regionserver
Reporter: Anoop Sam John
Assignee: Anoop Sam John
Fix For: 2.0.0, 0.99.1
Attachments: HBASE-12112.patch, HBASE-12112_V2.patch,
HBASE-12112_V2.patch
This include fixes with
- Replace KeyValue#heapSize() with CellUtil#estimatedHeapSizeOf(Cell)
- Printing the key portion of a cell (rk+cf+q+ts+type). These are in
Exception messages
- HFilePrettyPrinter - Avoiding ensureKeyValue() calls and calls to
cell#getxxx() which involves bytes copying. This is not a hot area still we
can avoid as much usage of deprecated methods as possible in core code. I
believe these bytes copying methods are used in many other parts and later we
can try fixing those as per area importance
- Creating CellUtil#createKeyOnlyCell and using that in KeyOnlyFilter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12096) In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation
[ https://issues.apache.org/jira/browse/HBASE-12096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152992#comment-14152992 ] Ashish Singhi commented on HBASE-12096: --- The test failures are mainly due to time out. Are they flaky ? In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation - Key: HBASE-12096 URL: https://issues.apache.org/jira/browse/HBASE-12096 Project: HBase Issue Type: Sub-task Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0 Attachments: HBASE-12096.patch, HBASE-12096.patch In ZKSplitLog Coordination classes and AggregateImplementation replace enhanced for statements with basic for statement to avoid unnecessary object allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11980) Change sync to hsync, remove unused InfoServer, and reference our httpserver instead of hadoops
[ https://issues.apache.org/jira/browse/HBASE-11980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153038#comment-14153038 ] Hudson commented on HBASE-11980: FAILURE: Integrated in HBase-1.0 #247 (See [https://builds.apache.org/job/HBase-1.0/247/]) HBASE-11980 Change sync to hsync, remove unused InfoServer, and reference our httpserver instead of hadoops (stack: rev ddc6a42f0ff6778129afa49bcd7d2559e35084bd) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogWriter.java * hbase-server/pom.xml * hbase-server/src/main/java/org/apache/hadoop/hbase/http/InfoServer.java * pom.xml * hbase-server/src/main/java/org/apache/hadoop/hbase/util/InfoServer.java Change sync to hsync, remove unused InfoServer, and reference our httpserver instead of hadoops --- Key: HBASE-11980 URL: https://issues.apache.org/jira/browse/HBASE-11980 Project: HBase Issue Type: Sub-task Reporter: stack Assignee: stack Fix For: 2.0.0, 0.99.1 Attachments: 0001-HBASE-11980-Change-sync-to-hsync-remove-unused-InfoS.patch, 11980v2.txt Subtask that fixes a few issues with our building against hadoop3. Get it in. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12112) Avoid KeyValueUtil#ensureKeyValue some more simple cases
[ https://issues.apache.org/jira/browse/HBASE-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-12112: --- Attachment: HBASE-12112_V4.patch Avoid KeyValueUtil#ensureKeyValue some more simple cases Key: HBASE-12112 URL: https://issues.apache.org/jira/browse/HBASE-12112 Project: HBase Issue Type: Sub-task Components: regionserver Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12112.patch, HBASE-12112_V2.patch, HBASE-12112_V2.patch, HBASE-12112_V4.patch This include fixes with - Replace KeyValue#heapSize() with CellUtil#estimatedHeapSizeOf(Cell) - Printing the key portion of a cell (rk+cf+q+ts+type). These are in Exception messages - HFilePrettyPrinter - Avoiding ensureKeyValue() calls and calls to cell#getxxx() which involves bytes copying. This is not a hot area still we can avoid as much usage of deprecated methods as possible in core code. I believe these bytes copying methods are used in many other parts and later we can try fixing those as per area importance - Creating CellUtil#createKeyOnlyCell and using that in KeyOnlyFilter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12118) Explain how to grant permission to a namespace in grant command usage
[ https://issues.apache.org/jira/browse/HBASE-12118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12118: -- Resolution: Fixed Fix Version/s: 0.99.1 0.98.7 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to 0.98+ Thanks [~ashish singhi] and [~srikanth235] Explain how to grant permission to a namespace in grant command usage - Key: HBASE-12118 URL: https://issues.apache.org/jira/browse/HBASE-12118 Project: HBase Issue Type: Improvement Components: documentation, shell Affects Versions: 0.98.6.1 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12118-1.patch, HBASE-12118.patch In the grant command usage, How to grant permission to a namespace is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12112) Avoid KeyValueUtil#ensureKeyValue some more simple cases
[ https://issues.apache.org/jira/browse/HBASE-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153242#comment-14153242 ] stack commented on HBASE-12112: --- +1 Avoid KeyValueUtil#ensureKeyValue some more simple cases Key: HBASE-12112 URL: https://issues.apache.org/jira/browse/HBASE-12112 Project: HBase Issue Type: Sub-task Components: regionserver Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12112.patch, HBASE-12112_V2.patch, HBASE-12112_V2.patch, HBASE-12112_V4.patch This include fixes with - Replace KeyValue#heapSize() with CellUtil#estimatedHeapSizeOf(Cell) - Printing the key portion of a cell (rk+cf+q+ts+type). These are in Exception messages - HFilePrettyPrinter - Avoiding ensureKeyValue() calls and calls to cell#getxxx() which involves bytes copying. This is not a hot area still we can avoid as much usage of deprecated methods as possible in core code. I believe these bytes copying methods are used in many other parts and later we can try fixing those as per area importance - Creating CellUtil#createKeyOnlyCell and using that in KeyOnlyFilter -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12114) Meta table cache hashing may access the wrong table
[ https://issues.apache.org/jira/browse/HBASE-12114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153265#comment-14153265 ] He Liangliang commented on HBASE-12114: --- I will have a look and add a test case for this when back from vacation. Meta table cache hashing may access the wrong table --- Key: HBASE-12114 URL: https://issues.apache.org/jira/browse/HBASE-12114 Project: HBase Issue Type: Bug Components: Client Reporter: He Liangliang Assignee: He Liangliang Fix For: 0.94.24 Attachments: HBASE-12114.patch The cache key used a hash code from a weak hash algorithm Bytes.mapKey(tableName), which can cause collisions in a quite high probability then make the client accessing a wrong region from another table. Example: 2fx0 and 2fvn -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12096) In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation
[ https://issues.apache.org/jira/browse/HBASE-12096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12096: -- Resolution: Fixed Fix Version/s: 0.99.1 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-1+ We need to go back and do a test cleanup. Too many failing for too long now. In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation - Key: HBASE-12096 URL: https://issues.apache.org/jira/browse/HBASE-12096 Project: HBase Issue Type: Sub-task Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12096.patch, HBASE-12096.patch In ZKSplitLog Coordination classes and AggregateImplementation replace enhanced for statements with basic for statement to avoid unnecessary object allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[ https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manukranth Kolloju updated HBASE-12115: --- Attachment: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Fixing the TestCheckTestClasses by adding the category annotations to my test case. Fix NumberFormat Exception in TableInputFormatBase. --- Key: HBASE-12115 URL: https://issues.apache.org/jira/browse/HBASE-12115 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Minor Fix For: 1.0.0 Attachments: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Original Estimate: 24h Remaining Estimate: 24h DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12038) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents.
[ https://issues.apache.org/jira/browse/HBASE-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12038: --- Attachment: (was: HBASE-12038.patch) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents. Key: HBASE-12038 URL: https://issues.apache.org/jira/browse/HBASE-12038 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.1 Reporter: Solomon Duskis Assignee: Solomon Duskis Signatures with byte[] and String table name variables were deprecated in favor of a TableName input. Replace all byte[] and String table name variables with TableName types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12038) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents.
[ https://issues.apache.org/jira/browse/HBASE-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12038: --- Attachment: HBASE-12038.patch Removed lots of cases of HTable(... byte[] tableName ... ) and replaced them with TableName variants. Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents. Key: HBASE-12038 URL: https://issues.apache.org/jira/browse/HBASE-12038 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.1 Reporter: Solomon Duskis Assignee: Solomon Duskis Attachments: HBASE-12038.patch Signatures with byte[] and String table name variables were deprecated in favor of a TableName input. Replace all byte[] and String table name variables with TableName types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12038) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents.
[ https://issues.apache.org/jira/browse/HBASE-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12038: --- Status: Patch Available (was: In Progress) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents. Key: HBASE-12038 URL: https://issues.apache.org/jira/browse/HBASE-12038 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.1 Reporter: Solomon Duskis Assignee: Solomon Duskis Attachments: HBASE-12038.patch Signatures with byte[] and String table name variables were deprecated in favor of a TableName input. Replace all byte[] and String table name variables with TableName types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12117) Constructors that use Configuration may be harmful
[ https://issues.apache.org/jira/browse/HBASE-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153312#comment-14153312 ] Andrew Purtell commented on HBASE-12117: Yeah I don't think HTable is as lightweight as we want because if an app manages its own HConnection and creates an HTable for each interaction - as we recommend - then it can pay this unexpected cost as much as ~20% of CPU time. This is one example where using Configuration to set up an object is expensive. Found this when looking at something else. Yes I think we could cache configuration in Connection. We are using it like a factory for HTable. Object factories would one way to address this (anti?)pattern wherever it's costly. Related, we should also create by reflection once and cache the desired RpcController object, and clone it for new HTables for the Connection. Constructors that use Configuration may be harmful -- Key: HBASE-12117 URL: https://issues.apache.org/jira/browse/HBASE-12117 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Attachments: traces.client.c.svg, traces.client.getHTable.svg There's a common pattern in HBase code where in the constructor, or in an initialization method also called once per instantiation, or both, we look up values from Hadoop Configuration and store them into fields. This can be expensive if the object is frequently created. Configuration is a heavyweight registry that does a lot of string operations and regex matching. See attached example. Method calls into Configuration account for 48.25% of CPU time when creating the HTable object in 0.98. (The remainder is spent instantiating the RPC controller via reflection, a separate issue that merits followup elsewhere.) Creation of HTable instances is expected to be a lightweight operation if a client is using unmanaged HConnections; however creating HTable instances takes up about 18% of the client's total on-CPU time. This is just one example where constructors that use Configuration may be harmful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12038) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents.
[ https://issues.apache.org/jira/browse/HBASE-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12038: --- Attachment: (was: HBASE-12038.patch) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents. Key: HBASE-12038 URL: https://issues.apache.org/jira/browse/HBASE-12038 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.1 Reporter: Solomon Duskis Assignee: Solomon Duskis Attachments: HBASE-12038.patch Signatures with byte[] and String table name variables were deprecated in favor of a TableName input. Replace all byte[] and String table name variables with TableName types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12038) Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents.
[ https://issues.apache.org/jira/browse/HBASE-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12038: --- Attachment: HBASE-12038.patch Replace internal uses of signatures with byte[] and String tableNames to use the TableName equivalents. Key: HBASE-12038 URL: https://issues.apache.org/jira/browse/HBASE-12038 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.1 Reporter: Solomon Duskis Assignee: Solomon Duskis Attachments: HBASE-12038.patch Signatures with byte[] and String table name variables were deprecated in favor of a TableName input. Replace all byte[] and String table name variables with TableName types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1415#comment-1415
]
Jimmy Xiang commented on HBASE-12099:
-
+1 on changing the element name too. [~esteban], patch v0 works with both
jackson version 1.9.13 and 1.8.8, right?
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153340#comment-14153340
]
Esteban Gutierrez commented on HBASE-12099:
---
Yes, works with both.
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12083) Deprecate new HBaseAdmin() in favor of Connection.getAdmin()
[ https://issues.apache.org/jira/browse/HBASE-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153342#comment-14153342 ] Solomon Duskis commented on HBASE-12083: [~jmspaggi]: Can you please create a new JIRA issue for that? I'll work on it. Deprecate new HBaseAdmin() in favor of Connection.getAdmin() Key: HBASE-12083 URL: https://issues.apache.org/jira/browse/HBASE-12083 Project: HBase Issue Type: Bug Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Critical Fix For: 2.0.0, 0.99.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12075) Preemptive Fast Fail
[ https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-12075: -- Status: Open (was: Patch Available) Preemptive Fast Fail Key: HBASE-12075 URL: https://issues.apache.org/jira/browse/HBASE-12075 Project: HBase Issue Type: Sub-task Components: Client Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Fix For: 1.0.0 Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch, 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch In multi threaded clients, we use a feature developed on 0.89-fb branch called Preemptive Fast Fail. This allows the client threads which would potentially fail, fail fast. The idea behind this feature is that we allow, among the hundreds of client threads, one thread to try and establish connection with the regionserver and if that succeeds, we mark it as a live node again. Meanwhile, other threads which are trying to establish connection to the same server would ideally go into the timeouts which is effectively unfruitful. We can in those cases return appropriate exceptions to those clients instead of letting them retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12075) Preemptive Fast Fail
[ https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-12075: -- Fix Version/s: (was: 1.0.0) Affects Version/s: (was: 1.0.0) 0.99.0 0.98.6.1 2.00 Status: Patch Available (was: Open) Preemptive Fast Fail Key: HBASE-12075 URL: https://issues.apache.org/jira/browse/HBASE-12075 Project: HBase Issue Type: Sub-task Components: Client Affects Versions: 2.00, 0.98.6.1, 0.99.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch, 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch, 0001-Implement-Preemptive-Fast-Fail.patch In multi threaded clients, we use a feature developed on 0.89-fb branch called Preemptive Fast Fail. This allows the client threads which would potentially fail, fail fast. The idea behind this feature is that we allow, among the hundreds of client threads, one thread to try and establish connection with the regionserver and if that succeeds, we mark it as a live node again. Meanwhile, other threads which are trying to establish connection to the same server would ideally go into the timeouts which is effectively unfruitful. We can in those cases return appropriate exceptions to those clients instead of letting them retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12040) Performances issues with FilteredScanTest
[ https://issues.apache.org/jira/browse/HBASE-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153366#comment-14153366 ] Nick Dimiduk commented on HBASE-12040: -- I cannot remember if I restarted the RS between loading the data and running the first test on 0.98.6.1, which means the first run may have a significantly warmer JIT than the subsequent runs. Please disregard my previous comment; I'll try to find time to run a more correct script today. Performances issues with FilteredScanTest -- Key: HBASE-12040 URL: https://issues.apache.org/jira/browse/HBASE-12040 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: Jean-Marc Spaggiari Priority: Critical Attachments: at-HBASE-11331.html, pre-HBASE-11331.html, ycsb-0.98.6.1-vs-0.98.7.pdf While testing 0.99.0RC1 release performances, compared to 0.98.6, figured that: - FilteredScanTest is 100 times slower; - RandomReadTest is 1.5 times slower; - RandomSeekScanTest is 3.2 times slower; - RandomScanWithRange10Test is 1,2 times slower; - RandomScanWithRange100Test is 1,3 times slower; - RandomScanWithRange1000Test is 4 times slower; - SequentialReadTest is 1,7 times slower; - SequentialWriteTest is just a bit faster; - RandomWriteTest is just a bit faster; - GaussianRandomReadBenchmark is just a beat slower; - SequentialReadBenchmark is 1,1 times slower; - SequentialWriteBenchmark is 1,1 times slower; - UniformRandomReadBenchmark crashed; - UniformRandomSmallScan is 1,3 times slower. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12119) Master regionserver web UI NOT_FOUND
Jimmy Xiang created HBASE-12119: --- Summary: Master regionserver web UI NOT_FOUND Key: HBASE-12119 URL: https://issues.apache.org/jira/browse/HBASE-12119 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Although the active master is configured to host regions, I got Error 404 NOT_FOUND. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12040) Performances issues with FilteredScanTest
[ https://issues.apache.org/jira/browse/HBASE-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153402#comment-14153402 ] Andrew Purtell commented on HBASE-12040: Let me add that I did a comparison yesterday between 3645223 [4 weeks ago] (tag: 0.98.6RC2, tag: 0.98.6) Update CHANGES.txt for 0.98 and c220be9 [3 days ago] (HEAD, 0.98) HBASE-12110 Fix .arcconfig [Elliott Clark] and I didn't see a significant difference. However I have been using the local filesystem not HDFS, and Hadoop 2.2 not Hadoop 2.4, so I will try again today with a setup closer to Nick's above. *If* I can get repeatable results that show a significant difference I'll be able to bisect to an implicated commit. Performances issues with FilteredScanTest -- Key: HBASE-12040 URL: https://issues.apache.org/jira/browse/HBASE-12040 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: Jean-Marc Spaggiari Priority: Critical Attachments: at-HBASE-11331.html, pre-HBASE-11331.html, ycsb-0.98.6.1-vs-0.98.7.pdf While testing 0.99.0RC1 release performances, compared to 0.98.6, figured that: - FilteredScanTest is 100 times slower; - RandomReadTest is 1.5 times slower; - RandomSeekScanTest is 3.2 times slower; - RandomScanWithRange10Test is 1,2 times slower; - RandomScanWithRange100Test is 1,3 times slower; - RandomScanWithRange1000Test is 4 times slower; - SequentialReadTest is 1,7 times slower; - SequentialWriteTest is just a bit faster; - RandomWriteTest is just a bit faster; - GaussianRandomReadBenchmark is just a beat slower; - SequentialReadBenchmark is 1,1 times slower; - SequentialWriteBenchmark is 1,1 times slower; - UniformRandomReadBenchmark crashed; - UniformRandomSmallScan is 1,3 times slower. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10200) Better error message when HttpServer fails to start due to java.net.BindException
[
https://issues.apache.org/jira/browse/HBASE-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153410#comment-14153410
]
Jeffrey Zhong commented on HBASE-10200:
---
looks good to me(+1) with one minor suggestion: could we use the same error
message in LOG.error and IOException?
{code}
+ LOG.error(Address
+ + addr
+ + does not belong to this host. Correct configuration parameter:
hbase.regionserver.info.bindAddress);
+ throw new IOException(Failed to start http info server. + Address
+ addr
+ + does not belong to this host.);
{code}
Better error message when HttpServer fails to start due to
java.net.BindException
-
Key: HBASE-10200
URL: https://issues.apache.org/jira/browse/HBASE-10200
Project: HBase
Issue Type: Task
Affects Versions: 2.0.0
Reporter: Ted Yu
Priority: Minor
Labels: beginner
Attachments: 10200.out, HBASE-10020.patch, HBASE-10020.patch
Starting HBase using Hoya, I saw the following in log:
{code}
2013-12-17 21:49:06,758 INFO [master:hor12n19:42587] http.HttpServer:
HttpServer.start() threw a non Bind IOException
java.net.BindException: Port in use: hor12n14.gq1.ygridcore.net:12432
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:742)
at org.apache.hadoop.http.HttpServer.start(HttpServer.java:686)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:586)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:344)
at sun.nio.ch.Net.bind(Net.java:336)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:738)
{code}
This was due to hbase.master.info.bindAddress giving static address but Hoya
allocates master dynamically.
Better error message should be provided: when bindAddress points another host
than local host, message should remind user to remove / adjust
hbase.master.info.bindAddress config param from hbase-site.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-10200) Better error message when HttpServer fails to start due to java.net.BindException
[
https://issues.apache.org/jira/browse/HBASE-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reassigned HBASE-10200:
--
Assignee: Kiran Kumar M R
Better error message when HttpServer fails to start due to
java.net.BindException
-
Key: HBASE-10200
URL: https://issues.apache.org/jira/browse/HBASE-10200
Project: HBase
Issue Type: Task
Affects Versions: 2.0.0
Reporter: Ted Yu
Assignee: Kiran Kumar M R
Priority: Minor
Labels: beginner
Attachments: 10200.out, HBASE-10020.patch, HBASE-10020.patch
Starting HBase using Hoya, I saw the following in log:
{code}
2013-12-17 21:49:06,758 INFO [master:hor12n19:42587] http.HttpServer:
HttpServer.start() threw a non Bind IOException
java.net.BindException: Port in use: hor12n14.gq1.ygridcore.net:12432
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:742)
at org.apache.hadoop.http.HttpServer.start(HttpServer.java:686)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:586)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:344)
at sun.nio.ch.Net.bind(Net.java:336)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:738)
{code}
This was due to hbase.master.info.bindAddress giving static address but Hoya
allocates master dynamically.
Better error message should be provided: when bindAddress points another host
than local host, message should remind user to remove / adjust
hbase.master.info.bindAddress config param from hbase-site.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-10200) Better error message when HttpServer fails to start due to java.net.BindException
[
https://issues.apache.org/jira/browse/HBASE-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-10200:
---
Fix Version/s: 0.99.1
2.0.0
Hadoop Flags: Reviewed
Better error message when HttpServer fails to start due to
java.net.BindException
-
Key: HBASE-10200
URL: https://issues.apache.org/jira/browse/HBASE-10200
Project: HBase
Issue Type: Task
Affects Versions: 2.0.0
Reporter: Ted Yu
Assignee: Kiran Kumar M R
Priority: Minor
Labels: beginner
Fix For: 2.0.0, 0.99.1
Attachments: 10200.out, HBASE-10020.patch, HBASE-10020.patch
Starting HBase using Hoya, I saw the following in log:
{code}
2013-12-17 21:49:06,758 INFO [master:hor12n19:42587] http.HttpServer:
HttpServer.start() threw a non Bind IOException
java.net.BindException: Port in use: hor12n14.gq1.ygridcore.net:12432
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:742)
at org.apache.hadoop.http.HttpServer.start(HttpServer.java:686)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:586)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:344)
at sun.nio.ch.Net.bind(Net.java:336)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:738)
{code}
This was due to hbase.master.info.bindAddress giving static address but Hoya
allocates master dynamically.
Better error message should be provided: when bindAddress points another host
than local host, message should remind user to remove / adjust
hbase.master.info.bindAddress config param from hbase-site.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12119) Master regionserver web UI NOT_FOUND
[ https://issues.apache.org/jira/browse/HBASE-12119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-12119: Fix Version/s: 0.99.1 2.0.0 Master regionserver web UI NOT_FOUND Key: HBASE-12119 URL: https://issues.apache.org/jira/browse/HBASE-12119 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: hbase-12119.patch Although the active master is configured to host regions, I got Error 404 NOT_FOUND. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12119) Master regionserver web UI NOT_FOUND
[ https://issues.apache.org/jira/browse/HBASE-12119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-12119: Status: Patch Available (was: Open) Master regionserver web UI NOT_FOUND Key: HBASE-12119 URL: https://issues.apache.org/jira/browse/HBASE-12119 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: hbase-12119.patch Although the active master is configured to host regions, I got Error 404 NOT_FOUND. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12119) Master regionserver web UI NOT_FOUND
[ https://issues.apache.org/jira/browse/HBASE-12119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-12119: Priority: Minor (was: Major) Master regionserver web UI NOT_FOUND Key: HBASE-12119 URL: https://issues.apache.org/jira/browse/HBASE-12119 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: hbase-12119.patch Although the active master is configured to host regions, I got Error 404 NOT_FOUND. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12119) Master regionserver web UI NOT_FOUND
[ https://issues.apache.org/jira/browse/HBASE-12119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-12119: Attachment: hbase-12119.patch The problem is a member in master is not initialized when regionserver puts up the web UI. Attached a patch. Master regionserver web UI NOT_FOUND Key: HBASE-12119 URL: https://issues.apache.org/jira/browse/HBASE-12119 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Fix For: 2.0.0, 0.99.1 Attachments: hbase-12119.patch Although the active master is configured to host regions, I got Error 404 NOT_FOUND. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12118) Explain how to grant permission to a namespace in grant command usage
[ https://issues.apache.org/jira/browse/HBASE-12118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153434#comment-14153434 ] Hudson commented on HBASE-12118: FAILURE: Integrated in HBase-0.98 #549 (See [https://builds.apache.org/job/HBase-0.98/549/]) HBASE-12118 Explain how to grant permission to a namespace in grant command usage (stack: rev 2968d385e65b6ae4737258bdd4fcfbb0d2bb6cdd) * hbase-shell/src/main/ruby/shell/commands/grant.rb Explain how to grant permission to a namespace in grant command usage - Key: HBASE-12118 URL: https://issues.apache.org/jira/browse/HBASE-12118 Project: HBase Issue Type: Improvement Components: documentation, shell Affects Versions: 0.98.6.1 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12118-1.patch, HBASE-12118.patch In the grant command usage, How to grant permission to a namespace is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12120) HBase shell doesn't allow deleting of a cell by user with W-only permissions to it
Dima Spivak created HBASE-12120: --- Summary: HBase shell doesn't allow deleting of a cell by user with W-only permissions to it Key: HBASE-12120 URL: https://issues.apache.org/jira/browse/HBASE-12120 Project: HBase Issue Type: Bug Components: shell Reporter: Dima Spivak If cell-level ACLs are used to give a user W permissions to a cell, they should be able to delete that cell. In testing the Java API, I've confirmed that this is respected. Using the HBase shell, however, a user trying to delete a cell to which they don't have read permissions results in a Row Not Found error. [~mbertozzi] tracked this down to a change introduced by HBASE-5837 wherein an attempt is made to get the cell before deleting it to confirm that it exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12121) maven release plugin does not allow for customized goals
Enoch Hsu created HBASE-12121:
-
Summary: maven release plugin does not allow for customized goals
Key: HBASE-12121
URL: https://issues.apache.org/jira/browse/HBASE-12121
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.6
Reporter: Enoch Hsu
Assignee: Enoch Hsu
Priority: Minor
Inside the pom under the maven-release-plugin there is a configuration that
defines what the release-plugin uses like so
configuration
!--You need this profile. It'll sign your artifacts.
I'm not sure if this config. actually works though.
I've been specifying -Papache-release on the command-line
--
releaseProfilesapache-release/releaseProfiles
!--This stops our running tests for each stage of maven release.
But it builds the test jar. From SUREFIRE-172.
--
arguments-Dmaven.test.skip.exec/arguments
pomFileNamepom.xml/pomFileName
/configuration
There is no property for goals so if the user passes in a goal from the command
line it will not get executed and the default behavior will be used instead.
I propose to add in the following
goals${goals}/goals
This will allow custom release goal options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12122) Try not to assign user regions to master all the time
Jimmy Xiang created HBASE-12122: --- Summary: Try not to assign user regions to master all the time Key: HBASE-12122 URL: https://issues.apache.org/jira/browse/HBASE-12122 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.99.1 Load balancer does a good job not to assign regions of tables not configured to put on the active master. However, if there is no other region server, it still assigns users regions to the master. This happens when all normal region servers are crashed and recovering. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12121) maven release plugin does not allow for customized goals
[
https://issues.apache.org/jira/browse/HBASE-12121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enoch Hsu updated HBASE-12121:
--
Attachment: HBASE-12121.patch
maven release plugin does not allow for customized goals
Key: HBASE-12121
URL: https://issues.apache.org/jira/browse/HBASE-12121
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.6
Reporter: Enoch Hsu
Assignee: Enoch Hsu
Priority: Minor
Attachments: HBASE-12121.patch
Inside the pom under the maven-release-plugin there is a configuration that
defines what the release-plugin uses like so
configuration
!--You need this profile. It'll sign your artifacts.
I'm not sure if this config. actually works though.
I've been specifying -Papache-release on the command-line
--
releaseProfilesapache-release/releaseProfiles
!--This stops our running tests for each stage of maven release.
But it builds the test jar. From SUREFIRE-172.
--
arguments-Dmaven.test.skip.exec/arguments
pomFileNamepom.xml/pomFileName
/configuration
There is no property for goals so if the user passes in a goal from the
command line it will not get executed and the default behavior will be used
instead.
I propose to add in the following
goals${goals}/goals
This will allow custom release goal options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12121) maven release plugin does not allow for customized goals
[
https://issues.apache.org/jira/browse/HBASE-12121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enoch Hsu updated HBASE-12121:
--
Status: Patch Available (was: Open)
maven release plugin does not allow for customized goals
Key: HBASE-12121
URL: https://issues.apache.org/jira/browse/HBASE-12121
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.6
Reporter: Enoch Hsu
Assignee: Enoch Hsu
Priority: Minor
Attachments: HBASE-12121.patch
Inside the pom under the maven-release-plugin there is a configuration that
defines what the release-plugin uses like so
configuration
!--You need this profile. It'll sign your artifacts.
I'm not sure if this config. actually works though.
I've been specifying -Papache-release on the command-line
--
releaseProfilesapache-release/releaseProfiles
!--This stops our running tests for each stage of maven release.
But it builds the test jar. From SUREFIRE-172.
--
arguments-Dmaven.test.skip.exec/arguments
pomFileNamepom.xml/pomFileName
/configuration
There is no property for goals so if the user passes in a goal from the
command line it will not get executed and the default behavior will be used
instead.
I propose to add in the following
goals${goals}/goals
This will allow custom release goal options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12121) maven release plugin does not allow for customized goals
[
https://issues.apache.org/jira/browse/HBASE-12121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enoch Hsu updated HBASE-12121:
--
Issue Type: Improvement (was: Bug)
maven release plugin does not allow for customized goals
Key: HBASE-12121
URL: https://issues.apache.org/jira/browse/HBASE-12121
Project: HBase
Issue Type: Improvement
Affects Versions: 0.98.6
Reporter: Enoch Hsu
Assignee: Enoch Hsu
Priority: Minor
Attachments: HBASE-12121.patch
Inside the pom under the maven-release-plugin there is a configuration that
defines what the release-plugin uses like so
configuration
!--You need this profile. It'll sign your artifacts.
I'm not sure if this config. actually works though.
I've been specifying -Papache-release on the command-line
--
releaseProfilesapache-release/releaseProfiles
!--This stops our running tests for each stage of maven release.
But it builds the test jar. From SUREFIRE-172.
--
arguments-Dmaven.test.skip.exec/arguments
pomFileNamepom.xml/pomFileName
/configuration
There is no property for goals so if the user passes in a goal from the
command line it will not get executed and the default behavior will be used
instead.
I propose to add in the following
goals${goals}/goals
This will allow custom release goal options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153466#comment-14153466
]
Devaraj Das commented on HBASE-12099:
-
+1 on making it labels if backward compatibility is not a concern.. (which I
hope it is not since the tags feature is new and experimental).
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12040) Performances issues with FilteredScanTest
[ https://issues.apache.org/jira/browse/HBASE-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153469#comment-14153469 ] Andrew Purtell commented on HBASE-12040: Separate processes for NN, DN, ZK, HMaster, RS, HDFS 2.4.0, SCR enabled, 1 SSD. RS running with 4 GB heap and LruBlockCache. Setup: ./bin/hbase pe --nomapred --compress=SNAPPY --presplit=10 sequentialWrite 1 (--size not available in 0.98 PE) Run: Stop and start the RS. Then: sync; echo 3 | sudo tee /proc/sys/vm/drop_caches ; ./bin/hbase pe --nomapred scanRange100 1 c220be9 [3 days ago] (HEAD, 0.98) HBASE-12110 Fix .arcconfig [Elliott Clark] hbase.PerformanceEvaluation: Finished TestClient-0 in 1296699ms over 1048576 rows 3645223 [4 weeks ago] (tag: 0.98.6RC2, tag: 0.98.6) Update CHANGES.txt for 0.98. hbase.PerformanceEvaluation: Finished TestClient-0 in 1316509ms over 1048576 row Not enough data? Let me create a table with 10x the number of rows. Performances issues with FilteredScanTest -- Key: HBASE-12040 URL: https://issues.apache.org/jira/browse/HBASE-12040 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: Jean-Marc Spaggiari Priority: Critical Attachments: at-HBASE-11331.html, pre-HBASE-11331.html, ycsb-0.98.6.1-vs-0.98.7.pdf While testing 0.99.0RC1 release performances, compared to 0.98.6, figured that: - FilteredScanTest is 100 times slower; - RandomReadTest is 1.5 times slower; - RandomSeekScanTest is 3.2 times slower; - RandomScanWithRange10Test is 1,2 times slower; - RandomScanWithRange100Test is 1,3 times slower; - RandomScanWithRange1000Test is 4 times slower; - SequentialReadTest is 1,7 times slower; - SequentialWriteTest is just a bit faster; - RandomWriteTest is just a bit faster; - GaussianRandomReadBenchmark is just a beat slower; - SequentialReadBenchmark is 1,1 times slower; - SequentialWriteBenchmark is 1,1 times slower; - UniformRandomReadBenchmark crashed; - UniformRandomSmallScan is 1,3 times slower. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-12040) Performances issues with FilteredScanTest
[
https://issues.apache.org/jira/browse/HBASE-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153469#comment-14153469
]
Andrew Purtell edited comment on HBASE-12040 at 9/30/14 6:03 PM:
-
Separate processes for NN, DN, ZK, HMaster, RS, HDFS 2.4.0, SCR enabled, 1 SSD.
RS running with 4 GB heap and LruBlockCache.
Setup: {{./bin/hbase pe -nomapred -compress=SNAPPY -presplit=10 sequentialWrite
1}} (-size not available in 0.98 PE)
Run: Stop and start the RS. Then: {{sync; echo 3 | sudo tee
/proc/sys/vm/drop_caches ; ./bin/hbase pe -nomapred scanRange100 1}}
{noformat}
c220be9 [3 days ago] (HEAD, 0.98) HBASE-12110 Fix .arcconfig [Elliott Clark]
hbase.PerformanceEvaluation: Finished TestClient-0 in 1296699ms over
1048576 rows
3645223 [4 weeks ago] (tag: 0.98.6RC2, tag: 0.98.6) Update CHANGES.txt for 0.98.
hbase.PerformanceEvaluation: Finished TestClient-0 in 1316509ms over
1048576 row
{noformat}
Not enough data?
Let me create a table with 10x the number of rows.
Edit: Fix formatting
was (Author: apurtell):
Separate processes for NN, DN, ZK, HMaster, RS, HDFS 2.4.0, SCR enabled, 1 SSD.
RS running with 4 GB heap and LruBlockCache.
Setup: ./bin/hbase pe --nomapred --compress=SNAPPY --presplit=10
sequentialWrite 1 (--size not available in 0.98 PE)
Run: Stop and start the RS. Then: sync; echo 3 | sudo tee
/proc/sys/vm/drop_caches ; ./bin/hbase pe --nomapred scanRange100 1
c220be9 [3 days ago] (HEAD, 0.98) HBASE-12110 Fix .arcconfig [Elliott Clark]
hbase.PerformanceEvaluation: Finished TestClient-0 in 1296699ms over
1048576 rows
3645223 [4 weeks ago] (tag: 0.98.6RC2, tag: 0.98.6) Update CHANGES.txt for 0.98.
hbase.PerformanceEvaluation: Finished TestClient-0 in 1316509ms over
1048576 row
Not enough data?
Let me create a table with 10x the number of rows.
Performances issues with FilteredScanTest
--
Key: HBASE-12040
URL: https://issues.apache.org/jira/browse/HBASE-12040
Project: HBase
Issue Type: Bug
Affects Versions: 0.99.1
Reporter: Jean-Marc Spaggiari
Priority: Critical
Attachments: at-HBASE-11331.html, pre-HBASE-11331.html,
ycsb-0.98.6.1-vs-0.98.7.pdf
While testing 0.99.0RC1 release performances, compared to 0.98.6, figured
that:
- FilteredScanTest is 100 times slower;
- RandomReadTest is 1.5 times slower;
- RandomSeekScanTest is 3.2 times slower;
- RandomScanWithRange10Test is 1,2 times slower;
- RandomScanWithRange100Test is 1,3 times slower;
- RandomScanWithRange1000Test is 4 times slower;
- SequentialReadTest is 1,7 times slower;
- SequentialWriteTest is just a bit faster;
- RandomWriteTest is just a bit faster;
- GaussianRandomReadBenchmark is just a beat slower;
- SequentialReadBenchmark is 1,1 times slower;
- SequentialWriteBenchmark is 1,1 times slower;
- UniformRandomReadBenchmark crashed;
- UniformRandomSmallScan is 1,3 times slower.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12118) Explain how to grant permission to a namespace in grant command usage
[ https://issues.apache.org/jira/browse/HBASE-12118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153475#comment-14153475 ] Hudson commented on HBASE-12118: FAILURE: Integrated in HBase-1.0 #248 (See [https://builds.apache.org/job/HBase-1.0/248/]) HBASE-12118 Explain how to grant permission to a namespace in grant command usage (stack: rev 2ce0884aca9ae0061b7eb6642e70882f79bb4f70) * hbase-shell/src/main/ruby/shell/commands/grant.rb Explain how to grant permission to a namespace in grant command usage - Key: HBASE-12118 URL: https://issues.apache.org/jira/browse/HBASE-12118 Project: HBase Issue Type: Improvement Components: documentation, shell Affects Versions: 0.98.6.1 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12118-1.patch, HBASE-12118.patch In the grant command usage, How to grant permission to a namespace is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12096) In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation
[ https://issues.apache.org/jira/browse/HBASE-12096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153476#comment-14153476 ] Hudson commented on HBASE-12096: FAILURE: Integrated in HBase-1.0 #248 (See [https://builds.apache.org/job/HBase-1.0/248/]) HBASE-12096 In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation (stack: rev f719b57f7668a436ffe3df826cb2187df248e552) * hbase-server/src/main/java/org/apache/hadoop/hbase/coordination/ZKSplitLogManagerCoordination.java * hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/AggregateImplementation.java * hbase-server/src/main/java/org/apache/hadoop/hbase/coordination/ZkSplitLogWorkerCoordination.java In ZKSplitLog Coordination and AggregateImplementation replace enhaced for statements with basic for statement to avoid unnecessary object allocation - Key: HBASE-12096 URL: https://issues.apache.org/jira/browse/HBASE-12096 Project: HBase Issue Type: Sub-task Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12096.patch, HBASE-12096.patch In ZKSplitLog Coordination classes and AggregateImplementation replace enhanced for statements with basic for statement to avoid unnecessary object allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11879) Change TableInputFormatBase to take interface arguments
[
https://issues.apache.org/jira/browse/HBASE-11879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Solomon Duskis updated HBASE-11879:
---
Attachment: HBASE-11879_v2.patch
Update due to merging with master.
Change TableInputFormatBase to take interface arguments
---
Key: HBASE-11879
URL: https://issues.apache.org/jira/browse/HBASE-11879
Project: HBase
Issue Type: Improvement
Reporter: Carter
Assignee: Solomon Duskis
Fix For: 2.0.0, 0.99.1
Attachments: HBASE-11879_v2.patch, HBASE_11879.patch,
HBASE_11879_v1.patch
As part of the ongoing interface abstraction work, I'm now investigating
{{TableInputFormatBase}}, which has two methods that break encapsulation:
{code}
protected HTable getHTable();
protected void setHTable(HTable table);
{code}
While these are protected methods, the base @InterfaceAudience.Public is
abstract, meaning that it supports extension by user code.
I propose deprecating these two methods and replacing them with these four,
once the Table interface is merged:
{code}
protected Table getTable();
protected void setTable(Table table);
protected RegionLocator getRegionLocator();
protected void setRegionLocator(RegionLocator regionLocator);
{code}
Since users will frequently call {{setTable}} and {{setRegionLocator}}
together, it probably also makes sense to add the following convenience
method:
{code}
protected void setTableAndRegionLocator(Table table, RegionLocator
regionLocator);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11879) Change TableInputFormatBase to take interface arguments
[
https://issues.apache.org/jira/browse/HBASE-11879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Solomon Duskis updated HBASE-11879:
---
Fix Version/s: 2.0.0
Status: Patch Available (was: Open)
Change TableInputFormatBase to take interface arguments
---
Key: HBASE-11879
URL: https://issues.apache.org/jira/browse/HBASE-11879
Project: HBase
Issue Type: Improvement
Reporter: Carter
Assignee: Solomon Duskis
Fix For: 2.0.0, 0.99.1
Attachments: HBASE-11879_v2.patch, HBASE_11879.patch,
HBASE_11879_v1.patch
As part of the ongoing interface abstraction work, I'm now investigating
{{TableInputFormatBase}}, which has two methods that break encapsulation:
{code}
protected HTable getHTable();
protected void setHTable(HTable table);
{code}
While these are protected methods, the base @InterfaceAudience.Public is
abstract, meaning that it supports extension by user code.
I propose deprecating these two methods and replacing them with these four,
once the Table interface is merged:
{code}
protected Table getTable();
protected void setTable(Table table);
protected RegionLocator getRegionLocator();
protected void setRegionLocator(RegionLocator regionLocator);
{code}
Since users will frequently call {{setTable}} and {{setRegionLocator}}
together, it probably also makes sense to add the following convenience
method:
{code}
protected void setTableAndRegionLocator(Table table, RegionLocator
regionLocator);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-12099:
--
Fix Version/s: 0.99.1
0.98.7
2.0.0
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153498#comment-14153498
]
Enis Soztutar commented on HBASE-12099:
---
[~andrew.purt...@gmail.com] you are ok for this change (v0 patch) for 0.98? It
breaks compat for rest XML, but most of the folks think it is ok.
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11853) Provide an alternative to the apache build for developers (like me) who aren't committers
[ https://issues.apache.org/jira/browse/HBASE-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman updated HBASE-11853: Attachment: HBASE-11853-v5.patch Rebased off of todays master. rerunning tests at https://circleci.com/gh/OhmData/hbase-public/333 Provide an alternative to the apache build for developers (like me) who aren't committers - Key: HBASE-11853 URL: https://issues.apache.org/jira/browse/HBASE-11853 Project: HBase Issue Type: Sub-task Reporter: Alex Newman Assignee: Alex Newman Attachments: HBASE-11853-testing-v0.patch, HBASE-11853-testing-v1.patch, HBASE-11853-v0.patch, HBASE-11853-v3.patch, HBASE-11853-v4.patch, HBASE-11853-v5.patch Travis CI and Circle-CI now provide free builds for open source projects. I created the capability to run builds this way. Although they are closed source (and thus not a replacement for jenkins IMHO), they are super convenient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153502#comment-14153502
]
Andrew Purtell commented on HBASE-12099:
+1
Agreed, tags are communicated as an experimental feature in 0.98
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11178) Remove deprecation annotations from mapred namespace
[ https://issues.apache.org/jira/browse/HBASE-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153508#comment-14153508 ] Nick Dimiduk commented on HBASE-11178: -- BuildBot is out to lunch on this one. Builds clean for me on branch-1 and master. Remove deprecation annotations from mapred namespace Key: HBASE-11178 URL: https://issues.apache.org/jira/browse/HBASE-11178 Project: HBase Issue Type: Sub-task Components: mapreduce Reporter: Nick Dimiduk Assignee: Nick Dimiduk Fix For: 2.0.0, 0.99.1 Attachments: HBASE-11178.00.patch, HBASE-11178.00.patch I guess mapred API is here to stay. We should remove these annotations and clean it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12098) User granted namespace table create permissions can't create a table
[
https://issues.apache.org/jira/browse/HBASE-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-12098:
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to 0.98, branch-1, master.
thanks Srikanth
User granted namespace table create permissions can't create a table
Key: HBASE-12098
URL: https://issues.apache.org/jira/browse/HBASE-12098
Project: HBase
Issue Type: Bug
Components: Client, security
Affects Versions: 0.98.6
Reporter: Dima Spivak
Assignee: Srikanth Srungarapu
Priority: Critical
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12098-master.txt, HBASE-12098.patch,
HBASE-12098_master_v2.patch
From the HBase shell and Java API, I am seeing
{code}ERROR: org.apache.hadoop.hbase.security.AccessDeniedException:
Insufficient permissions for user 'dima' (global, action=CREATE){code}
when I try to create a table in a namespace to which I have been granted
RWXCA permissions by a global admin. Interestingly enough, this only seems to
extend to table creation; the same user is then allowed to disable and drop a
table created by a global admin in that namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12095) SecureWALCellCodec should handle the case where encryption is disabled
[
https://issues.apache.org/jira/browse/HBASE-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153509#comment-14153509
]
Andrew Purtell commented on HBASE-12095:
Patch looks ok, but here can we test if the encryptor/decryptor is null instead
of the IV?
{code}
@Override
protected Cell parseCell() throws IOException {
+ if (this.iv == null) {
+return super.parseCell();
+ }
{code}
SecureWALCellCodec should handle the case where encryption is disabled
--
Key: HBASE-12095
URL: https://issues.apache.org/jira/browse/HBASE-12095
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.6
Reporter: Ashish Singhi
Assignee: Ted Yu
Fix For: 0.98.7
Attachments: 12095-v1.txt, 12095-v1.txt
I observed that when I have the following value set in my hbase-site.xml file
{code}
property
namehbase.regionserver.wal.encryption/name
valuefalse/value
/property
property
namehbase.regionserver.hlog.reader.impl/name
valueorg.apache.hadoop.hbase.regionserver.wal.SecureProtobufLogReader/value
/property
property
namehbase.regionserver.hlog.writer.impl/name
valueorg.apache.hadoop.hbase.regionserver.wal.SecureProtobufLogWriter/value
/property
{code}
And while log splitting on hbase service restart, master shutdown with
following exception.
Exception in master log
{code}
2014-09-24 17:14:28,590 FATAL [master:host-10-18-40-18:6] master.HMaster:
Master server abort: loaded coprocessors are:
[org.apache.hadoop.hbase.security.access.AccessController]
2014-09-24 17:14:28,590 FATAL [master:host-10-18-40-18:6] master.HMaster:
Unhandled exception. Starting shutdown.
java.io.IOException: error or interrupted while splitting logs in
[hdfs://10.18.40.18:8020/tmp/hbase-ashish/hbase/WALs/host-10-18-40-18,60020,1411558717849-splitting]
Task = installed = 6 done = 0 error = 6
at
org.apache.hadoop.hbase.master.SplitLogManager.splitLogDistributed(SplitLogManager.java:378)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitLog(MasterFileSystem.java:415)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:307)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:298)
at
org.apache.hadoop.hbase.master.HMaster.splitMetaLogBeforeAssignment(HMaster.java:1071)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:863)
at
org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:612)
at java.lang.Thread.run(Thread.java:745)
Exception in region server log
2014-09-24 20:10:16,535 WARN [RS_LOG_REPLAY_OPS-host-10-18-40-18:60020-1]
regionserver.SplitLogWorker: log splitting of
WALs/host-10-18-40-18,60020,1411558717849-splitting/host-10-18-40-18%2C60020%2C1411558717849.1411558724316.meta
failed, returning error
java.io.IOException: Cannot get log reader
at
org.apache.hadoop.hbase.regionserver.wal.HLogFactory.createReader(HLogFactory.java:161)
at
org.apache.hadoop.hbase.regionserver.wal.HLogFactory.createReader(HLogFactory.java:89)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.getReader(HLogSplitter.java:660)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.getReader(HLogSplitter.java:569)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.splitLogFile(HLogSplitter.java:282)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.splitLogFile(HLogSplitter.java:225)
at
org.apache.hadoop.hbase.regionserver.SplitLogWorker$1.exec(SplitLogWorker.java:143)
at
org.apache.hadoop.hbase.regionserver.handler.HLogSplitterHandler.process(HLogSplitterHandler.java:82)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.UnsupportedOperationException: Unable to find suitable
constructor for class
org.apache.hadoop.hbase.regionserver.wal.SecureWALCellCodec
at
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:39)
at
org.apache.hadoop.hbase.regionserver.wal.WALCellCodec.create(WALCellCodec.java:101)
at
org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.getCodec(ProtobufLogReader.java:242)
[jira] [Updated] (HBASE-12095) SecureWALCellCodec should handle the case where encryption is disabled
[
https://issues.apache.org/jira/browse/HBASE-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-12095:
---
Fix Version/s: 0.99.1
2.0.0
Hadoop Flags: Reviewed
SecureWALCellCodec should handle the case where encryption is disabled
--
Key: HBASE-12095
URL: https://issues.apache.org/jira/browse/HBASE-12095
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.6
Reporter: Ashish Singhi
Assignee: Ted Yu
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12095-v1.txt, 12095-v1.txt, 12095-v2.txt
I observed that when I have the following value set in my hbase-site.xml file
{code}
property
namehbase.regionserver.wal.encryption/name
valuefalse/value
/property
property
namehbase.regionserver.hlog.reader.impl/name
valueorg.apache.hadoop.hbase.regionserver.wal.SecureProtobufLogReader/value
/property
property
namehbase.regionserver.hlog.writer.impl/name
valueorg.apache.hadoop.hbase.regionserver.wal.SecureProtobufLogWriter/value
/property
{code}
And while log splitting on hbase service restart, master shutdown with
following exception.
Exception in master log
{code}
2014-09-24 17:14:28,590 FATAL [master:host-10-18-40-18:6] master.HMaster:
Master server abort: loaded coprocessors are:
[org.apache.hadoop.hbase.security.access.AccessController]
2014-09-24 17:14:28,590 FATAL [master:host-10-18-40-18:6] master.HMaster:
Unhandled exception. Starting shutdown.
java.io.IOException: error or interrupted while splitting logs in
[hdfs://10.18.40.18:8020/tmp/hbase-ashish/hbase/WALs/host-10-18-40-18,60020,1411558717849-splitting]
Task = installed = 6 done = 0 error = 6
at
org.apache.hadoop.hbase.master.SplitLogManager.splitLogDistributed(SplitLogManager.java:378)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitLog(MasterFileSystem.java:415)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:307)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:298)
at
org.apache.hadoop.hbase.master.HMaster.splitMetaLogBeforeAssignment(HMaster.java:1071)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:863)
at
org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:612)
at java.lang.Thread.run(Thread.java:745)
Exception in region server log
2014-09-24 20:10:16,535 WARN [RS_LOG_REPLAY_OPS-host-10-18-40-18:60020-1]
regionserver.SplitLogWorker: log splitting of
WALs/host-10-18-40-18,60020,1411558717849-splitting/host-10-18-40-18%2C60020%2C1411558717849.1411558724316.meta
failed, returning error
java.io.IOException: Cannot get log reader
at
org.apache.hadoop.hbase.regionserver.wal.HLogFactory.createReader(HLogFactory.java:161)
at
org.apache.hadoop.hbase.regionserver.wal.HLogFactory.createReader(HLogFactory.java:89)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.getReader(HLogSplitter.java:660)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.getReader(HLogSplitter.java:569)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.splitLogFile(HLogSplitter.java:282)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.splitLogFile(HLogSplitter.java:225)
at
org.apache.hadoop.hbase.regionserver.SplitLogWorker$1.exec(SplitLogWorker.java:143)
at
org.apache.hadoop.hbase.regionserver.handler.HLogSplitterHandler.process(HLogSplitterHandler.java:82)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.UnsupportedOperationException: Unable to find suitable
constructor for class
org.apache.hadoop.hbase.regionserver.wal.SecureWALCellCodec
at
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:39)
at
org.apache.hadoop.hbase.regionserver.wal.WALCellCodec.create(WALCellCodec.java:101)
at
org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.getCodec(ProtobufLogReader.java:242)
at
org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.initAfterCompression(ProtobufLogReader.java:247)
at
[jira] [Updated] (HBASE-12095) SecureWALCellCodec should handle the case where encryption is disabled
[
https://issues.apache.org/jira/browse/HBASE-12095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-12095:
---
Attachment: 12095-v2.txt
That works.
Patch v2 does what Andrew suggested.
SecureWALCellCodec should handle the case where encryption is disabled
--
Key: HBASE-12095
URL: https://issues.apache.org/jira/browse/HBASE-12095
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.6
Reporter: Ashish Singhi
Assignee: Ted Yu
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12095-v1.txt, 12095-v1.txt, 12095-v2.txt
I observed that when I have the following value set in my hbase-site.xml file
{code}
property
namehbase.regionserver.wal.encryption/name
valuefalse/value
/property
property
namehbase.regionserver.hlog.reader.impl/name
valueorg.apache.hadoop.hbase.regionserver.wal.SecureProtobufLogReader/value
/property
property
namehbase.regionserver.hlog.writer.impl/name
valueorg.apache.hadoop.hbase.regionserver.wal.SecureProtobufLogWriter/value
/property
{code}
And while log splitting on hbase service restart, master shutdown with
following exception.
Exception in master log
{code}
2014-09-24 17:14:28,590 FATAL [master:host-10-18-40-18:6] master.HMaster:
Master server abort: loaded coprocessors are:
[org.apache.hadoop.hbase.security.access.AccessController]
2014-09-24 17:14:28,590 FATAL [master:host-10-18-40-18:6] master.HMaster:
Unhandled exception. Starting shutdown.
java.io.IOException: error or interrupted while splitting logs in
[hdfs://10.18.40.18:8020/tmp/hbase-ashish/hbase/WALs/host-10-18-40-18,60020,1411558717849-splitting]
Task = installed = 6 done = 0 error = 6
at
org.apache.hadoop.hbase.master.SplitLogManager.splitLogDistributed(SplitLogManager.java:378)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitLog(MasterFileSystem.java:415)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:307)
at
org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:298)
at
org.apache.hadoop.hbase.master.HMaster.splitMetaLogBeforeAssignment(HMaster.java:1071)
at
org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:863)
at
org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:612)
at java.lang.Thread.run(Thread.java:745)
Exception in region server log
2014-09-24 20:10:16,535 WARN [RS_LOG_REPLAY_OPS-host-10-18-40-18:60020-1]
regionserver.SplitLogWorker: log splitting of
WALs/host-10-18-40-18,60020,1411558717849-splitting/host-10-18-40-18%2C60020%2C1411558717849.1411558724316.meta
failed, returning error
java.io.IOException: Cannot get log reader
at
org.apache.hadoop.hbase.regionserver.wal.HLogFactory.createReader(HLogFactory.java:161)
at
org.apache.hadoop.hbase.regionserver.wal.HLogFactory.createReader(HLogFactory.java:89)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.getReader(HLogSplitter.java:660)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.getReader(HLogSplitter.java:569)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.splitLogFile(HLogSplitter.java:282)
at
org.apache.hadoop.hbase.regionserver.wal.HLogSplitter.splitLogFile(HLogSplitter.java:225)
at
org.apache.hadoop.hbase.regionserver.SplitLogWorker$1.exec(SplitLogWorker.java:143)
at
org.apache.hadoop.hbase.regionserver.handler.HLogSplitterHandler.process(HLogSplitterHandler.java:82)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.UnsupportedOperationException: Unable to find suitable
constructor for class
org.apache.hadoop.hbase.regionserver.wal.SecureWALCellCodec
at
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:39)
at
org.apache.hadoop.hbase.regionserver.wal.WALCellCodec.create(WALCellCodec.java:101)
at
org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.getCodec(ProtobufLogReader.java:242)
at
org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.initAfterCompression(ProtobufLogReader.java:247)
at
[jira] [Updated] (HBASE-11178) Remove deprecation annotations from mapred namespace
[ https://issues.apache.org/jira/browse/HBASE-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-11178: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-1 and master. Thanks for the review [~tedyu]. Remove deprecation annotations from mapred namespace Key: HBASE-11178 URL: https://issues.apache.org/jira/browse/HBASE-11178 Project: HBase Issue Type: Sub-task Components: mapreduce Reporter: Nick Dimiduk Assignee: Nick Dimiduk Fix For: 2.0.0, 0.99.1 Attachments: HBASE-11178.00.patch, HBASE-11178.00.patch I guess mapred API is here to stay. We should remove these annotations and clean it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11983) HRegion constructors should not create HLog
[
https://issues.apache.org/jira/browse/HBASE-11983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153525#comment-14153525
]
Nick Dimiduk commented on HBASE-11983:
--
[~busbey] any progress on this one?
HRegion constructors should not create HLog
Key: HBASE-11983
URL: https://issues.apache.org/jira/browse/HBASE-11983
Project: HBase
Issue Type: Bug
Components: wal
Reporter: Enis Soztutar
Assignee: Sean Busbey
We should get rid of HRegion creating its own HLog. It should ALWAYS get the
log from outside.
I think this was added for unit tests, but we should refrain from such
practice in the future (adding UT constructors always leads to weird and
critical bugs down the road). See recent: HBASE-11982, HBASE-11654.
Get rid of weird things like ignoreHLog:
{code}
/**
* @param ignoreHLog - true to skip generate new hlog if it is null, mostly
for createTable
*/
public static HRegion createHRegion(final HRegionInfo info, final Path
rootDir,
final Configuration conf,
final HTableDescriptor hTableDescriptor,
final HLog hlog,
final boolean initialize, final boolean
ignoreHLog)
{code}
We can unify all the createXX and newXX methods and separate creating a
region in the file system vs opening a region.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11178) Remove deprecation annotations from mapred namespace
[ https://issues.apache.org/jira/browse/HBASE-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153550#comment-14153550 ] Hudson commented on HBASE-11178: FAILURE: Integrated in HBase-1.0 #249 (See [https://builds.apache.org/job/HBase-1.0/249/]) HBASE-11178 Remove deprecation annotations from mapred namespace (ndimiduk: rev 33a00c13083e0f795e8954a954653c4a3614583a) * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMap.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/package-info.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableOutputFormat.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableInputFormatBase.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableRecordReader.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/IdentityTableMap.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/Driver.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/GroupingTableMap.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableRecordReaderImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/RowCounter.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableInputFormat.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableReduce.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/package-info.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/IdentityTableReduce.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/HRegionPartitioner.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableSplit.java Remove deprecation annotations from mapred namespace Key: HBASE-11178 URL: https://issues.apache.org/jira/browse/HBASE-11178 Project: HBase Issue Type: Sub-task Components: mapreduce Reporter: Nick Dimiduk Assignee: Nick Dimiduk Fix For: 2.0.0, 0.99.1 Attachments: HBASE-11178.00.patch, HBASE-11178.00.patch I guess mapred API is here to stay. We should remove these annotations and clean it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12098) User granted namespace table create permissions can't create a table
[
https://issues.apache.org/jira/browse/HBASE-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153551#comment-14153551
]
Hudson commented on HBASE-12098:
FAILURE: Integrated in HBase-1.0 #249 (See
[https://builds.apache.org/job/HBase-1.0/249/])
HBASE-12098 User granted namespace table create permissions can't create a
table (Srikanth Srungarapu) (matteo.bertozzi: rev
469bfdf95afbef001e9c47b40efd0c42a1a25a46)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestNamespaceCommands.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java
User granted namespace table create permissions can't create a table
Key: HBASE-12098
URL: https://issues.apache.org/jira/browse/HBASE-12098
Project: HBase
Issue Type: Bug
Components: Client, security
Affects Versions: 0.98.6
Reporter: Dima Spivak
Assignee: Srikanth Srungarapu
Priority: Critical
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12098-master.txt, HBASE-12098.patch,
HBASE-12098_master_v2.patch
From the HBase shell and Java API, I am seeing
{code}ERROR: org.apache.hadoop.hbase.security.AccessDeniedException:
Insufficient permissions for user 'dima' (global, action=CREATE){code}
when I try to create a table in a namespace to which I have been granted
RWXCA permissions by a global admin. Interestingly enough, this only seems to
extend to table creation; the same user is then allowed to disable and drop a
table created by a global admin in that namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-12099:
--
Resolution: Fixed
Hadoop Flags: Incompatible change,Reviewed
Status: Resolved (was: Patch Available)
I've pushed this to 0.98+. Thanks Esteban and all. Esteban, would you mind
adding a release note here as well about the incompatibility in the XML format.
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12118) Explain how to grant permission to a namespace in grant command usage
[ https://issues.apache.org/jira/browse/HBASE-12118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153563#comment-14153563 ] Hudson commented on HBASE-12118: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #522 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/522/]) HBASE-12118 Explain how to grant permission to a namespace in grant command usage (stack: rev 2968d385e65b6ae4737258bdd4fcfbb0d2bb6cdd) * hbase-shell/src/main/ruby/shell/commands/grant.rb Explain how to grant permission to a namespace in grant command usage - Key: HBASE-12118 URL: https://issues.apache.org/jira/browse/HBASE-12118 Project: HBase Issue Type: Improvement Components: documentation, shell Affects Versions: 0.98.6.1 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12118-1.patch, HBASE-12118.patch In the grant command usage, How to grant permission to a namespace is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12119) Master regionserver web UI NOT_FOUND
[
https://issues.apache.org/jira/browse/HBASE-12119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153591#comment-14153591
]
Hadoop QA commented on HBASE-12119:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672068/hbase-12119.patch
against trunk revision .
ATTACHMENT ID: 12672068
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s):
at
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery.testSplitWhileBulkLoadPhase(TestLoadIncrementalHFilesSplitRecovery.java:339)
at
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles.testSimpleLoad(TestLoadIncrementalHFiles.java:100)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11144//console
This message is automatically generated.
Master regionserver web UI NOT_FOUND
Key: HBASE-12119
URL: https://issues.apache.org/jira/browse/HBASE-12119
Project: HBase
Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
Fix For: 2.0.0, 0.99.1
Attachments: hbase-12119.patch
Although the active master is configured to host regions, I got Error 404
NOT_FOUND.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Esteban Gutierrez updated HBASE-12099:
--
Release Note:
The XML element used for the visibility labels in the REST API has been renamed
from label lo labels in order to support old and the new versions of
jackson.
Developers that use visibility labels via REST XML need to modify their
applications in order to use the new XML element name.
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12099) TestScannerModel fails if using jackson 1.9.13
[
https://issues.apache.org/jira/browse/HBASE-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153596#comment-14153596
]
Esteban Gutierrez commented on HBASE-12099:
---
[~enis] done! thanks all.
TestScannerModel fails if using jackson 1.9.13
--
Key: HBASE-12099
URL: https://issues.apache.org/jira/browse/HBASE-12099
Project: HBase
Issue Type: Bug
Components: REST
Affects Versions: 2.0.0, 0.98.7, 0.99.1
Environment: hadoop-2.5.0
Reporter: Esteban Gutierrez
Assignee: Esteban Gutierrez
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12099-1.txt, 12099-2.txt, HBASE-12099.v0.txt
TestScannerModel fails if jackson 1.9.13 is used. (Hadoop 2.5 now uses that
version, see HADOOP-10104):
{code}
Failed tests:
testToJSON(org.apache.hadoop.hbase.rest.model.TestScannerModel):
expected:{batch:100,caching:1000,cacheBlocks:false,endRow:enp5eng=,endTime:1245393318192,maxVersions:2147483647,startRow:YWJyYWNhZGFicmE=,startTime:1245219839331,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],labels:[private,public]}
but
was:{startRow:YWJyYWNhZGFicmE=,endRow:enp5eng=,batch:100,startTime:1245219839331,endTime:1245393318192,maxVersions:2147483647,caching:1000,cacheBlocks:false,column:[Y29sdW1uMQ==,Y29sdW1uMjpmb28=],label:[private,public]}
{code}
The problem is the annotation used for the labels element which is 'label'
instead of 'labels'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12123) Failed assertion in BucketCache after 11331
Nick Dimiduk created HBASE-12123:
Summary: Failed assertion in BucketCache after 11331
Key: HBASE-12123
URL: https://issues.apache.org/jira/browse/HBASE-12123
Project: HBase
Issue Type: Bug
Components: regionserver
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
Fix For: 2.0.0, 0.98.7, 0.99.1
As reported by [~enis]
We have seen this in one of the test runs:
{code}
2014-09-26 05:31:19,788 WARN [main-BucketCacheWriter-2] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,925 INFO [main-BucketCacheWriter-2] bucket.BucketCache:
main-BucketCacheWriter-2 exiting, cacheEnabled=true
2014-09-26 05:31:19,838 WARN [main-BucketCacheWriter-1] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,791 WARN [main-BucketCacheWriter-0] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-0] bucket.BucketCache:
main-BucketCacheWriter-0 exiting, cacheEnabled=true
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-1] bucket.BucketCache:
main-BucketCacheWriter-1 exiting, cacheEnabled=true
{code}
We are still running with assertions on in tests, and this block is failing the
assertion. Seems important:
{code}
if (data instanceof HFileBlock) {
ByteBuffer sliceBuf = ((HFileBlock)
data).getBufferReadOnlyWithHeader();
sliceBuf.rewind();
assert len == sliceBuf.limit() + HFileBlock.EXTRA_SERIALIZATION_SPACE;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12123) Failed assertion in BucketCache after 11331
[
https://issues.apache.org/jira/browse/HBASE-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-12123:
-
Reporter: Enis Soztutar (was: Nick Dimiduk)
Failed assertion in BucketCache after 11331
---
Key: HBASE-12123
URL: https://issues.apache.org/jira/browse/HBASE-12123
Project: HBase
Issue Type: Bug
Components: regionserver
Reporter: Enis Soztutar
Assignee: Nick Dimiduk
Fix For: 2.0.0, 0.98.7, 0.99.1
As reported by [~enis]
We have seen this in one of the test runs:
{code}
2014-09-26 05:31:19,788 WARN [main-BucketCacheWriter-2] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,925 INFO [main-BucketCacheWriter-2] bucket.BucketCache:
main-BucketCacheWriter-2 exiting, cacheEnabled=true
2014-09-26 05:31:19,838 WARN [main-BucketCacheWriter-1] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,791 WARN [main-BucketCacheWriter-0] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-0] bucket.BucketCache:
main-BucketCacheWriter-0 exiting, cacheEnabled=true
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-1] bucket.BucketCache:
main-BucketCacheWriter-1 exiting, cacheEnabled=true
{code}
We are still running with assertions on in tests, and this block is failing
the assertion. Seems important:
{code}
if (data instanceof HFileBlock) {
ByteBuffer sliceBuf = ((HFileBlock)
data).getBufferReadOnlyWithHeader();
sliceBuf.rewind();
assert len == sliceBuf.limit() +
HFileBlock.EXTRA_SERIALIZATION_SPACE;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12123) Failed assertion in BucketCache after 11331
[
https://issues.apache.org/jira/browse/HBASE-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153641#comment-14153641
]
Nick Dimiduk commented on HBASE-12123:
--
This assertion needs to be updated or removed. It does not account for the
possible presence of the next block's header. Seems to me that BucketCache need
not be this familiar with the intimate details of HFileBlock.
Failed assertion in BucketCache after 11331
---
Key: HBASE-12123
URL: https://issues.apache.org/jira/browse/HBASE-12123
Project: HBase
Issue Type: Bug
Components: regionserver
Reporter: Enis Soztutar
Assignee: Nick Dimiduk
Fix For: 2.0.0, 0.98.7, 0.99.1
As reported by [~enis]
We have seen this in one of the test runs:
{code}
2014-09-26 05:31:19,788 WARN [main-BucketCacheWriter-2] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,925 INFO [main-BucketCacheWriter-2] bucket.BucketCache:
main-BucketCacheWriter-2 exiting, cacheEnabled=true
2014-09-26 05:31:19,838 WARN [main-BucketCacheWriter-1] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,791 WARN [main-BucketCacheWriter-0] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-0] bucket.BucketCache:
main-BucketCacheWriter-0 exiting, cacheEnabled=true
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-1] bucket.BucketCache:
main-BucketCacheWriter-1 exiting, cacheEnabled=true
{code}
We are still running with assertions on in tests, and this block is failing
the assertion. Seems important:
{code}
if (data instanceof HFileBlock) {
ByteBuffer sliceBuf = ((HFileBlock)
data).getBufferReadOnlyWithHeader();
sliceBuf.rewind();
assert len == sliceBuf.limit() +
HFileBlock.EXTRA_SERIALIZATION_SPACE;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12123) Failed assertion in BucketCache after 11331
[
https://issues.apache.org/jira/browse/HBASE-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-12123:
-
Attachment: 12123.patch
Trying something like the following.
Failed assertion in BucketCache after 11331
---
Key: HBASE-12123
URL: https://issues.apache.org/jira/browse/HBASE-12123
Project: HBase
Issue Type: Bug
Components: regionserver
Reporter: Enis Soztutar
Assignee: Nick Dimiduk
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12123.patch
As reported by [~enis]
We have seen this in one of the test runs:
{code}
2014-09-26 05:31:19,788 WARN [main-BucketCacheWriter-2] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,925 INFO [main-BucketCacheWriter-2] bucket.BucketCache:
main-BucketCacheWriter-2 exiting, cacheEnabled=true
2014-09-26 05:31:19,838 WARN [main-BucketCacheWriter-1] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,791 WARN [main-BucketCacheWriter-0] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-0] bucket.BucketCache:
main-BucketCacheWriter-0 exiting, cacheEnabled=true
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-1] bucket.BucketCache:
main-BucketCacheWriter-1 exiting, cacheEnabled=true
{code}
We are still running with assertions on in tests, and this block is failing
the assertion. Seems important:
{code}
if (data instanceof HFileBlock) {
ByteBuffer sliceBuf = ((HFileBlock)
data).getBufferReadOnlyWithHeader();
sliceBuf.rewind();
assert len == sliceBuf.limit() +
HFileBlock.EXTRA_SERIALIZATION_SPACE;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12123) Failed assertion in BucketCache after 11331
[
https://issues.apache.org/jira/browse/HBASE-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153645#comment-14153645
]
Enis Soztutar commented on HBASE-12123:
---
+1 if it works for you.
Failed assertion in BucketCache after 11331
---
Key: HBASE-12123
URL: https://issues.apache.org/jira/browse/HBASE-12123
Project: HBase
Issue Type: Bug
Components: regionserver
Reporter: Enis Soztutar
Assignee: Nick Dimiduk
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12123.patch
As reported by [~enis]
We have seen this in one of the test runs:
{code}
2014-09-26 05:31:19,788 WARN [main-BucketCacheWriter-2] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,925 INFO [main-BucketCacheWriter-2] bucket.BucketCache:
main-BucketCacheWriter-2 exiting, cacheEnabled=true
2014-09-26 05:31:19,838 WARN [main-BucketCacheWriter-1] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,791 WARN [main-BucketCacheWriter-0] bucket.BucketCache:
Failed doing drain
java.lang.AssertionError
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$RAMQueueEntry.writeToCache(BucketCache.java:1239)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.doDrain(BucketCache.java:773)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache$WriterThread.run(BucketCache.java:731)
at java.lang.Thread.run(Thread.java:745)
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-0] bucket.BucketCache:
main-BucketCacheWriter-0 exiting, cacheEnabled=true
2014-09-26 05:31:19,926 INFO [main-BucketCacheWriter-1] bucket.BucketCache:
main-BucketCacheWriter-1 exiting, cacheEnabled=true
{code}
We are still running with assertions on in tests, and this block is failing
the assertion. Seems important:
{code}
if (data instanceof HFileBlock) {
ByteBuffer sliceBuf = ((HFileBlock)
data).getBufferReadOnlyWithHeader();
sliceBuf.rewind();
assert len == sliceBuf.limit() +
HFileBlock.EXTRA_SERIALIZATION_SPACE;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[ https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-12115: -- Fix Version/s: (was: 1.0.0) 0.99.1 2.0.0 Fix NumberFormat Exception in TableInputFormatBase. --- Key: HBASE-12115 URL: https://issues.apache.org/jira/browse/HBASE-12115 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Original Estimate: 24h Remaining Estimate: 24h DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[ https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153648#comment-14153648 ] Enis Soztutar commented on HBASE-12115: --- +1 for 0.99+. Fix NumberFormat Exception in TableInputFormatBase. --- Key: HBASE-12115 URL: https://issues.apache.org/jira/browse/HBASE-12115 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Original Estimate: 24h Remaining Estimate: 24h DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12098) User granted namespace table create permissions can't create a table
[
https://issues.apache.org/jira/browse/HBASE-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153702#comment-14153702
]
Hudson commented on HBASE-12098:
FAILURE: Integrated in HBase-0.98 #550 (See
[https://builds.apache.org/job/HBase-0.98/550/])
HBASE-12098 User granted namespace table create permissions can't create a
table (Srikanth Srungarapu) (matteo.bertozzi: rev
6570e0ed87adb1ba1310c8f72181053a99a36532)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestNamespaceCommands.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java
User granted namespace table create permissions can't create a table
Key: HBASE-12098
URL: https://issues.apache.org/jira/browse/HBASE-12098
Project: HBase
Issue Type: Bug
Components: Client, security
Affects Versions: 0.98.6
Reporter: Dima Spivak
Assignee: Srikanth Srungarapu
Priority: Critical
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: 12098-master.txt, HBASE-12098.patch,
HBASE-12098_master_v2.patch
From the HBase shell and Java API, I am seeing
{code}ERROR: org.apache.hadoop.hbase.security.AccessDeniedException:
Insufficient permissions for user 'dima' (global, action=CREATE){code}
when I try to create a table in a namespace to which I have been granted
RWXCA permissions by a global admin. Interestingly enough, this only seems to
extend to table creation; the same user is then allowed to disable and drop a
table created by a global admin in that namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11645) Snapshot for MOB
[ https://issues.apache.org/jira/browse/HBASE-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153713#comment-14153713 ] Jonathan Hsieh commented on HBASE-11645: link to review board here https://reviews.apache.org/r/24448/ Snapshot for MOB Key: HBASE-11645 URL: https://issues.apache.org/jira/browse/HBASE-11645 Project: HBase Issue Type: Sub-task Components: snapshots Reporter: Jingcheng Du Assignee: Jingcheng Du Attachments: HBASE-11645-V2.diff, HBASE-11645.diff Add snapshot support for MOB. In the initial implementation, taking a table snapshot does not preserve the mob data. This issue will make sure that when a snapshot is taken, mob data is properly preserved and is restorable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12115) Fix NumberFormat Exception in TableInputFormatBase.
[ https://issues.apache.org/jira/browse/HBASE-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-12115: -- Resolution: Fixed Fix Version/s: 0.98.7 Status: Resolved (was: Patch Available) Fix NumberFormat Exception in TableInputFormatBase. --- Key: HBASE-12115 URL: https://issues.apache.org/jira/browse/HBASE-12115 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Priority: Minor Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch, 0001-Fix-TableInputFormatBase.reverseDNS-for-ipv6-address.patch Original Estimate: 24h Remaining Estimate: 24h DNS.reverseDns doesn't work well with IPv6 addresses. This patch is to fix that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11980) Change sync to hsync, remove unused InfoServer, and reference our httpserver instead of hadoops
[ https://issues.apache.org/jira/browse/HBASE-11980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153725#comment-14153725 ] Hudson commented on HBASE-11980: ABORTED: Integrated in HBase-TRUNK #5590 (See [https://builds.apache.org/job/HBase-TRUNK/5590/]) HBASE-11980 Change sync to hsync, remove unused InfoServer, and reference our httpserver instead of hadoops (stack: rev aa432fd68fcf89756ceb3d81922ebb0989fb3423) * hbase-server/pom.xml * hbase-server/src/main/java/org/apache/hadoop/hbase/http/InfoServer.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogWriter.java * pom.xml * hbase-server/src/main/java/org/apache/hadoop/hbase/util/InfoServer.java Change sync to hsync, remove unused InfoServer, and reference our httpserver instead of hadoops --- Key: HBASE-11980 URL: https://issues.apache.org/jira/browse/HBASE-11980 Project: HBase Issue Type: Sub-task Reporter: stack Assignee: stack Fix For: 2.0.0, 0.99.1 Attachments: 0001-HBASE-11980-Change-sync-to-hsync-remove-unused-InfoS.patch, 11980v2.txt Subtask that fixes a few issues with our building against hadoop3. Get it in. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12118) Explain how to grant permission to a namespace in grant command usage
[ https://issues.apache.org/jira/browse/HBASE-12118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153726#comment-14153726 ] Hudson commented on HBASE-12118: ABORTED: Integrated in HBase-TRUNK #5590 (See [https://builds.apache.org/job/HBase-TRUNK/5590/]) HBASE-12118 Explain how to grant permission to a namespace in grant command usage (stack: rev 02cdcefe4fd738a969863e599f29c1faae6fec12) * hbase-shell/src/main/ruby/shell/commands/grant.rb Explain how to grant permission to a namespace in grant command usage - Key: HBASE-12118 URL: https://issues.apache.org/jira/browse/HBASE-12118 Project: HBase Issue Type: Improvement Components: documentation, shell Affects Versions: 0.98.6.1 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12118-1.patch, HBASE-12118.patch In the grant command usage, How to grant permission to a namespace is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12119) Master regionserver web UI NOT_FOUND
[ https://issues.apache.org/jira/browse/HBASE-12119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153736#comment-14153736 ] stack commented on HBASE-12119: --- lgtm +1 Master regionserver web UI NOT_FOUND Key: HBASE-12119 URL: https://issues.apache.org/jira/browse/HBASE-12119 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: hbase-12119.patch Although the active master is configured to host regions, I got Error 404 NOT_FOUND. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12119) Master regionserver web UI NOT_FOUND
[ https://issues.apache.org/jira/browse/HBASE-12119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153781#comment-14153781 ] Enis Soztutar commented on HBASE-12119: --- +1. Master regionserver web UI NOT_FOUND Key: HBASE-12119 URL: https://issues.apache.org/jira/browse/HBASE-12119 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: hbase-12119.patch Although the active master is configured to host regions, I got Error 404 NOT_FOUND. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11853) Provide an alternative to the apache build for developers (like me) who aren't committers
[ https://issues.apache.org/jira/browse/HBASE-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153784#comment-14153784 ] stack commented on HBASE-11853: --- Is that running tests? Provide an alternative to the apache build for developers (like me) who aren't committers - Key: HBASE-11853 URL: https://issues.apache.org/jira/browse/HBASE-11853 Project: HBase Issue Type: Sub-task Reporter: Alex Newman Assignee: Alex Newman Attachments: HBASE-11853-testing-v0.patch, HBASE-11853-testing-v1.patch, HBASE-11853-v0.patch, HBASE-11853-v3.patch, HBASE-11853-v4.patch, HBASE-11853-v5.patch Travis CI and Circle-CI now provide free builds for open source projects. I created the capability to run builds this way. Although they are closed source (and thus not a replacement for jenkins IMHO), they are super convenient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11853) Provide an alternative to the apache build for developers (like me) who aren't committers
[ https://issues.apache.org/jira/browse/HBASE-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14153797#comment-14153797 ] Alex Newman commented on HBASE-11853: - Looks like it is running, although every once in a while we get flakey builds. I will take a deeper look at it soon. Provide an alternative to the apache build for developers (like me) who aren't committers - Key: HBASE-11853 URL: https://issues.apache.org/jira/browse/HBASE-11853 Project: HBase Issue Type: Sub-task Reporter: Alex Newman Assignee: Alex Newman Attachments: HBASE-11853-testing-v0.patch, HBASE-11853-testing-v1.patch, HBASE-11853-v0.patch, HBASE-11853-v3.patch, HBASE-11853-v4.patch, HBASE-11853-v5.patch Travis CI and Circle-CI now provide free builds for open source projects. I created the capability to run builds this way. Although they are closed source (and thus not a replacement for jenkins IMHO), they are super convenient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10200) Better error message when HttpServer fails to start due to java.net.BindException
[
https://issues.apache.org/jira/browse/HBASE-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Kumar M R updated HBASE-10200:
Attachment: HBASE-10020-V2.patch
Better error message when HttpServer fails to start due to
java.net.BindException
-
Key: HBASE-10200
URL: https://issues.apache.org/jira/browse/HBASE-10200
Project: HBase
Issue Type: Task
Affects Versions: 2.0.0
Reporter: Ted Yu
Assignee: Kiran Kumar M R
Priority: Minor
Labels: beginner
Fix For: 2.0.0, 0.99.1
Attachments: 10200.out, HBASE-10020-V2.patch, HBASE-10020.patch,
HBASE-10020.patch
Starting HBase using Hoya, I saw the following in log:
{code}
2013-12-17 21:49:06,758 INFO [master:hor12n19:42587] http.HttpServer:
HttpServer.start() threw a non Bind IOException
java.net.BindException: Port in use: hor12n14.gq1.ygridcore.net:12432
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:742)
at org.apache.hadoop.http.HttpServer.start(HttpServer.java:686)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:586)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:344)
at sun.nio.ch.Net.bind(Net.java:336)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at org.apache.hadoop.http.HttpServer.openListener(HttpServer.java:738)
{code}
This was due to hbase.master.info.bindAddress giving static address but Hoya
allocates master dynamically.
Better error message should be provided: when bindAddress points another host
than local host, message should remind user to remove / adjust
hbase.master.info.bindAddress config param from hbase-site.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
