[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639526#comment-14639526 ] Lars Hofhansl commented on HBASE-13992: --- Would like to meet up. Out of the country on vacation until August 11th, though. Re: Tests. I think we can commit this, and file a sub jira to add tests. (On the other hand, why rush? If more tests are requested, why not add them now before commit?) I'm fine either way. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14146) Once replication sees an error it slows down forever
[ https://issues.apache.org/jira/browse/HBASE-14146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-14146: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 1.2.0 2.0.0 Status: Resolved (was: Patch Available) Once replication sees an error it slows down forever Key: HBASE-14146 URL: https://issues.apache.org/jira/browse/HBASE-14146 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 1.2.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14146.patch sleepMultiplier inside of HBaseInterClusterReplicationEndpoint and ReplicationSource never gets reset to zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[
https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639442#comment-14639442
]
Hadoop QA commented on HBASE-14063:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746826/HBASE-14063.patch
against master branch at commit 4ec69ccf3ae8701727299179ac6b5002bbd72c55.
ATTACHMENT ID: 12746826
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1869 checkstyle errors (more than the master's current 1866 errors).
{color:green}+1 findbugs{color}. The patch does not introduce any 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:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ByteBufferUtils.copyFromArrayToBuffer(buf, kvCell.getBuffer(),
kvCell.getKeyOffset(), kvCell.getKeyLength());
+offheapKeyOnlyKV.getQualifierPositionInByteBuffer(),
offheapKeyOnlyKV.getQualifierLength()));
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor.testCoprocessorCanCreateConnectionToRemoteTableWithCustomPool(TestOpenTableInCoprocessor.java:145)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14873//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14873//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14873//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14873//console
This message is automatically generated.
Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
---
Key: HBASE-14063
URL: https://issues.apache.org/jira/browse/HBASE-14063
Project: HBase
Issue Type: Sub-task
Components: regionserver, Scanners
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 2.0.0
Attachments: HBASE-14063.patch
Subtask to ensure that the BytebufferBackedCell gets used in the read path
after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change
the required places and makes the review easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639511#comment-14639511 ] Rick Kellogg commented on HBASE-7621: - On a related issue, I spent most of the day today tracking down a problem with text keys (part1*part2*part3) with embedded asterisks. When I converted them to underscores all the problems went away. Believe the fundamental issue is within the org.apache.hadoop.hbase.util.Bytes.toStringBinary method. It attempts to do some sort of encoding which I believe is not URL friendly. There are no unit tests related to punctuation characters in the KeyValueTestUtil class. REST server doesn't support binary row keys --- Key: HBASE-7621 URL: https://issues.apache.org/jira/browse/HBASE-7621 Project: HBase Issue Type: Bug Components: REST Affects Versions: 0.94.0, 0.95.2 Reporter: Craig Muchinsky The REST server doesn't seem to support using binary (MD5 for example) row keys. I believe the root cause of this is the use of Bytes.toBytes() in the RowSpec.parseRowKeys() method. Based on the use of Bytes.toStringBinary() within RemoteHTable.buildRowSpec(), I believe the converse function Bytes.toBytesBinary() should be used for row key parsing in RowSpec.parseRowKeys(). I also noticed that the RemoteHTable.buildRowSpec() method isn't URL encoding the row key, which is a mismatch to the logic in RowSpec.parseRowKeys() which performs URL decoding for both the start and stop row keys. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[
https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639709#comment-14639709
]
Sean Busbey commented on HBASE-13992:
-
{quote}
Were a project I was a committer on, I'd be mandating the failure tests, as
they are the tests most likely to break things. As I'm not an HBase committer,
I will leave the opinions to others. At the very least, there needs to be a
followup JIRA for the extra tests.
{quote}
HBase works by consensus across our community, not just consensus from those
who have been flagged as more established in the project.
Ted, let me know if you run into any trouble getting these set up or if you
want a hand off on adding them.
Integrate SparkOnHBase into HBase
-
Key: HBASE-13992
URL: https://issues.apache.org/jira/browse/HBASE-13992
Project: HBase
Issue Type: New Feature
Components: spark
Reporter: Ted Malaska
Assignee: Ted Malaska
Fix For: 2.0.0
Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch,
HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch,
HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4,
HBASE-13992.patch.5
This Jira is to ask if SparkOnHBase can find a home in side HBase core.
Here is the github:
https://github.com/cloudera-labs/SparkOnHBase
I am the core author of this project and the license is Apache 2.0
A blog explaining this project is here
http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/
A spark Streaming example is here
http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/
A real customer using this in produce is blogged here
http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/
Please debate and let me know what I can do to make this happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[
https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639495#comment-14639495
]
Hadoop QA commented on HBASE-14069:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746821/0001-Improve-RegionSplitter.patch
against master branch at commit 4ec69ccf3ae8701727299179ac6b5002bbd72c55.
ATTACHMENT ID: 12746821
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1870 checkstyle errors (more than the master's current 1866 errors).
{color:green}+1 findbugs{color}. The patch does not introduce any 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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS
{color:red}-1 core zombie tests{color}. There are 3 zombie test(s):
at
org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor.testCoprocessorCanCreateConnectionToRemoteTableWithCustomPool(TestOpenTableInCoprocessor.java:145)
at
org.apache.camel.component.jetty.jettyproducer.HttpJettyProducerRecipientListCustomThreadPoolTest.testRecipientList(HttpJettyProducerRecipientListCustomThreadPoolTest.java:40)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14874//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14874//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14874//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14874//console
This message is automatically generated.
Add the ability for RegionSplitter to rolling split without using a
SplitAlgorithm
--
Key: HBASE-14069
URL: https://issues.apache.org/jira/browse/HBASE-14069
Project: HBase
Issue Type: New Feature
Components: hbase, util
Reporter: Elliott Clark
Assignee: Abhilash
Attachments: 0001-Improve-RegionSplitter.patch
RegionSplittler is the utility that can rolling split regions. It would be
nice to be able to split regions and have the normal split points get
computed for me so that I'm not reliant on knowing data distribution.
Tested manually on standalone mode for various test cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14153) Typo in ProcedureManagerHost.MASTER_PROCEUDRE_CONF_KEY
Konstantin Shvachko created HBASE-14153:
---
Summary: Typo in ProcedureManagerHost.MASTER_PROCEUDRE_CONF_KEY
Key: HBASE-14153
URL: https://issues.apache.org/jira/browse/HBASE-14153
Project: HBase
Issue Type: Bug
Affects Versions: 1.0.1
Reporter: Konstantin Shvachko
Priority: Trivial
The constant should read {{PROCE _*DU*_ RE}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14143) remove obsolete maven repositories
[ https://issues.apache.org/jira/browse/HBASE-14143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-14143: Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 1.3.0 Release Note: (was: HBASE-14143 Remove obsolete maven repositories) Status: Resolved (was: Patch Available) Thanks Gabor! remove obsolete maven repositories -- Key: HBASE-14143 URL: https://issues.apache.org/jira/browse/HBASE-14143 Project: HBase Issue Type: Bug Reporter: Gabor Liptak Assignee: Gabor Liptak Priority: Minor Fix For: 1.3.0 Attachments: HBASE-14143.base-1.1.patch, HBASE-14143.branch-1.2.patch The root pom.xml contains repositories no longer available and/or updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639575#comment-14639575 ] Rick Kellogg commented on HBASE-7621: - Per the Stargate Wiki, the use of an asterisk (*) is considered a wildcard for Globbing purposes on a Cell or Row Query. See http://wiki.apache.org/hadoop/Hbase/Stargate. Therefore it is invalid to create a row key with an embedded asterisk unless changes are made to support escaping or wildcard logic. REST server doesn't support binary row keys --- Key: HBASE-7621 URL: https://issues.apache.org/jira/browse/HBASE-7621 Project: HBase Issue Type: Bug Components: REST Affects Versions: 0.94.0, 0.95.2, 0.98.4 Reporter: Craig Muchinsky The REST server doesn't seem to support using binary (MD5 for example) row keys. I believe the root cause of this is the use of Bytes.toBytes() in the RowSpec.parseRowKeys() method. Based on the use of Bytes.toStringBinary() within RemoteHTable.buildRowSpec(), I believe the converse function Bytes.toBytesBinary() should be used for row key parsing in RowSpec.parseRowKeys(). I also noticed that the RemoteHTable.buildRowSpec() method isn't URL encoding the row key, which is a mismatch to the logic in RowSpec.parseRowKeys() which performs URL decoding for both the start and stop row keys. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Kellogg updated HBASE-7621: Affects Version/s: 0.98.4 REST server doesn't support binary row keys --- Key: HBASE-7621 URL: https://issues.apache.org/jira/browse/HBASE-7621 Project: HBase Issue Type: Bug Components: REST Affects Versions: 0.94.0, 0.95.2, 0.98.4 Reporter: Craig Muchinsky The REST server doesn't seem to support using binary (MD5 for example) row keys. I believe the root cause of this is the use of Bytes.toBytes() in the RowSpec.parseRowKeys() method. Based on the use of Bytes.toStringBinary() within RemoteHTable.buildRowSpec(), I believe the converse function Bytes.toBytesBinary() should be used for row key parsing in RowSpec.parseRowKeys(). I also noticed that the RemoteHTable.buildRowSpec() method isn't URL encoding the row key, which is a mismatch to the logic in RowSpec.parseRowKeys() which performs URL decoding for both the start and stop row keys. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-7621) REST server doesn't support binary row keys
[ https://issues.apache.org/jira/browse/HBASE-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639523#comment-14639523 ] Rick Kellogg commented on HBASE-7621: - Verified problem exists with 0.98.4.2.2.4.2-2-hadoop2 REST server doesn't support binary row keys --- Key: HBASE-7621 URL: https://issues.apache.org/jira/browse/HBASE-7621 Project: HBase Issue Type: Bug Components: REST Affects Versions: 0.94.0, 0.95.2, 0.98.4 Reporter: Craig Muchinsky The REST server doesn't seem to support using binary (MD5 for example) row keys. I believe the root cause of this is the use of Bytes.toBytes() in the RowSpec.parseRowKeys() method. Based on the use of Bytes.toStringBinary() within RemoteHTable.buildRowSpec(), I believe the converse function Bytes.toBytesBinary() should be used for row key parsing in RowSpec.parseRowKeys(). I also noticed that the RemoteHTable.buildRowSpec() method isn't URL encoding the row key, which is a mismatch to the logic in RowSpec.parseRowKeys() which performs URL decoding for both the start and stop row keys. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639697#comment-14639697 ] Steve Loughran commented on HBASE-13992: Were a project I was a committer on, I'd be mandating the failure tests, as they are the tests most likely to break things. As I'm not an HBase committer, I will leave the opinions to others. At the very least, there needs to be a followup JIRA for the extra tests. As ted notes, they should just throw the standard exceptions. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638800#comment-14638800 ] Ted Malaska commented on HBASE-13992: - Thanks lars. Will do there will be a lot of jiras after this one. Also if u have time next week or the week after I would love to brain storm about the road map. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638666#comment-14638666 ] Lars Hofhansl commented on HBASE-13992: --- +1 on V9. Thanks for your patience [~ted.m]. One more idea for a future improvement: Make BulkGet return things in exactly the same format as distributed scan. Would be cool, since then one could plug ways to get data (bulk get, scan with filter, InputputFormat, etc) and leave all the rest of the code identical. Can do later. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[
https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638721#comment-14638721
]
ramkrishna.s.vasudevan commented on HBASE-14152:
The QA report says no find bugs warning.
But inside
{code}
ugInstance type=VO_VOLATILE_INCREMENT priority=1 abbrev=VO
category=MT_CORRECTNESS
Class classname=org.apache.hadoop.hbase.regionserver.HMobStore
SourceLine classname=org.apache.hadoop.hbase.regionserver.HMobStore
start=85 end=583 sourcefile=HMobStore.java
sourcepath=org/apache/hadoop/hbase/regionserver/HMobStore.java/
/Class
Method classname=org.apache.hadoop.hbase.regionserver.HMobStore
name=updateMobFlushCount signature=()V isStatic=false
SourceLine classname=org.apache.hadoop.hbase.regionserver.HMobStore
start=547 end=548 startBytecode=0 endBytecode=56
sourcefile=HMobStore.java
sourcepath=org/apache/hadoop/hbase/regionserver/HMobStore.java/
/Method
Field classname=org.apache.hadoop.hbase.regionserver.HMobStore
name=mobFlushCount signature=J isStatic=false
SourceLine classname=org.apache.hadoop.hbase.regionserver.HMobStore
sourcefile=HMobStore.java
sourcepath=org/apache/hadoop/hbase/regionserver/HMobStore.java/
/Field
SourceLine classname=org.apache.hadoop.hbase.regionserver.HMobStore
start=547 end=547 startBytecode=7 endBytecode=7
sourcefile=HMobStore.java
sourcepath=org/apache/hadoop/hbase/regionserver/HMobStore.java/
/BugInstance
{code}
Which one is the truth here?
Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
-
Key: HBASE-14152
URL: https://issues.apache.org/jira/browse/HBASE-14152
Project: HBase
Issue Type: Improvement
Components: mob
Affects Versions: 2.0.0
Reporter: Jingcheng Du
Assignee: Jingcheng Du
Fix For: 2.0.0
Attachments: HBASE-14152-V2.patch, HBASE-14152.patch
There are some new warnings in Checkstyle and FindBugs brought in by merging
the feature branch hbase-11339 to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[
https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638684#comment-14638684
]
Hadoop QA commented on HBASE-14152:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746749/HBASE-14152-V2.patch
against master branch at commit 4ec69ccf3ae8701727299179ac6b5002bbd72c55.
ATTACHMENT ID: 12746749
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any 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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14872//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14872//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14872//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14872//console
This message is automatically generated.
Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
-
Key: HBASE-14152
URL: https://issues.apache.org/jira/browse/HBASE-14152
Project: HBase
Issue Type: Improvement
Components: mob
Affects Versions: 2.0.0
Reporter: Jingcheng Du
Assignee: Jingcheng Du
Fix For: 2.0.0
Attachments: HBASE-14152-V2.patch, HBASE-14152.patch
There are some new warnings in Checkstyle and FindBugs brought in by merging
the feature branch hbase-11339 to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639941#comment-14639941
]
Ashish Singhi commented on HBASE-14122:
---
+1 (non-binding)
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2-0.98.patch,
HBASE-14122-v2-branch-1.patch, HBASE-14122-v2.patch, HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14143) remove obsolete maven repositories
[ https://issues.apache.org/jira/browse/HBASE-14143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639731#comment-14639731 ] Hudson commented on HBASE-14143: FAILURE: Integrated in HBase-1.3 #71 (See [https://builds.apache.org/job/HBase-1.3/71/]) HBASE-14143 Remove obsolete maven repositories (busbey: rev e3a7669e0b9784f0e855e9fdf7db281bee540d94) * pom.xml remove obsolete maven repositories -- Key: HBASE-14143 URL: https://issues.apache.org/jira/browse/HBASE-14143 Project: HBase Issue Type: Bug Reporter: Gabor Liptak Assignee: Gabor Liptak Priority: Minor Fix For: 1.3.0 Attachments: HBASE-14143.base-1.1.patch, HBASE-14143.branch-1.2.patch The root pom.xml contains repositories no longer available and/or updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639735#comment-14639735 ] Enis Soztutar commented on HBASE-14070: --- bq. What about replication? Are we trying to order events between clusters? I assume we won't: On the sink we just apply edits at the timestamps at which they happened, which may be in the past. So I think replication does not need special consideration. Sorry I missed this. For replication, the timestamps from cells should just update the Clock of the node. In that case, there is no special handling. Since we always carry the PT+LT components in the timestamps with cells, it is just a matter of doing a receive event per cell in writes from replication. Hybrid Logical Clocks for HBase --- Key: HBASE-14070 URL: https://issues.apache.org/jira/browse/HBASE-14070 Project: HBase Issue Type: New Feature Reporter: Enis Soztutar Assignee: Enis Soztutar Attachments: HybridLogicalClocksforHBaseandPhoenix.docx, HybridLogicalClocksforHBaseandPhoenix.pdf HBase and Phoenix uses systems physical clock (PT) to give timestamps to events (read and writes). This works mostly when the system clock is strictly monotonically increasing and there is no cross-dependency between servers clocks. However we know that leap seconds, general clock skew and clock drift are in fact real. This jira proposes using Hybrid Logical Clocks (HLC) as an implementation of hybrid physical clock + a logical clock. HLC is best of both worlds where it keeps causality relationship similar to logical clocks, but still is compatible with NTP based physical system clock. HLC can be represented in 64bits. A design document is attached and also can be found here: https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[
https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-11276:
--
Resolution: Fixed
Fix Version/s: 1.3.0
1.1.2
1.2.0
1.0.2
2.0.0
Status: Resolved (was: Patch Available)
I've committed this to 1.0+ (does not compile with 0.98). I've changed the
package name to be {{util}} to be consistent with the rest of packages.Thanks
[~carp84] for the patch.
Add back support for running ChaosMonkey as standalone tool
---
Key: HBASE-11276
URL: https://issues.apache.org/jira/browse/HBASE-11276
Project: HBase
Issue Type: Task
Affects Versions: 0.98.0, 0.96.0, 0.99.0
Reporter: Dima Spivak
Assignee: Yu Li
Priority: Minor
Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0
Attachments: HBASE-11276.patch, HBASE-11276_v2.patch,
HBASE-11276_v3.patch, HBASE-11276_v4.patch
[According to the ref
guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it
was once possible to run ChaosMonkey as a standalone tool against a deployed
cluster. After 0.94, this is no longer possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14146) Once replication sees an error it slows down forever
[ https://issues.apache.org/jira/browse/HBASE-14146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639817#comment-14639817 ] Hudson commented on HBASE-14146: FAILURE: Integrated in HBase-1.2 #80 (See [https://builds.apache.org/job/HBase-1.2/80/]) HBASE-14146 Fix Once replication sees an error it slows down forever (eclark: rev 2414fdc7a51f957ff1805062e4e141565865772a) * hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Once replication sees an error it slows down forever Key: HBASE-14146 URL: https://issues.apache.org/jira/browse/HBASE-14146 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 1.2.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14146.patch sleepMultiplier inside of HBaseInterClusterReplicationEndpoint and ReplicationSource never gets reset to zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14122:
---
Attachment: HBASE-14122-v2.patch
v2 patch rebased against current master and incorporating feedback
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2.patch, HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639896#comment-14639896 ] Hudson commented on HBASE-11276: FAILURE: Integrated in HBase-1.1 #590 (See [https://builds.apache.org/job/HBase-1.1/590/]) HBASE-11276 Add back support for running ChaosMonkey as standalone tool (Yu Li) (enis: rev 8a54799ceedb4f8ecec42c15f2c32c0cf262f5aa) * hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestingUtility.java * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639934#comment-14639934 ] Hudson commented on HBASE-11276: SUCCESS: Integrated in HBase-1.2-IT #64 (See [https://builds.apache.org/job/HBase-1.2-IT/64/]) HBASE-11276 Add back support for running ChaosMonkey as standalone tool (Yu Li) (enis: rev a692295e23bccead7c285f94f10f2dc85986dba1) * hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestingUtility.java * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639944#comment-14639944 ] Hudson commented on HBASE-11276: SUCCESS: Integrated in HBase-1.3-IT #57 (See [https://builds.apache.org/job/HBase-1.3-IT/57/]) HBASE-11276 Add back support for running ChaosMonkey as standalone tool (Yu Li) (enis: rev 4a041fd837f30e90384d06a825b4db82c6be0838) * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java * hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestingUtility.java Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14146) Once replication sees an error it slows down forever
[ https://issues.apache.org/jira/browse/HBASE-14146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639821#comment-14639821 ] Hudson commented on HBASE-14146: SUCCESS: Integrated in HBase-1.2-IT #63 (See [https://builds.apache.org/job/HBase-1.2-IT/63/]) HBASE-14146 Fix Once replication sees an error it slows down forever (eclark: rev 2414fdc7a51f957ff1805062e4e141565865772a) * hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Once replication sees an error it slows down forever Key: HBASE-14146 URL: https://issues.apache.org/jira/browse/HBASE-14146 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 1.2.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14146.patch sleepMultiplier inside of HBaseInterClusterReplicationEndpoint and ReplicationSource never gets reset to zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Malaska updated HBASE-13992: Attachment: HBASE-13992.10.patch Fixed scala tests so that the HBase test cluster doesn't blow up. Also added in failure tests for bad column and bad table. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.10.patch, HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14082) Add replica id to JMX metrics names
[
https://issues.apache.org/jira/browse/HBASE-14082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639875#comment-14639875
]
Lei Chen commented on HBASE-14082:
--
If an existing parser uses exact-string matching or order-sensitive key-value
matching, it may not be backwards compatible.
For example, If we have 2 regions, one primary and one secondary
{{namespace_default_table_sales_region__metric_storeCount}}
{{namespace_default_table_sales_region__metric_storeCount}}
becomes
{{namespace_default_table_sales_region__metric_storeCount}}
{{namespace_default_table_sales_region__replicaid_1_metric_storeCount}}
Since I'm not familiar with any existing parser, please correct me if I made
any false assumption.
Add replica id to JMX metrics names
---
Key: HBASE-14082
URL: https://issues.apache.org/jira/browse/HBASE-14082
Project: HBase
Issue Type: Improvement
Components: metrics
Reporter: Lei Chen
Assignee: Lei Chen
Attachments: HBASE-14082-v1.patch
Today, via JMX, one cannot distinguish a primary region from a replica. A
possible solution is to add replica id to JMX metrics names. The benefits may
include, for example:
# Knowing the latency of a read request on a replica region means the first
attempt to the primary region has timeout.
# Write requests on replicas are due to the replication process, while the
ones on primary are from clients.
# In case of looking for hot spots of read operations, replicas should be
excluded since TIMELINE reads are sent to all replicas.
To implement, we can change the format of metrics names found at
{code}Hadoop-HBase-RegionServer-Regions-Attributes{code}
from
{code}namespace_namespace_table_tablename_region_regionname_metric_metricname{code}
to
{code}namespace_namespace_table_tablename_region_regionname_replicaid_replicaid_metric_metricname{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14122:
---
Attachment: HBASE-14122-v2-branch-1.patch
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2-branch-1.patch, HBASE-14122-v2.patch,
HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14146) Once replication sees an error it slows down forever
[ https://issues.apache.org/jira/browse/HBASE-14146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639888#comment-14639888 ] Hudson commented on HBASE-14146: FAILURE: Integrated in HBase-1.3 #72 (See [https://builds.apache.org/job/HBase-1.3/72/]) HBASE-14146 Fix Once replication sees an error it slows down forever (eclark: rev 7b8311eb90b0993447e515de1cf9bda42dbf9e92) * hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Once replication sees an error it slows down forever Key: HBASE-14146 URL: https://issues.apache.org/jira/browse/HBASE-14146 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 1.2.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14146.patch sleepMultiplier inside of HBaseInterClusterReplicationEndpoint and ReplicationSource never gets reset to zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639734#comment-14639734 ] Ted Malaska commented on HBASE-13992: - Hey Steve, no worries. You r right those tests are important and I will try to get a patch in the next couple of hours. But just note this is not a perfect patch. After this there is about 4 to 6 more patches to make this really great. Once this patch is in more people can help and we can multi thread our development effort. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14082) Add replica id to JMX metrics names
[
https://issues.apache.org/jira/browse/HBASE-14082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639815#comment-14639815
]
Enis Soztutar commented on HBASE-14082:
---
I think we can do this so that it is backwards compatible:
{code}
_region_ + regionWrapper.getRegionName() +
+ if (regionWrapper.getReplicaId() 0) {
+_replicaid_ + regionWrapper.getReplicaId() +
+ }
_metric_;
{code}
Add replica id to JMX metrics names
---
Key: HBASE-14082
URL: https://issues.apache.org/jira/browse/HBASE-14082
Project: HBase
Issue Type: Improvement
Components: metrics
Reporter: Lei Chen
Assignee: Lei Chen
Attachments: HBASE-14082-v1.patch
Today, via JMX, one cannot distinguish a primary region from a replica. A
possible solution is to add replica id to JMX metrics names. The benefits may
include, for example:
# Knowing the latency of a read request on a replica region means the first
attempt to the primary region has timeout.
# Write requests on replicas are due to the replication process, while the
ones on primary are from clients.
# In case of looking for hot spots of read operations, replicas should be
excluded since TIMELINE reads are sent to all replicas.
To implement, we can change the format of metrics names found at
{code}Hadoop-HBase-RegionServer-Regions-Attributes{code}
from
{code}namespace_namespace_table_tablename_region_regionname_metric_metricname{code}
to
{code}namespace_namespace_table_tablename_region_regionname_replicaid_replicaid_metric_metricname{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Li updated HBASE-11276: -- Attachment: HBASE-11276-0.98.patch Thanks [~enis], here is the patch for 0.98 Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639841#comment-14639841 ] Yu Li commented on HBASE-11276: --- Yes, and maybe we could use HBASE-14084 to do this :-) Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14122:
---
Status: Patch Available (was: Open)
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2.patch, HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639870#comment-14639870 ] Hudson commented on HBASE-11276: FAILURE: Integrated in HBase-TRUNK #6677 (See [https://builds.apache.org/job/HBase-TRUNK/6677/]) HBASE-11276 Add back support for running ChaosMonkey as standalone tool (Yu Li) (enis: rev dad4cad30e5b0c69694ee90908ad8e74c592d821) * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java * hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestingUtility.java Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Attachment: HBASE-14063_1.patch Fixing checkstyle comments and wrapping 100 lines. Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch, HBASE-14063_1.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Status: Open (was: Patch Available) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639806#comment-14639806 ] Enis Soztutar commented on HBASE-11276: --- Now, we have to update the documentation in the book about the tool. Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Status: Patch Available (was: Open) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch, HBASE-14063_1.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639811#comment-14639811 ] Jingcheng Du commented on HBASE-14152: -- Hi Ram, where did you find this? It's found in the latest patch or the first one? This message tells a FindBugs violation in class, field and method, updateMObFlushCount is a method name, mobFlushCount is a field name. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14143) remove obsolete maven repositories
[ https://issues.apache.org/jira/browse/HBASE-14143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639831#comment-14639831 ] Hudson commented on HBASE-14143: SUCCESS: Integrated in HBase-1.3-IT #56 (See [https://builds.apache.org/job/HBase-1.3-IT/56/]) HBASE-14143 Remove obsolete maven repositories (busbey: rev e3a7669e0b9784f0e855e9fdf7db281bee540d94) * pom.xml remove obsolete maven repositories -- Key: HBASE-14143 URL: https://issues.apache.org/jira/browse/HBASE-14143 Project: HBase Issue Type: Bug Reporter: Gabor Liptak Assignee: Gabor Liptak Priority: Minor Fix For: 1.3.0 Attachments: HBASE-14143.base-1.1.patch, HBASE-14143.branch-1.2.patch The root pom.xml contains repositories no longer available and/or updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14146) Once replication sees an error it slows down forever
[ https://issues.apache.org/jira/browse/HBASE-14146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639832#comment-14639832 ] Hudson commented on HBASE-14146: SUCCESS: Integrated in HBase-1.3-IT #56 (See [https://builds.apache.org/job/HBase-1.3-IT/56/]) HBASE-14146 Fix Once replication sees an error it slows down forever (eclark: rev 7b8311eb90b0993447e515de1cf9bda42dbf9e92) * hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Once replication sees an error it slows down forever Key: HBASE-14146 URL: https://issues.apache.org/jira/browse/HBASE-14146 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 1.2.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14146.patch sleepMultiplier inside of HBaseInterClusterReplicationEndpoint and ReplicationSource never gets reset to zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14146) Once replication sees an error it slows down forever
[ https://issues.apache.org/jira/browse/HBASE-14146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639844#comment-14639844 ] Hudson commented on HBASE-14146: FAILURE: Integrated in HBase-TRUNK #6676 (See [https://builds.apache.org/job/HBase-TRUNK/6676/]) HBASE-14146 Fix Once replication sees an error it slows down forever (eclark: rev e087a9ef51ac2d48a56ec331a27d779974e13ca5) * hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java Once replication sees an error it slows down forever Key: HBASE-14146 URL: https://issues.apache.org/jira/browse/HBASE-14146 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 1.2.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14146.patch sleepMultiplier inside of HBaseInterClusterReplicationEndpoint and ReplicationSource never gets reset to zero. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reassigned HBASE-14122:
--
Assignee: Andrew Purtell
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639883#comment-14639883 ] Hudson commented on HBASE-11276: FAILURE: Integrated in HBase-1.0 #996 (See [https://builds.apache.org/job/HBase-1.0/996/]) HBASE-11276 Add back support for running ChaosMonkey as standalone tool (Yu Li) (enis: rev 647d27992415e5c934106d185619d9f88b478e0b) * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java * hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestingUtility.java Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639894#comment-14639894 ] ramkrishna.s.vasudevan commented on HBASE-14152: https://builds.apache.org/job/PreCommit-HBASE-Build/14872//artifact/patchprocess/patchFindbugsWarningshbase-server.xml I used this link [~jingchengdu]. Not sure whether we have really solved the findbugs issue after seeing this. But the QA report says no findbugs. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639920#comment-14639920 ] Hudson commented on HBASE-11276: FAILURE: Integrated in HBase-1.2 #81 (See [https://builds.apache.org/job/HBase-1.2/81/]) HBASE-11276 Add back support for running ChaosMonkey as standalone tool (Yu Li) (enis: rev a692295e23bccead7c285f94f10f2dc85986dba1) * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java * hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestingUtility.java Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[ https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639877#comment-14639877 ] Lei Chen commented on HBASE-13965: -- I've been trying to apply the patch on a test hbase cluster for verifying. Currently experiencing some compatibility issues. Will update status once got results. Stochastic Load Balancer JMX Metrics Key: HBASE-13965 URL: https://issues.apache.org/jira/browse/HBASE-13965 Project: HBase Issue Type: Improvement Components: Balancer, metrics Reporter: Lei Chen Assignee: Lei Chen Attachments: HBASE-13965-v3.patch, HBASE-13965-v4.patch, HBASE-13965-v5.patch, HBASE-13965-v6.patch, HBASE-13965-v7.patch, HBASE-13965-v8.patch, HBASE-13965_v2.patch, HBase-13965-v1.patch, stochasticloadbalancerclasses_v2.png Today’s default HBase load balancer (the Stochastic load balancer) is cost function based. The cost function weights are tunable but no visibility into those cost function results is directly provided. A driving example is a cluster we have been tuning which has skewed rack size (one rack has half the nodes of the other few racks). We are tuning the cluster for uniform response time from all region servers with the ability to tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and RegionCountSkew Cost is difficult without a way to attribute each cost function’s contribution to overall cost. What this jira proposes is to provide visibility via JMX into each cost function of the stochastic load balancer, as well as the overall cost of the balancing plan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14122:
---
Attachment: HBASE-14122-v2-0.98.patch
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2-0.98.patch,
HBASE-14122-v2-branch-1.patch, HBASE-14122-v2.patch, HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14148) Web UI Framable Page
[ https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apekshit Sharma updated HBASE-14148: Attachment: HBASE-14148-v2-master.patch Web UI Framable Page Key: HBASE-14148 URL: https://issues.apache.org/jira/browse/HBASE-14148 Project: HBase Issue Type: Bug Reporter: Apekshit Sharma Assignee: Apekshit Sharma Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch The web UIs do not include the X-Frame-Options header to prevent the pages from being framed from another site. Reference: https://www.owasp.org/index.php/Clickjacking https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14148) Web UI Framable Page
[ https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639408#comment-14639408 ] Apekshit Sharma commented on HBASE-14148: - [~eclark] bq. I don't think that this is complex enough that we should be copying code from others. I agree with you that it is very trivial piece of code and that anyone would have written same. However, when i was reading on clickjacking, i came across it, read it and it was in the back of my head when I was doing changes. So the fact remains, that i referenced it and since the code looks same (it couldn't have looked different, right!), I'd would prefer to have the new-BSD license here. We all are anyways interested in the feature, right? Web UI Framable Page Key: HBASE-14148 URL: https://issues.apache.org/jira/browse/HBASE-14148 Project: HBase Issue Type: Bug Reporter: Apekshit Sharma Assignee: Apekshit Sharma Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch The web UIs do not include the X-Frame-Options header to prevent the pages from being framed from another site. Reference: https://www.owasp.org/index.php/Clickjacking https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639471#comment-14639471 ] Sean Busbey commented on HBASE-13992: - I agree that test handling around failures will be necessary for this to be robust and usable for downstream folks. Steve, do you think we need those tests in place to land on master? Would you be fine with making those additions part of the gate for getting this backported to branch-1? The expectation is that backporting to branch-1 will mark when users end up interacting with this code. Similar to needing failure handling we'll definitely need to have user-facing docs before that happens, but those docs are part of the follow on work after this first jira. I think right now the expectation is that master won't have a release before the end of the year and these changes in branch-1 would correspond to 1.3. Given that we're trying to get 1.2 out now, that would give us at least 3-4 months for the follow on tickets. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639587#comment-14639587 ] Ted Malaska commented on HBASE-13992: - I can add in those tests today or tomorrow. There if nothing special about the Spark integration it just gives a connection to the executors. So in these cases we will just see a normal HBase exception like if you did without spark. test against non-existent database attempt to work with a table that doesn't exist attempt to read a column that doesn't exist Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14148) Web UI Framable Page
[
https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639602#comment-14639602
]
Hadoop QA commented on HBASE-14148:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746852/HBASE-14148-v2-master.patch
against master branch at commit 4ec69ccf3ae8701727299179ac6b5002bbd72c55.
ATTACHMENT ID: 12746852
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14875//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14875//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14875//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14875//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14875//console
This message is automatically generated.
Web UI Framable Page
Key: HBASE-14148
URL: https://issues.apache.org/jira/browse/HBASE-14148
Project: HBase
Issue Type: Bug
Reporter: Apekshit Sharma
Assignee: Apekshit Sharma
Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch
The web UIs do not include the X-Frame-Options header to prevent the pages
from being framed from another site.
Reference:
https://www.owasp.org/index.php/Clickjacking
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet
https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13788) Shell comands do not support column qualifiers containing colon (:)
[
https://issues.apache.org/jira/browse/HBASE-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638822#comment-14638822
]
Dave Latham commented on HBASE-13788:
-
Don't have time to make a patch for this at present.
Shell comands do not support column qualifiers containing colon (:)
---
Key: HBASE-13788
URL: https://issues.apache.org/jira/browse/HBASE-13788
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.98.0, 0.96.0, 1.0.0, 1.1.0
Reporter: Dave Latham
Assignee: Pankaj Kumar
The shell interprets the colon within the qualifier as a delimiter to a
FORMATTER instead of part of the qualifier itself.
Example from the mailing list:
Hmph, I may have spoken too soon. I know I tested this at one point and
it worked, but now I'm getting different results:
On the new cluster, I created a duplicate test table:
hbase(main):043:0 create 'content3', {NAME = 'x', BLOOMFILTER =
'NONE', REPLICATION_SCOPE = '0', VERSIONS = '3', COMPRESSION =
'NONE', MIN_VERSIONS = '0', TTL = '2147483647', BLOCKSIZE = '65536',
IN_MEMORY = 'false', BLOCKCACHE = 'true'}
Then I pull some data from the imported table:
hbase(main):045:0 scan 'content', {LIMIT=1,
STARTROW='A:9223370612089311807:twtr:57013379'}
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408
column=x:twitter:username, timestamp=1424775595345, value=BERITA
INFORMASI!
Then put it:
hbase(main):046:0 put
'content3','A:9223370612089311807:twtr:570133798827921408',
'x:twitter:username', 'BERITA INFORMASI!'
But then when I query it, I see that I've lost the column qualifier
:username:
hbase(main):046:0 scan 'content3'
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408 column=x:twitter,
timestamp=1432745301788, value=BERITA INFORMASI!
Even though I'm missing one of the qualifiers, I can at least filter on
columns in this sample table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhilash updated HBASE-14069: - Description: RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. was:RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14151) Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638231#comment-14638231 ] Anoop Sam John commented on HBASE-14151: +1. Will commit now Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339 Key: HBASE-14151 URL: https://issues.apache.org/jira/browse/HBASE-14151 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14151.patch When merging the feature branch hbase-11339 into trunk, one unnecessary file is committed. We need to remove it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13788) Shell comands do not support column qualifiers containing colon (:)
[
https://issues.apache.org/jira/browse/HBASE-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638254#comment-14638254
]
Pankaj Kumar commented on HBASE-13788:
--
Sounds good, adding new attribute will be good to avoid such limitation in
future. Are you planning to provide a patch?
Shell comands do not support column qualifiers containing colon (:)
---
Key: HBASE-13788
URL: https://issues.apache.org/jira/browse/HBASE-13788
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.98.0, 0.96.0, 1.0.0, 1.1.0
Reporter: Dave Latham
Assignee: Pankaj Kumar
The shell interprets the colon within the qualifier as a delimiter to a
FORMATTER instead of part of the qualifier itself.
Example from the mailing list:
Hmph, I may have spoken too soon. I know I tested this at one point and
it worked, but now I'm getting different results:
On the new cluster, I created a duplicate test table:
hbase(main):043:0 create 'content3', {NAME = 'x', BLOOMFILTER =
'NONE', REPLICATION_SCOPE = '0', VERSIONS = '3', COMPRESSION =
'NONE', MIN_VERSIONS = '0', TTL = '2147483647', BLOCKSIZE = '65536',
IN_MEMORY = 'false', BLOCKCACHE = 'true'}
Then I pull some data from the imported table:
hbase(main):045:0 scan 'content', {LIMIT=1,
STARTROW='A:9223370612089311807:twtr:57013379'}
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408
column=x:twitter:username, timestamp=1424775595345, value=BERITA
INFORMASI!
Then put it:
hbase(main):046:0 put
'content3','A:9223370612089311807:twtr:570133798827921408',
'x:twitter:username', 'BERITA INFORMASI!'
But then when I query it, I see that I've lost the column qualifier
:username:
hbase(main):046:0 scan 'content3'
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408 column=x:twitter,
timestamp=1432745301788, value=BERITA INFORMASI!
Even though I'm missing one of the qualifiers, I can at least filter on
columns in this sample table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13788) Shell comands do not support column qualifiers containing colon (:)
[
https://issues.apache.org/jira/browse/HBASE-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638255#comment-14638255
]
Pankaj Kumar commented on HBASE-13788:
--
Sounds good, adding new attribute will be good to avoid such limitation in
future. Are you planning to provide a patch?
Shell comands do not support column qualifiers containing colon (:)
---
Key: HBASE-13788
URL: https://issues.apache.org/jira/browse/HBASE-13788
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.98.0, 0.96.0, 1.0.0, 1.1.0
Reporter: Dave Latham
Assignee: Pankaj Kumar
The shell interprets the colon within the qualifier as a delimiter to a
FORMATTER instead of part of the qualifier itself.
Example from the mailing list:
Hmph, I may have spoken too soon. I know I tested this at one point and
it worked, but now I'm getting different results:
On the new cluster, I created a duplicate test table:
hbase(main):043:0 create 'content3', {NAME = 'x', BLOOMFILTER =
'NONE', REPLICATION_SCOPE = '0', VERSIONS = '3', COMPRESSION =
'NONE', MIN_VERSIONS = '0', TTL = '2147483647', BLOCKSIZE = '65536',
IN_MEMORY = 'false', BLOCKCACHE = 'true'}
Then I pull some data from the imported table:
hbase(main):045:0 scan 'content', {LIMIT=1,
STARTROW='A:9223370612089311807:twtr:57013379'}
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408
column=x:twitter:username, timestamp=1424775595345, value=BERITA
INFORMASI!
Then put it:
hbase(main):046:0 put
'content3','A:9223370612089311807:twtr:570133798827921408',
'x:twitter:username', 'BERITA INFORMASI!'
But then when I query it, I see that I've lost the column qualifier
:username:
hbase(main):046:0 scan 'content3'
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408 column=x:twitter,
timestamp=1432745301788, value=BERITA INFORMASI!
Even though I'm missing one of the qualifiers, I can at least filter on
columns in this sample table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhilash updated HBASE-14069: - Attachment: 0001-Improve-RegionSplitter.patch Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-14151) Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John resolved HBASE-14151. Resolution: Fixed Hadoop Flags: Reviewed Thanks for noticing this and giving a quick patch Jingcheng. Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339 Key: HBASE-14151 URL: https://issues.apache.org/jira/browse/HBASE-14151 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14151.patch When merging the feature branch hbase-11339 into trunk, one unnecessary file is committed. We need to remove it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12295) Prevent block eviction under us if reads are in progress from the BBs
[ https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638713#comment-14638713 ] Hudson commented on HBASE-12295: FAILURE: Integrated in HBase-TRUNK #6675 (See [https://builds.apache.org/job/HBase-TRUNK/6675/]) HBASE-12295 - Addendum for multiGets to add the call back(Ram) (ramkrishna: rev 4ec69ccf3ae8701727299179ac6b5002bbd72c55) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java Prevent block eviction under us if reads are in progress from the BBs - Key: HBASE-12295 URL: https://issues.apache.org/jira/browse/HBASE-12295 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-12295.pdf, HBASE-12295_1.patch, HBASE-12295_1.pdf, HBASE-12295_10.patch, HBASE-12295_12.patch, HBASE-12295_14.patch, HBASE-12295_15.patch, HBASE-12295_16.patch, HBASE-12295_16.patch, HBASE-12295_17.patch, HBASE-12295_18.patch, HBASE-12295_2.patch, HBASE-12295_21.patch, HBASE-12295_4.patch, HBASE-12295_4.pdf, HBASE-12295_5.pdf, HBASE-12295_9.patch, HBASE-12295_addendum.patch, HBASE-12295_final.patch, HBASE-12295_trunk.patch While we try to serve the reads from the BBs directly from the block cache, we need to ensure that the blocks does not get evicted under us while reading. This JIRA is to discuss and implement a strategy for the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13788) Shell comands do not support column qualifiers containing colon (:)
[
https://issues.apache.org/jira/browse/HBASE-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639376#comment-14639376
]
Elliott Clark commented on HBASE-13788:
---
I was saying what [~davelatham] was. We shouldn't try and interpret columns.
All we should do is split on the first colon. Everything else needs to be
specified somewhere else.
Shell comands do not support column qualifiers containing colon (:)
---
Key: HBASE-13788
URL: https://issues.apache.org/jira/browse/HBASE-13788
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.98.0, 0.96.0, 1.0.0, 1.1.0
Reporter: Dave Latham
Assignee: Pankaj Kumar
The shell interprets the colon within the qualifier as a delimiter to a
FORMATTER instead of part of the qualifier itself.
Example from the mailing list:
Hmph, I may have spoken too soon. I know I tested this at one point and
it worked, but now I'm getting different results:
On the new cluster, I created a duplicate test table:
hbase(main):043:0 create 'content3', {NAME = 'x', BLOOMFILTER =
'NONE', REPLICATION_SCOPE = '0', VERSIONS = '3', COMPRESSION =
'NONE', MIN_VERSIONS = '0', TTL = '2147483647', BLOCKSIZE = '65536',
IN_MEMORY = 'false', BLOCKCACHE = 'true'}
Then I pull some data from the imported table:
hbase(main):045:0 scan 'content', {LIMIT=1,
STARTROW='A:9223370612089311807:twtr:57013379'}
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408
column=x:twitter:username, timestamp=1424775595345, value=BERITA
INFORMASI!
Then put it:
hbase(main):046:0 put
'content3','A:9223370612089311807:twtr:570133798827921408',
'x:twitter:username', 'BERITA INFORMASI!'
But then when I query it, I see that I've lost the column qualifier
:username:
hbase(main):046:0 scan 'content3'
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408 column=x:twitter,
timestamp=1432745301788, value=BERITA INFORMASI!
Even though I'm missing one of the qualifiers, I can at least filter on
columns in this sample table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639377#comment-14639377 ] Yu Li commented on HBASE-11276: --- I don't think the zombie tests are caused by change in this jira since we're simply adding a standalone tool and should have no impact on existing tests. Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Attachments: HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[
https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639390#comment-14639390
]
Elliott Clark commented on HBASE-14069:
---
* You're doing a lot with start and end keys trying to keep them in a map. I
don't think that there's a need. Just look for a region with the start key of
the parent region to come online ( child one). When you find that, look for
another region (child two) with the start key of that's the same as child one's
end key. If those two regions come online then it's split.
* requiredRegionSize and requiredNumRegions aren't good names. They aren't
required. They are what is being requested. The sizes may or may not get there.
The number may or may not get there.
* configuration names should start with hbase.
* Sizes are usually specified in bytes unless the name says otherwise.
* splitAllRegions is a bad name. It's splitting regions that meet some
guidelines.
* You're creating a lot of filesystems. Get one and keep it the whole time.
* {code}Pairbyte[][], byte[][] tmp = null;{code} This could be named better.
* Line 507 seems wrong. There's no need for start and end keys to be the same
length.
* Why have line 511?
* Why the magic numbers in the retry counter factory?
Add the ability for RegionSplitter to rolling split without using a
SplitAlgorithm
--
Key: HBASE-14069
URL: https://issues.apache.org/jira/browse/HBASE-14069
Project: HBase
Issue Type: New Feature
Components: hbase, util
Reporter: Elliott Clark
Assignee: Abhilash
Attachments: 0001-Improve-RegionSplitter.patch
RegionSplittler is the utility that can rolling split regions. It would be
nice to be able to split regions and have the normal split points get
computed for me so that I'm not reliant on knowing data distribution.
Tested manually on standalone mode for various test cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13408) HBase In-Memory Memstore Compaction
[ https://issues.apache.org/jira/browse/HBASE-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638791#comment-14638791 ] Eshcar Hillel commented on HBASE-13408: --- I did some learning of the flush-by-column-family feature (HBASE-10201). I think it will help us in supporting WAL truncation in compacting memstore. [~Apache9] I would appreciate if you can confirm that this should work. In the current implementation, when a region flushes a store, the previous sequence id that was associated with this store in the WAL oldestUnflushedStoreSequenceIds set is removed. The first put operation to occur after the flush installs a new sequence id for the store. The WAL uses this bookeeping when it needs to decide which WAL files can be archived (WAL truncation). For compacting memstore we would like to keep the sequence id in the oldestUnflushedStoreSequenceIds set of the WAL even after a flush is invoked. Instead, the memstore compaction thread will be responsible for setting an approximation of the correct sequence id for the store in the set. To this end, the compacting memstore maintains a mapping of timestamp to region sequence number (the same sequence numbers that are attached to WAL edits). Whenever a flush is invoked on a compacting memstore it adds the current time and current sequence number pair to this mapping. As an additional artifact of the memstore compaction the minimal timestamp that is still present in the memstore is computed. This timestamp is then used to identify the maximal sequence id in the timestamp-seqId mapping for which no entries are left in the memstore. Finally, it uses this approximated sequence number to update the oldestUnflushedStoreSequenceIds set. This way the WAL is being truncated with some delay with respect to the real sequence number, but the memory overhead if fairly small (only a small map of ts-seq is added to the memstore) when compared to a solution that adds a sequence number to each cell in the memstore and then uses it to find the *exact* oldest unflushed sequence id. What say you? HBase In-Memory Memstore Compaction --- Key: HBASE-13408 URL: https://issues.apache.org/jira/browse/HBASE-13408 Project: HBase Issue Type: New Feature Reporter: Eshcar Hillel Attachments: HBaseIn-MemoryMemstoreCompactionDesignDocument-ver02.pdf, HBaseIn-MemoryMemstoreCompactionDesignDocument.pdf, InMemoryMemstoreCompactionEvaluationResults.pdf A store unit holds a column family in a region, where the memstore is its in-memory component. The memstore absorbs all updates to the store; from time to time these updates are flushed to a file on disk, where they are compacted. Unlike disk components, the memstore is not compacted until it is written to the filesystem and optionally to block-cache. This may result in underutilization of the memory due to duplicate entries per row, for example, when hot data is continuously updated. Generally, the faster the data is accumulated in memory, more flushes are triggered, the data sinks to disk more frequently, slowing down retrieval of data, even if very recent. In high-churn workloads, compacting the memstore can help maintain the data in memory, and thereby speed up data retrieval. We suggest a new compacted memstore with the following principles: 1.The data is kept in memory for as long as possible 2.Memstore data is either compacted or in process of being compacted 3.Allow a panic mode, which may interrupt an in-progress compaction and force a flush of part of the memstore. We suggest applying this optimization only to in-memory column families. A design document is attached. This feature was previously discussed in HBASE-5311. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13788) Shell comands do not support column qualifiers containing colon (:)
[
https://issues.apache.org/jira/browse/HBASE-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639328#comment-14639328
]
Dave Latham commented on HBASE-13788:
-
Elliott, I don't understand. Are you saying CF:Formatter:Qualifier? It
could work if you required formatter or at least 2 colons to always be present,
but that would change the usage for people not using formatters.
Shell comands do not support column qualifiers containing colon (:)
---
Key: HBASE-13788
URL: https://issues.apache.org/jira/browse/HBASE-13788
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.98.0, 0.96.0, 1.0.0, 1.1.0
Reporter: Dave Latham
Assignee: Pankaj Kumar
The shell interprets the colon within the qualifier as a delimiter to a
FORMATTER instead of part of the qualifier itself.
Example from the mailing list:
Hmph, I may have spoken too soon. I know I tested this at one point and
it worked, but now I'm getting different results:
On the new cluster, I created a duplicate test table:
hbase(main):043:0 create 'content3', {NAME = 'x', BLOOMFILTER =
'NONE', REPLICATION_SCOPE = '0', VERSIONS = '3', COMPRESSION =
'NONE', MIN_VERSIONS = '0', TTL = '2147483647', BLOCKSIZE = '65536',
IN_MEMORY = 'false', BLOCKCACHE = 'true'}
Then I pull some data from the imported table:
hbase(main):045:0 scan 'content', {LIMIT=1,
STARTROW='A:9223370612089311807:twtr:57013379'}
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408
column=x:twitter:username, timestamp=1424775595345, value=BERITA
INFORMASI!
Then put it:
hbase(main):046:0 put
'content3','A:9223370612089311807:twtr:570133798827921408',
'x:twitter:username', 'BERITA INFORMASI!'
But then when I query it, I see that I've lost the column qualifier
:username:
hbase(main):046:0 scan 'content3'
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408 column=x:twitter,
timestamp=1432745301788, value=BERITA INFORMASI!
Even though I'm missing one of the qualifiers, I can at least filter on
columns in this sample table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639357#comment-14639357 ] Steve Loughran commented on HBASE-13992: There's not much in the way of tests here, in particular, not much in the way of generation of failure conditions and validation of outcome Ideally, there'd be one test to generate each failure condition: the exception handling including those which downgrade a failure to a log message...the test should verify that such actions are the correct response. At the very least, I'd recommend # test against non-existent database # attempt to work with a table that doesn't exist # attempt to read a column that doesn't exist I'd also make sure test teardown is robust, catching exceptions downgrading to logs. That way, if something didn't get set up properly, the root cause of the failure isn't hidden by any exception generated in teardown. Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Status: Patch Available (was: Open) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhilash updated HBASE-14069: - Status: Patch Available (was: Open) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Components: hbase, util Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter.patch, 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13788) Shell comands do not support column qualifiers containing colon (:)
[
https://issues.apache.org/jira/browse/HBASE-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639295#comment-14639295
]
Elliott Clark commented on HBASE-13788:
---
Why not just left split on the first colon?
The CF can't have a colon in it. So the first one is the divider between cf and
qualifier. Everything else is the qualifier.
Shell comands do not support column qualifiers containing colon (:)
---
Key: HBASE-13788
URL: https://issues.apache.org/jira/browse/HBASE-13788
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 0.98.0, 0.96.0, 1.0.0, 1.1.0
Reporter: Dave Latham
Assignee: Pankaj Kumar
The shell interprets the colon within the qualifier as a delimiter to a
FORMATTER instead of part of the qualifier itself.
Example from the mailing list:
Hmph, I may have spoken too soon. I know I tested this at one point and
it worked, but now I'm getting different results:
On the new cluster, I created a duplicate test table:
hbase(main):043:0 create 'content3', {NAME = 'x', BLOOMFILTER =
'NONE', REPLICATION_SCOPE = '0', VERSIONS = '3', COMPRESSION =
'NONE', MIN_VERSIONS = '0', TTL = '2147483647', BLOCKSIZE = '65536',
IN_MEMORY = 'false', BLOCKCACHE = 'true'}
Then I pull some data from the imported table:
hbase(main):045:0 scan 'content', {LIMIT=1,
STARTROW='A:9223370612089311807:twtr:57013379'}
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408
column=x:twitter:username, timestamp=1424775595345, value=BERITA
INFORMASI!
Then put it:
hbase(main):046:0 put
'content3','A:9223370612089311807:twtr:570133798827921408',
'x:twitter:username', 'BERITA INFORMASI!'
But then when I query it, I see that I've lost the column qualifier
:username:
hbase(main):046:0 scan 'content3'
ROW COLUMN+CELL
A:9223370612089311807:twtr:570133798827921408 column=x:twitter,
timestamp=1432745301788, value=BERITA INFORMASI!
Even though I'm missing one of the qualifiers, I can at least filter on
columns in this sample table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Attachment: HBASE-14063.patch Patch for QA. Renames OffheapKeyOnlyKV to ByteBufferedKeyOnlyKV. The KeyOnlyKV is changed to ByteBufferedKeyOnlyKV in the HFileReader so that the kvs created for comparison are always considered to work with BBs. Tested with L1 cached with both BB based KV and having a byte[] backed KeyonlyKV. No significant difference in the perf and GC. Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12751) Allow RowLock to be reader writer
[ https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639243#comment-14639243 ] Elliott Clark commented on HBASE-12751: --- bq.Let me look at the patch again. The above description sounds like how it mostly worked previous. Let me see Thanks E. Yeah it's pretty similar. The patch is just adding to the wal append/sync queue earlier. That allows a creating the sequence id/mvcc number for real. Because the edits are already in the queue for the wal we know for sure that their ordering is the same as the sequence number. The bonus nice thing from this re-ordering is that adding to the memstore and the append are running in parallel. Allow RowLock to be reader writer - Key: HBASE-12751 URL: https://issues.apache.org/jira/browse/HBASE-12751 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 2.0.0, 1.3.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-12751-v1.patch, HBASE-12751-v10.patch, HBASE-12751-v10.patch, HBASE-12751-v11.patch, HBASE-12751-v12.patch, HBASE-12751-v13.patch, HBASE-12751-v14.patch, HBASE-12751-v15.patch, HBASE-12751-v16.patch, HBASE-12751-v2.patch, HBASE-12751-v3.patch, HBASE-12751-v4.patch, HBASE-12751-v5.patch, HBASE-12751-v6.patch, HBASE-12751-v7.patch, HBASE-12751-v8.patch, HBASE-12751-v9.patch, HBASE-12751.patch Right now every write operation grabs a row lock. This is to prevent values from changing during a read modify write operation (increment or check and put). However it limits parallelism in several different scenarios. If there are several puts to the same row but different columns or stores then this is very limiting. If there are puts to the same column then mvcc number should ensure a consistent ordering. So locking is not needed. However locking for check and put or increment is still needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhilash updated HBASE-14069: - Attachment: (was: 0001-Improve-RegionSplitter.patch) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Components: hbase, util Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[
https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639290#comment-14639290
]
Sean Busbey commented on HBASE-13992:
-
I'm trying to do a final build to make sure I've got the patch applied
correctly, and the new integration tests are failing.
{code}
[INFO] --- scalatest-maven-plugin:1.0:test (integration-test) @ hbase-spark ---
WARNING: -c has been deprecated and will be reused for a different (but still
very cool) purpose in ScalaTest 2.0. Please change all uses of -c to -P.
Discovery starting.
Discovery completed in 284 milliseconds.
Run starting. Expected test count is: 11
HBaseDStreamFunctionsSuite:
HBaseContextSuite:
HBaseRDDFunctionsSuite:
2015-07-23 10:50:56.702 java[97585:6403] Unable to load realm info from
SCDynamicStore
*** RUN ABORTED ***
java.util.concurrent.ExecutionException: java.io.IOException: Shutting down
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at
org.scalatest.tools.ConcurrentDistributor.waitUntilDone(ConcurrentDistributor.scala:52)
at org.scalatest.tools.Runner$.doRunRunRunDaDoRunRun(Runner.scala:2549)
at
org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:1044)
at
org.scalatest.tools.Runner$$anonfun$runOptionallyWithPassFailReporter$2.apply(Runner.scala:1043)
at
org.scalatest.tools.Runner$.withClassLoaderAndDispatchReporter(Runner.scala:2722)
at
org.scalatest.tools.Runner$.runOptionallyWithPassFailReporter(Runner.scala:1043)
at org.scalatest.tools.Runner$.main(Runner.scala:860)
at org.scalatest.tools.Runner.main(Runner.scala)
...
Cause: java.io.IOException: Shutting down
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:232)
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1040)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1006)
at
org.apache.hadoop.hbase.spark.HBaseDStreamFunctionsSuite.beforeAll(HBaseDStreamFunctionsSuite.scala:44)
at
org.scalatest.BeforeAndAfterAll$class.beforeAll(BeforeAndAfterAll.scala:187)
at
org.apache.hadoop.hbase.spark.HBaseDStreamFunctionsSuite.beforeAll(HBaseDStreamFunctionsSuite.scala:30)
at org.scalatest.BeforeAndAfterAll$class.run(BeforeAndAfterAll.scala:253)
at
org.apache.hadoop.hbase.spark.HBaseDStreamFunctionsSuite.run(HBaseDStreamFunctionsSuite.scala:30)
at org.scalatest.tools.SuiteRunner.run(SuiteRunner.scala:55)
...
Cause: java.lang.RuntimeException: Failed construction of Master: class
org.apache.hadoop.hbase.master.HMasterAddress already in use
at
org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:143)
at
org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:218)
at
org.apache.hadoop.hbase.LocalHBaseCluster.init(LocalHBaseCluster.java:154)
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:214)
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1040)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1006)
at
org.apache.hadoop.hbase.spark.HBaseDStreamFunctionsSuite.beforeAll(HBaseDStreamFunctionsSuite.scala:44)
at
org.scalatest.BeforeAndAfterAll$class.beforeAll(BeforeAndAfterAll.scala:187)
at
org.apache.hadoop.hbase.spark.HBaseDStreamFunctionsSuite.beforeAll(HBaseDStreamFunctionsSuite.scala:30)
...
Cause: java.net.BindException: Port in use: 0.0.0.0:16010
at org.apache.hadoop.hbase.http.HttpServer.openListeners(HttpServer.java:1013)
at org.apache.hadoop.hbase.http.HttpServer.start(HttpServer.java:949)
at org.apache.hadoop.hbase.http.InfoServer.start(InfoServer.java:91)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.putUpWebUI(HRegionServer.java:1789)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.init(HRegionServer.java:604)
at org.apache.hadoop.hbase.master.HMaster.init(HMaster.java:363)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
...
Cause: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:444)
at sun.nio.ch.Net.bind(Net.java:436)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at
[jira] [Updated] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhilash updated HBASE-14069: - Attachment: 0001-Improve-RegionSplitter.patch Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Components: hbase, util Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter.patch, 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
Jingcheng Du created HBASE-14152: Summary: Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12295) Prevent block eviction under us if reads are in progress from the BBs
[ https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-12295: --- Attachment: HBASE-12295_addendum.patch A critical addendum that would be needed for HBASE-12295 to work with multiGets. While testing with random multiGets found that the place we are creating the callBack was like we were overriding the initially created callbacks and because of that the scanners that were created for the older regions were not getting closed. This addendum fixes that issue. It is now tested and there are no issues with it. Prevent block eviction under us if reads are in progress from the BBs - Key: HBASE-12295 URL: https://issues.apache.org/jira/browse/HBASE-12295 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-12295.pdf, HBASE-12295_1.patch, HBASE-12295_1.pdf, HBASE-12295_10.patch, HBASE-12295_12.patch, HBASE-12295_14.patch, HBASE-12295_15.patch, HBASE-12295_16.patch, HBASE-12295_16.patch, HBASE-12295_17.patch, HBASE-12295_18.patch, HBASE-12295_2.patch, HBASE-12295_21.patch, HBASE-12295_4.patch, HBASE-12295_4.pdf, HBASE-12295_5.pdf, HBASE-12295_9.patch, HBASE-12295_addendum.patch, HBASE-12295_final.patch, HBASE-12295_trunk.patch While we try to serve the reads from the BBs directly from the block cache, we need to ensure that the blocks does not get evicted under us while reading. This JIRA is to discuss and implement a strategy for the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Attachment: HBASE-14152.patch Upload the patch to fix the warnings in Checkstyle and FindBugs. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13867) Add endpoint coprocessor guide to HBase book
[
https://issues.apache.org/jira/browse/HBASE-13867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638368#comment-14638368
]
Hadoop QA commented on HBASE-13867:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746716/HBASE-13867.2.patch
against master branch at commit 493f36c899bc990de0400fbf777a2bf29c5c60e3.
ATTACHMENT ID: 12746716
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14871//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14871//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14871//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14871//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14871//console
This message is automatically generated.
Add endpoint coprocessor guide to HBase book
Key: HBASE-13867
URL: https://issues.apache.org/jira/browse/HBASE-13867
Project: HBase
Issue Type: Task
Components: Coprocessors, documentation
Reporter: Vladimir Rodionov
Assignee: Gaurav Bhardwaj
Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2
Attachments: HBASE-13867.1.patch, HBASE-13867.2.patch
Endpoint coprocessors are very poorly documented.
Coprocessor section of HBase book must be updated either with its own
endpoint coprocessors HOW-TO guide or, at least, with the link(s) to some
other guides. There is good description here:
http://www.3pillarglobal.com/insights/hbase-coprocessors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638435#comment-14638435 ] ramkrishna.s.vasudevan commented on HBASE-14152: Discussed with Jingcheng. +1 on patch. The change to volatile to Atomic in HMobStore was a find bug comment. Similar comment may exist in for the normal Store/Region. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhilash updated HBASE-14069: - Component/s: util hbase Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Components: hbase, util Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14151) Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638452#comment-14638452 ] Hudson commented on HBASE-14151: FAILURE: Integrated in HBase-TRUNK #6674 (See [https://builds.apache.org/job/HBase-TRUNK/6674/]) HBASE-14151 Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339. (Jingcheng) (anoopsamjohn: rev 4f60d9c28d80472d195637eeff98e19fcdf62af5) * hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java.rej Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339 Key: HBASE-14151 URL: https://issues.apache.org/jira/browse/HBASE-14151 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14151.patch When merging the feature branch hbase-11339 into trunk, one unnecessary file is committed. We need to remove it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11339) HBase MOB
[ https://issues.apache.org/jira/browse/HBASE-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638451#comment-14638451 ] Hudson commented on HBASE-11339: FAILURE: Integrated in HBase-TRUNK #6674 (See [https://builds.apache.org/job/HBase-TRUNK/6674/]) HBASE-14151 Remove the unnecessary file ProtobufUtil.java.rej which is brought in by merging hbase-11339. (Jingcheng) (anoopsamjohn: rev 4f60d9c28d80472d195637eeff98e19fcdf62af5) * hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java.rej HBase MOB - Key: HBASE-11339 URL: https://issues.apache.org/jira/browse/HBASE-11339 Project: HBase Issue Type: Umbrella Components: regionserver, Scanners Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0, hbase-11339 Attachments: 11339-master-v10.patch, 11339-master-v3.txt, 11339-master-v4.txt, 11339-master-v5.txt, 11339-master-v6.txt, 11339-master-v7.txt, 11339-master-v8.patch, 11339-master-v9.patch, HBase MOB Design-v2.pdf, HBase MOB Design-v3.pdf, HBase MOB Design-v4.pdf, HBase MOB Design-v5.pdf, HBase MOB Design.pdf, MOB user guide.docx, MOB user guide_v2.docx, MOB user guide_v3.docx, MOB user guide_v4.docx, MOB user guide_v5.docx, hbase-11339-150519.patch, hbase-11339-in-dev.patch, hbase-11339.150417.patch, merge-150212.patch, merge.150212b.patch, merge.150212c.patch, merge.150710.patch It's quite useful to save the medium binary data like images, documents into Apache HBase. Unfortunately directly saving the binary MOB(medium object) to HBase leads to a worse performance since the frequent split and compaction. In this design, the MOB data are stored in an more efficient way, which keeps a high write/read performance and guarantees the data consistency in Apache HBase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12751) Allow RowLock to be reader writer
[ https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638576#comment-14638576 ] stack commented on HBASE-12751: --- bq. People were really digging into sequence id a lot on tests. Crew on your side [~eclark]? Some notes: https://docs.google.com/document/d/16beczDie-KU1uSpJvd0GoUlQbPtQBL93rOOPqnE5Ma0/edit# bq. Do we want to make the locking fair? I think so as a means of evening out the latencies. bq. All edits are queued in the wal before they are put in the memstore... Our comparitor on the map does that. Let me look at the patch again. The above description sounds like how it mostly worked previous. Let me see Thanks E. Allow RowLock to be reader writer - Key: HBASE-12751 URL: https://issues.apache.org/jira/browse/HBASE-12751 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 2.0.0, 1.3.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-12751-v1.patch, HBASE-12751-v10.patch, HBASE-12751-v10.patch, HBASE-12751-v11.patch, HBASE-12751-v12.patch, HBASE-12751-v13.patch, HBASE-12751-v14.patch, HBASE-12751-v15.patch, HBASE-12751-v16.patch, HBASE-12751-v2.patch, HBASE-12751-v3.patch, HBASE-12751-v4.patch, HBASE-12751-v5.patch, HBASE-12751-v6.patch, HBASE-12751-v7.patch, HBASE-12751-v8.patch, HBASE-12751-v9.patch, HBASE-12751.patch Right now every write operation grabs a row lock. This is to prevent values from changing during a read modify write operation (increment or check and put). However it limits parallelism in several different scenarios. If there are several puts to the same row but different columns or stores then this is very limiting. If there are puts to the same column then mvcc number should ensure a consistent ordering. So locking is not needed. However locking for check and put or increment is still needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638596#comment-14638596 ] Jingcheng Du commented on HBASE-14152: -- I use mobFileCount += 1 instead of mobFileCount++ since I want to turn off the FindBugs warnings, I think mobFileCount++ can trigger that warning. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638594#comment-14638594 ] Jingcheng Du commented on HBASE-14152: -- Right, this is not atomic, and cannot avoid the race condition. I think metrics is a rough statistics, few race condition is allowed? HBase has some similar usages in HStore where the volatile variables are used. I think it made a tradeoff between the accuracy and speed? Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638531#comment-14638531 ] Anoop Sam John commented on HBASE-14152: Wait.. How this fix will avoid that warn? mobFlushCount += 1; is also like 3 ops internally and as a whole it is not atomic. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Attachment: HBASE-14152-V2.patch Upload a new patch to fix an issue in FindBugs. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-12295) Prevent block eviction under us if reads are in progress from the BBs
[ https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan resolved HBASE-12295. Resolution: Fixed Committed. Thanks for the review Anoop. Prevent block eviction under us if reads are in progress from the BBs - Key: HBASE-12295 URL: https://issues.apache.org/jira/browse/HBASE-12295 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-12295.pdf, HBASE-12295_1.patch, HBASE-12295_1.pdf, HBASE-12295_10.patch, HBASE-12295_12.patch, HBASE-12295_14.patch, HBASE-12295_15.patch, HBASE-12295_16.patch, HBASE-12295_16.patch, HBASE-12295_17.patch, HBASE-12295_18.patch, HBASE-12295_2.patch, HBASE-12295_21.patch, HBASE-12295_4.patch, HBASE-12295_4.pdf, HBASE-12295_5.pdf, HBASE-12295_9.patch, HBASE-12295_addendum.patch, HBASE-12295_final.patch, HBASE-12295_trunk.patch While we try to serve the reads from the BBs directly from the block cache, we need to ensure that the blocks does not get evicted under us while reading. This JIRA is to discuss and implement a strategy for the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Status: Patch Available (was: Open) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (HBASE-12295) Prevent block eviction under us if reads are in progress from the BBs
[ https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reopened HBASE-12295: Prevent block eviction under us if reads are in progress from the BBs - Key: HBASE-12295 URL: https://issues.apache.org/jira/browse/HBASE-12295 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-12295.pdf, HBASE-12295_1.patch, HBASE-12295_1.pdf, HBASE-12295_10.patch, HBASE-12295_12.patch, HBASE-12295_14.patch, HBASE-12295_15.patch, HBASE-12295_16.patch, HBASE-12295_16.patch, HBASE-12295_17.patch, HBASE-12295_18.patch, HBASE-12295_2.patch, HBASE-12295_21.patch, HBASE-12295_4.patch, HBASE-12295_4.pdf, HBASE-12295_5.pdf, HBASE-12295_9.patch, HBASE-12295_addendum.patch, HBASE-12295_final.patch, HBASE-12295_trunk.patch While we try to serve the reads from the BBs directly from the block cache, we need to ensure that the blocks does not get evicted under us while reading. This JIRA is to discuss and implement a strategy for the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12295) Prevent block eviction under us if reads are in progress from the BBs
[ https://issues.apache.org/jira/browse/HBASE-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638493#comment-14638493 ] Anoop Sam John commented on HBASE-12295: +1 Prevent block eviction under us if reads are in progress from the BBs - Key: HBASE-12295 URL: https://issues.apache.org/jira/browse/HBASE-12295 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-12295.pdf, HBASE-12295_1.patch, HBASE-12295_1.pdf, HBASE-12295_10.patch, HBASE-12295_12.patch, HBASE-12295_14.patch, HBASE-12295_15.patch, HBASE-12295_16.patch, HBASE-12295_16.patch, HBASE-12295_17.patch, HBASE-12295_18.patch, HBASE-12295_2.patch, HBASE-12295_21.patch, HBASE-12295_4.patch, HBASE-12295_4.pdf, HBASE-12295_5.pdf, HBASE-12295_9.patch, HBASE-12295_addendum.patch, HBASE-12295_final.patch, HBASE-12295_trunk.patch While we try to serve the reads from the BBs directly from the block cache, we need to ensure that the blocks does not get evicted under us while reading. This JIRA is to discuss and implement a strategy for the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[
https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638516#comment-14638516
]
Anoop Sam John commented on HBASE-14152:
+1
{code}
- mobFlushCount++;
+ mobFlushCount += 1;
{code}
Nice catch by findbugs :-)
Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
-
Key: HBASE-14152
URL: https://issues.apache.org/jira/browse/HBASE-14152
Project: HBase
Issue Type: Improvement
Components: mob
Affects Versions: 2.0.0
Reporter: Jingcheng Du
Assignee: Jingcheng Du
Fix For: 2.0.0
Attachments: HBASE-14152-V2.patch, HBASE-14152.patch
There are some new warnings in Checkstyle and FindBugs brought in by merging
the feature branch hbase-11339 to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
