[jira] [Commented] (HBASE-10358) Shell changes for setting consistency per request
[ https://issues.apache.org/jira/browse/HBASE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303559#comment-15303559 ] Hudson commented on HBASE-10358: FAILURE: Integrated in HBase-1.4 #181 (See [https://builds.apache.org/job/HBase-1.4/181/]) HBASE-10358 Shell changes for setting consistency per request (yi liang) (enis: rev 70c3a7854f148acb1a04c6d873884c6b2f703cb9) * hbase-shell/src/main/ruby/shell/commands/scan.rb * hbase-shell/src/main/ruby/shell/commands/get.rb * hbase-shell/src/main/ruby/shell/formatter.rb * hbase-shell/src/main/ruby/hbase/table.rb > Shell changes for setting consistency per request > - > > Key: HBASE-10358 > URL: https://issues.apache.org/jira/browse/HBASE-10358 > Project: HBase > Issue Type: New Feature > Components: shell >Reporter: Enis Soztutar >Assignee: yi liang > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: Screen Shot 2016-04-21 at 3.09.52 PM.png, Screen Shot > 2016-05-05 at 10.38.27 AM.png, shell.patch, shell4.patch, shell_3.patch > > > We can add shell support to set consistency per request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[
https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303541#comment-15303541
]
stack commented on HBASE-15896:
---
[~appy] I tried it:
kalashnikov:hbase.git.commit stack$ ./dev-support/findHangingTests.py
Traceback (most recent call last):
File "./dev-support/findHangingTests.py", line 23, in
import requests
ImportError: No module named requests
You remember how to fix the above? Here is what i have:
{code}
kalashnikov:hbase.git.commit stack$ pip show requests
---
Metadata-Version: 2.0
Name: requests
Version: 2.10.0
Summary: Python HTTP for Humans.
Home-page: http://python-requests.org
Author: Kenneth Reitz
Author-email: m...@kennethreitz.com
Installer: pip
License: Apache 2.0
Location: /usr/local/lib/python2.7/site-packages
Requires:
Classifiers:
Development Status :: 5 - Production/Stable
Intended Audience :: Developers
Natural Language :: English
License :: OSI Approved :: Apache Software License
Programming Language :: Python
Programming Language :: Python :: 2.6
Programming Language :: Python :: 2.7
Programming Language :: Python :: 3
Programming Language :: Python :: 3.3
Programming Language :: Python :: 3.4
Programming Language :: Python :: 3.5
Programming Language :: Python :: Implementation :: CPython
Programming Language :: Python :: Implementation :: PyPy
{code}
Thanks.
> Add timeout tests to flaky list from report-flakies.py
> --
>
> Key: HBASE-15896
> URL: https://issues.apache.org/jira/browse/HBASE-15896
> Project: HBase
> Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
> Attachments: HBASE-15896_master_v1.patch,
> HBASE-15896_master_v2.patch, HBASE-15896_master_v3.patch
>
>
> - Adds timed-out tests to flaky list. Dumpes two new files for reference,
> 'timeout' and 'failed' for corresponding list of bad tests.
> - Set --max-builds for different urls separately. This is needed so that we
> can turn the knobs for post-commit job and flaky-tests job separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
[ https://issues.apache.org/jira/browse/HBASE-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303522#comment-15303522 ] Gary Helmling commented on HBASE-15830: --- Committed to master. Thanks for the patch [~colinma]. > Sasl encryption doesn't work with AsyncRpcChannelImpl > - > > Key: HBASE-15830 > URL: https://issues.apache.org/jira/browse/HBASE-15830 > Project: HBase > Issue Type: Bug >Reporter: Colin Ma > Fix For: 2.0.0 > > Attachments: HBASE-15830.001.patch, HBASE-15830.002.patch, > HBASE-15830.003.patch, HBASE-15830.004.patch > > > Currently, sasl encryption doesn't work with AsyncRpcChannelImpl, there has 3 > problems: > 1. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslClientHandler.java#L308] > will throw the following exception: > java.lang.UnsupportedOperationException: direct buffer > at > io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199) > at > org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:308) > 2. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java#L212] > has deadlocks problem. > 3. TestAsyncSecureIPC doesn't cover the sasl encryption test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
[ https://issues.apache.org/jira/browse/HBASE-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Helmling updated HBASE-15830: -- Fix Version/s: 2.0.0 > Sasl encryption doesn't work with AsyncRpcChannelImpl > - > > Key: HBASE-15830 > URL: https://issues.apache.org/jira/browse/HBASE-15830 > Project: HBase > Issue Type: Bug >Reporter: Colin Ma > Fix For: 2.0.0 > > Attachments: HBASE-15830.001.patch, HBASE-15830.002.patch, > HBASE-15830.003.patch, HBASE-15830.004.patch > > > Currently, sasl encryption doesn't work with AsyncRpcChannelImpl, there has 3 > problems: > 1. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslClientHandler.java#L308] > will throw the following exception: > java.lang.UnsupportedOperationException: direct buffer > at > io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199) > at > org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:308) > 2. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java#L212] > has deadlocks problem. > 3. TestAsyncSecureIPC doesn't cover the sasl encryption test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303447#comment-15303447 ] Hudson commented on HBASE-15854: FAILURE: Integrated in HBase-Trunk_matrix #951 (See [https://builds.apache.org/job/HBase-Trunk_matrix/951/]) HBASE-15854 Log the cause of SASL connection failures (Robert Yokota) (apurtell: rev fdaf3be84fc0732efba00aff87801a939612f785) * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10358) Shell changes for setting consistency per request
[ https://issues.apache.org/jira/browse/HBASE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303448#comment-15303448 ] Hudson commented on HBASE-10358: FAILURE: Integrated in HBase-Trunk_matrix #951 (See [https://builds.apache.org/job/HBase-Trunk_matrix/951/]) HBASE-10358 Shell changes for setting consistency per request (yi liang) (enis: rev b89d88a19306f25e8aca57ea1b01b725ffe861e9) * hbase-shell/src/main/ruby/shell/formatter.rb * hbase-shell/src/main/ruby/shell/commands/scan.rb * hbase-shell/src/main/ruby/shell/commands/get.rb * hbase-shell/src/main/ruby/hbase/table.rb > Shell changes for setting consistency per request > - > > Key: HBASE-10358 > URL: https://issues.apache.org/jira/browse/HBASE-10358 > Project: HBase > Issue Type: New Feature > Components: shell >Reporter: Enis Soztutar >Assignee: yi liang > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: Screen Shot 2016-04-21 at 3.09.52 PM.png, Screen Shot > 2016-05-05 at 10.38.27 AM.png, shell.patch, shell4.patch, shell_3.patch > > > We can add shell support to set consistency per request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
[
https://issues.apache.org/jira/browse/HBASE-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303437#comment-15303437
]
Hadoop QA commented on HBASE-15830:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 9s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
55s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 3s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
49s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
28s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
51s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 52s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 52s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 9s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
2s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 12s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 12s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 49s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
49s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
28s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 1s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
25s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 51s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 51s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 56s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 85m 51s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
36s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 134m 33s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806541/HBASE-15830.004.patch
|
| JIRA Issue | HBASE-15830 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf900.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
|
[jira] [Commented] (HBASE-15898) Document G1GC Recommendations
[
https://issues.apache.org/jira/browse/HBASE-15898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303410#comment-15303410
]
Hadoop QA commented on HBASE-15898:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
16s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
0s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 23s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 19s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
46s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
0s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
25m 40s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 24s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 99m 42s
{color} | {color:green} root in the patch passed. {color} |
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m 22s
{color} | {color:red} Patch generated 1 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 143m 23s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806533/HBASE-15898.patch |
| JIRA Issue | HBASE-15898 |
| Optional Tests | asflicense javac javadoc unit |
| uname | Linux pietas.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / b89d88a |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/2032/testReport/ |
| asflicense |
https://builds.apache.org/job/PreCommit-HBASE-Build/2032/artifact/patchprocess/patch-asflicense-problems.txt
|
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2032/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> Document G1GC Recommendations
> -
>
> Key: HBASE-15898
> URL: https://issues.apache.org/jira/browse/HBASE-15898
> Project: HBase
> Issue Type: Bug
> Components: documentation, java
>Affects Versions: 2.0.0
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-15898.patch
>
>
> Document G1GC recommendations for HBase
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-10358) Shell changes for setting consistency per request
[ https://issues.apache.org/jira/browse/HBASE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303381#comment-15303381 ] Hudson commented on HBASE-10358: SUCCESS: Integrated in HBase-1.3-IT #682 (See [https://builds.apache.org/job/HBase-1.3-IT/682/]) HBASE-10358 Shell changes for setting consistency per request (yi liang) (enis: rev 25e21ee196d18fa0490d386ed21eeea7a9ecfeb0) * hbase-shell/src/main/ruby/shell/commands/get.rb * hbase-shell/src/main/ruby/hbase/table.rb * hbase-shell/src/main/ruby/shell/commands/scan.rb * hbase-shell/src/main/ruby/shell/formatter.rb > Shell changes for setting consistency per request > - > > Key: HBASE-10358 > URL: https://issues.apache.org/jira/browse/HBASE-10358 > Project: HBase > Issue Type: New Feature > Components: shell >Reporter: Enis Soztutar >Assignee: yi liang > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: Screen Shot 2016-04-21 at 3.09.52 PM.png, Screen Shot > 2016-05-05 at 10.38.27 AM.png, shell.patch, shell4.patch, shell_3.patch > > > We can add shell support to set consistency per request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303371#comment-15303371 ] Hudson commented on HBASE-15854: FAILURE: Integrated in HBase-1.3 #717 (See [https://builds.apache.org/job/HBase-1.3/717/]) HBASE-15854 Log the cause of SASL connection failures (Robert Yokota) (apurtell: rev b1e498e77097920990561071e02ff2afd9852161) * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10358) Shell changes for setting consistency per request
[ https://issues.apache.org/jira/browse/HBASE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303372#comment-15303372 ] Hudson commented on HBASE-10358: FAILURE: Integrated in HBase-1.3 #717 (See [https://builds.apache.org/job/HBase-1.3/717/]) HBASE-10358 Shell changes for setting consistency per request (yi liang) (enis: rev 25e21ee196d18fa0490d386ed21eeea7a9ecfeb0) * hbase-shell/src/main/ruby/shell/commands/get.rb * hbase-shell/src/main/ruby/shell/commands/scan.rb * hbase-shell/src/main/ruby/shell/formatter.rb * hbase-shell/src/main/ruby/hbase/table.rb > Shell changes for setting consistency per request > - > > Key: HBASE-10358 > URL: https://issues.apache.org/jira/browse/HBASE-10358 > Project: HBase > Issue Type: New Feature > Components: shell >Reporter: Enis Soztutar >Assignee: yi liang > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: Screen Shot 2016-04-21 at 3.09.52 PM.png, Screen Shot > 2016-05-05 at 10.38.27 AM.png, shell.patch, shell4.patch, shell_3.patch > > > We can add shell support to set consistency per request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303352#comment-15303352 ] Hudson commented on HBASE-15854: FAILURE: Integrated in HBase-1.2 #637 (See [https://builds.apache.org/job/HBase-1.2/637/]) HBASE-15854 Log the cause of SASL connection failures (Robert Yokota) (apurtell: rev 52053cc90202d46fb28389e034d24db822ac5499) * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1530#comment-1530 ] Hudson commented on HBASE-15854: SUCCESS: Integrated in HBase-1.4 #180 (See [https://builds.apache.org/job/HBase-1.4/180/]) HBASE-15854 Log the cause of SASL connection failures (Robert Yokota) (apurtell: rev 22aa501436ba5f0b24a7c09b0fbbbff8c6289247) * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
[ https://issues.apache.org/jira/browse/HBASE-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303321#comment-15303321 ] Colin Ma commented on HBASE-15830: -- [~ghelmling], thanks for review, the patch is updated according to your comments. > Sasl encryption doesn't work with AsyncRpcChannelImpl > - > > Key: HBASE-15830 > URL: https://issues.apache.org/jira/browse/HBASE-15830 > Project: HBase > Issue Type: Bug >Reporter: Colin Ma > Attachments: HBASE-15830.001.patch, HBASE-15830.002.patch, > HBASE-15830.003.patch, HBASE-15830.004.patch > > > Currently, sasl encryption doesn't work with AsyncRpcChannelImpl, there has 3 > problems: > 1. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslClientHandler.java#L308] > will throw the following exception: > java.lang.UnsupportedOperationException: direct buffer > at > io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199) > at > org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:308) > 2. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java#L212] > has deadlocks problem. > 3. TestAsyncSecureIPC doesn't cover the sasl encryption test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
[ https://issues.apache.org/jira/browse/HBASE-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Ma updated HBASE-15830: - Attachment: HBASE-15830.004.patch > Sasl encryption doesn't work with AsyncRpcChannelImpl > - > > Key: HBASE-15830 > URL: https://issues.apache.org/jira/browse/HBASE-15830 > Project: HBase > Issue Type: Bug >Reporter: Colin Ma > Attachments: HBASE-15830.001.patch, HBASE-15830.002.patch, > HBASE-15830.003.patch, HBASE-15830.004.patch > > > Currently, sasl encryption doesn't work with AsyncRpcChannelImpl, there has 3 > problems: > 1. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslClientHandler.java#L308] > will throw the following exception: > java.lang.UnsupportedOperationException: direct buffer > at > io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199) > at > org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:308) > 2. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java#L212] > has deadlocks problem. > 3. TestAsyncSecureIPC doesn't cover the sasl encryption test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15600) Add provision for adding mutations to memstore or able to write to same region in batchMutate coprocessor hooks
[
https://issues.apache.org/jira/browse/HBASE-15600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303317#comment-15303317
]
Anoop Sam John commented on HBASE-15600:
Sorry if I was not clear abt the last comment
{code}
checkAndPrepareMutation(cpMutation, replay, cpFamilyMap, now);
3125
3126 // Acquire row locks. If not, the whole batch will fail.
3127 acquiredRowLocks.add(getRowLock(cpMutation.getRow(),
true));
{code}
checkRow() is done already in checkAndPrepareMutation(). getRowLock() is
going to do it again , instead if we use getRowLockInternal() that step is
avoided. Not a big deal, still better we can avoid 2 compare ops.
Can change on commit if you agree Enis. +1
> Add provision for adding mutations to memstore or able to write to same
> region in batchMutate coprocessor hooks
> ---
>
> Key: HBASE-15600
> URL: https://issues.apache.org/jira/browse/HBASE-15600
> Project: HBase
> Issue Type: Improvement
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
> Labels: phoenix
> Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.20
>
> Attachments: HBASE-15600.patch, HBASE-15600_v1.patch,
> HBASE-15600_v2.patch, hbase-15600_v3.patch, hbase-15600_v4.patch,
> hbase-15600_v5.patch, hbase-15600_v6.patch
>
>
> As part of PHOENIX-1734 we need to write the index updates to same region
> from coprocessors but writing from batchMutate API is not allowed because of
> mvcc.
> Raised PHOENIX-2742 to discuss any alternative way to write to the same
> region directly or not but not having any proper solution there.
> Currently we have provision to write wal edits from coprocessors. We can set
> wal edits in MiniBatchOperationInProgress.
> {noformat}
> /**
>* Sets the walEdit for the operation(Mutation) at the specified position.
>* @param index
>* @param walEdit
>*/
> public void setWalEdit(int index, WALEdit walEdit) {
> this.walEditsFromCoprocessors[getAbsoluteIndex(index)] = walEdit;
> }
> {noformat}
> Similarly we can allow to write mutations from coprocessors to memstore as
> well. Or else we should provide the batch mutation API allow write in batch
> mutate coprocessors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15861) Add support for table sets in restore operation
[ https://issues.apache.org/jira/browse/HBASE-15861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-15861: -- Description: We support backup operation for table set, but there is no support for restore operation for table set yet. > Add support for table sets in restore operation > --- > > Key: HBASE-15861 > URL: https://issues.apache.org/jira/browse/HBASE-15861 > Project: HBase > Issue Type: Task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-15861-v1.patch > > > We support backup operation for table set, but there is no support for > restore operation for table set yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15861) Add support for table sets in restore operation
[
https://issues.apache.org/jira/browse/HBASE-15861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303311#comment-15303311
]
Vladimir Rodionov commented on HBASE-15861:
---
Added the following command-line option to restore operation *restore [-set
set_name]*:
{code}
hbase restore [-set set_name] [tableMapping]
[-overwrite] [-check] [-automatic]
{code}
Now one can restore backup set by specifying backup set name. Restore can be
done to different table set, see [tableMapping] argument, if [tableMapping] is
missing, restores tables from backup set into the same tables.
> Add support for table sets in restore operation
> ---
>
> Key: HBASE-15861
> URL: https://issues.apache.org/jira/browse/HBASE-15861
> Project: HBase
> Issue Type: Task
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
> Attachments: HBASE-15861-v1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (HBASE-15862) Backup - Delete- Restore does not restore deleted data
[ https://issues.apache.org/jira/browse/HBASE-15862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-15862 started by Vladimir Rodionov. - > Backup - Delete- Restore does not restore deleted data > -- > > Key: HBASE-15862 > URL: https://issues.apache.org/jira/browse/HBASE-15862 > Project: HBase > Issue Type: Bug >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > > This was discovered during testing. If we delete row after full backup and > perform immediately restore, the deleted row still remains deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15897) Fix a wrong comment about QOS order
[
https://issues.apache.org/jira/browse/HBASE-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303304#comment-15303304
]
Hadoop QA commented on HBASE-15897:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
55s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 28s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 17s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
23s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
55s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 32s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 32s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
30s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
34m 13s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
18s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 29s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 8s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
11s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 48m 7s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806523/HBASE-15897.patch |
| JIRA Issue | HBASE-15897 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf900.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / b89d88a |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs |
[jira] [Commented] (HBASE-15861) Add support for table sets in restore operation
[ https://issues.apache.org/jira/browse/HBASE-15861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303302#comment-15303302 ] Ted Yu commented on HBASE-15861: Can you fill the description with some detail ? Will review tomorrow - reviewboard is preferred. > Add support for table sets in restore operation > --- > > Key: HBASE-15861 > URL: https://issues.apache.org/jira/browse/HBASE-15861 > Project: HBase > Issue Type: Task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-15861-v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15899) HBase incremental restore seems to have problems with namespaces
[ https://issues.apache.org/jira/browse/HBASE-15899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-15899: -- Description: HBase incremental restores seem to have problems with namespaces. As far as I can tell the incremental restore attempt to create invalid HDFS paths which leads to failure. > HBase incremental restore seems to have problems with namespaces > > > Key: HBASE-15899 > URL: https://issues.apache.org/jira/browse/HBASE-15899 > Project: HBase > Issue Type: Bug >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > > HBase incremental restores seem to have problems with namespaces. As far as I > can tell the incremental restore attempt to create invalid HDFS paths which > leads to failure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15861) Add support for table sets in restore operation
[ https://issues.apache.org/jira/browse/HBASE-15861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303298#comment-15303298 ] Vladimir Rodionov commented on HBASE-15861: --- [~te...@apache.org] can you take a look? > Add support for table sets in restore operation > --- > > Key: HBASE-15861 > URL: https://issues.apache.org/jira/browse/HBASE-15861 > Project: HBase > Issue Type: Task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-15861-v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15899) HBase incremental restore seems to have problems with namespaces
Vladimir Rodionov created HBASE-15899: - Summary: HBase incremental restore seems to have problems with namespaces Key: HBASE-15899 URL: https://issues.apache.org/jira/browse/HBASE-15899 Project: HBase Issue Type: Bug Reporter: Vladimir Rodionov Assignee: Vladimir Rodionov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15861) Add support for table sets in restore operation
[ https://issues.apache.org/jira/browse/HBASE-15861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-15861: -- Attachment: HBASE-15861-v1.patch v1 > Add support for table sets in restore operation > --- > > Key: HBASE-15861 > URL: https://issues.apache.org/jira/browse/HBASE-15861 > Project: HBase > Issue Type: Task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-15861-v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[
https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303289#comment-15303289
]
Hadoop QA commented on HBASE-15896:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} pylint {color} | {color:blue} 0m 4s
{color} | {color:blue} Pylint was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 17s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 26m 42s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806522/HBASE-15896_master_v3.patch
|
| JIRA Issue | HBASE-15896 |
| Optional Tests | asflicense pylint |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / b89d88a |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2031/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> Add timeout tests to flaky list from report-flakies.py
> --
>
> Key: HBASE-15896
> URL: https://issues.apache.org/jira/browse/HBASE-15896
> Project: HBase
> Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
> Attachments: HBASE-15896_master_v1.patch,
> HBASE-15896_master_v2.patch, HBASE-15896_master_v3.patch
>
>
> - Adds timed-out tests to flaky list. Dumpes two new files for reference,
> 'timeout' and 'failed' for corresponding list of bad tests.
> - Set --max-builds for different urls separately. This is needed so that we
> can turn the knobs for post-commit job and flaky-tests job separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15815) Region mover script sometimes reports stuck region where only one server was involved
[
https://issues.apache.org/jira/browse/HBASE-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-15815:
---
Fix Version/s: 0.98.20
> Region mover script sometimes reports stuck region where only one server was
> involved
> -
>
> Key: HBASE-15815
> URL: https://issues.apache.org/jira/browse/HBASE-15815
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.1.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 1.4.0, 0.98.20
>
> Attachments: 15815-branch-1.v1.txt, 15815-branch-1.v2.txt,
> HBASE-15815.branch-1.02.txt, HBASE-15815.branch-1.v2.txt
>
>
> Sometimes we saw the following in output from region mover script:
> {code}
> 2016-05-11 01:38:21,187||INFO|3969|140086696048384|MainThread|2016-05-11
> 01:38:21,186 INFO [RubyThread-7:
> /.../current/hbase-client/bin/thread-pool.rb:28-EventThread]
> zookeeper.ClientCnxn: EventThread shut down
> 2016-05-11 01:38:21,299||INFO|3969|140086696048384|MainThread|RuntimeError:
> Region stuck on hbase-5-2.osl,16020,1462930100540,,
> newserver=hbase-5-2.osl,16020,1462930100540
> {code}
> There was only one server involved.
> Since the name of region was not printed, it makes debugging hard to do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15808) Reduce potential bulk load intermediate space usage and waste
[ https://issues.apache.org/jira/browse/HBASE-15808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-15808: --- Fix Version/s: 0.98.20 > Reduce potential bulk load intermediate space usage and waste > - > > Key: HBASE-15808 > URL: https://issues.apache.org/jira/browse/HBASE-15808 > Project: HBase > Issue Type: Improvement >Affects Versions: 1.2.0 >Reporter: Jerry He >Assignee: Jerry He >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 0.98.20 > > Attachments: HBASE-15808-v2.patch, HBASE-15808-v3.patch, > HBASE-15808.patch > > > If the bulk load input files do not match the existing region boudaries, the > files will be splitted. > In the unfornate cases where the files need to be splitted multiple times, > the process can consume unnecessary space and can even cause out of space. > Here is over-simplified example. > Orinal size of input files: > consumed space: size --> 300GB > After a round of splits: > consumed space: size + tmpspace1 --> 300GB + 300GB > After another round of splits: > consumded space: size + tmpspace1 + tmpspace2 --> 300GB + 300GB + 300GB > .. > Currently we don't do any cleanup in the process. At least all the > intermediate tmpspace (not the last one) can be deleted in the process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15898) Document G1GC Recommendations
[ https://issues.apache.org/jira/browse/HBASE-15898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-15898: Status: Patch Available (was: Open) > Document G1GC Recommendations > - > > Key: HBASE-15898 > URL: https://issues.apache.org/jira/browse/HBASE-15898 > Project: HBase > Issue Type: Bug > Components: documentation, java >Affects Versions: 2.0.0 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-15898.patch > > > Document G1GC recommendations for HBase -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15898) Document G1GC Recommendations
[ https://issues.apache.org/jira/browse/HBASE-15898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-15898: Attachment: HBASE-15898.patch Ready for review. Thanks [~gkamat]! > Document G1GC Recommendations > - > > Key: HBASE-15898 > URL: https://issues.apache.org/jira/browse/HBASE-15898 > Project: HBase > Issue Type: Bug > Components: documentation, java >Affects Versions: 2.0.0 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-15898.patch > > > Document G1GC recommendations for HBase -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15898) Document G1GC Recommendations
Misty Stanley-Jones created HBASE-15898: --- Summary: Document G1GC Recommendations Key: HBASE-15898 URL: https://issues.apache.org/jira/browse/HBASE-15898 Project: HBase Issue Type: Bug Components: documentation, java Affects Versions: 2.0.0 Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Document G1GC recommendations for HBase -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15740) Replication source.shippedKBs metric is undercounting because it is in KB
[
https://issues.apache.org/jira/browse/HBASE-15740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-15740:
---
Fix Version/s: 0.98.20
> Replication source.shippedKBs metric is undercounting because it is in KB
> -
>
> Key: HBASE-15740
> URL: https://issues.apache.org/jira/browse/HBASE-15740
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.20
>
> Attachments: HBASE-15740-0.98.patch, hbase-15740_v1.patch,
> hbase-15740_v2.patch
>
>
> In a cluster where there is replication going on, I've noticed that this is
> always 0:
> {code}
> "source.shippedKBs" : 0,
> {code}
> Looking at the source reveals why:
> {code}
> metrics.shipBatch(currentNbOperations, currentSize / 1024,
> currentNbHFiles);
> {code}
> It is always undercounting because we discard remaining bytes after KB
> boundary. This is specially a problem when we are always shipping small
> batches <1KB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15740) Replication source.shippedKBs metric is undercounting because it is in KB
[
https://issues.apache.org/jira/browse/HBASE-15740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-15740:
---
Attachment: HBASE-15740-0.98.patch
Patch for 0.98
> Replication source.shippedKBs metric is undercounting because it is in KB
> -
>
> Key: HBASE-15740
> URL: https://issues.apache.org/jira/browse/HBASE-15740
> Project: HBase
> Issue Type: Sub-task
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.20
>
> Attachments: HBASE-15740-0.98.patch, hbase-15740_v1.patch,
> hbase-15740_v2.patch
>
>
> In a cluster where there is replication going on, I've noticed that this is
> always 0:
> {code}
> "source.shippedKBs" : 0,
> {code}
> Looking at the source reveals why:
> {code}
> metrics.shipBatch(currentNbOperations, currentSize / 1024,
> currentNbHFiles);
> {code}
> It is always undercounting because we discard remaining bytes after KB
> boundary. This is specially a problem when we are always shipping small
> batches <1KB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15897) Fix a wrong comment about QOS order
[
https://issues.apache.org/jira/browse/HBASE-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Youngjoon Kim updated HBASE-15897:
--
Status: Patch Available (was: Open)
> Fix a wrong comment about QOS order
> ---
>
> Key: HBASE-15897
> URL: https://issues.apache.org/jira/browse/HBASE-15897
> Project: HBase
> Issue Type: Bug
>Reporter: Youngjoon Kim
>Priority: Trivial
> Attachments: HBASE-15897.patch
>
>
> The following comment is wrong.
> It should be 'normal_QOS < replication_QOS < replay_QOS < QOS_threshold <
> admin_QOS < high_QOS'
> {code:title=hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java}
> // normal_QOS < QOS_threshold < replication_QOS < replay_QOS < admin_QOS <
> high_QOS
> public static final int NORMAL_QOS = 0;
> public static final int QOS_THRESHOLD = 10;
> public static final int HIGH_QOS = 200;
> public static final int REPLICATION_QOS = 5;
> public static final int REPLAY_QOS = 6;
> public static final int ADMIN_QOS = 100;
> public static final int SYSTEMTABLE_QOS = HIGH_QOS;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15897) Fix a wrong comment about QOS order
[
https://issues.apache.org/jira/browse/HBASE-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Youngjoon Kim updated HBASE-15897:
--
Attachment: HBASE-15897.patch
Attach a patch
> Fix a wrong comment about QOS order
> ---
>
> Key: HBASE-15897
> URL: https://issues.apache.org/jira/browse/HBASE-15897
> Project: HBase
> Issue Type: Bug
>Reporter: Youngjoon Kim
>Priority: Trivial
> Attachments: HBASE-15897.patch
>
>
> The following comment is wrong.
> It should be 'normal_QOS < replication_QOS < replay_QOS < QOS_threshold <
> admin_QOS < high_QOS'
> {code:title=hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java}
> // normal_QOS < QOS_threshold < replication_QOS < replay_QOS < admin_QOS <
> high_QOS
> public static final int NORMAL_QOS = 0;
> public static final int QOS_THRESHOLD = 10;
> public static final int HIGH_QOS = 200;
> public static final int REPLICATION_QOS = 5;
> public static final int REPLAY_QOS = 6;
> public static final int ADMIN_QOS = 100;
> public static final int SYSTEMTABLE_QOS = HIGH_QOS;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[ https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-15896: - Attachment: HBASE-15896_master_v3.patch > Add timeout tests to flaky list from report-flakies.py > -- > > Key: HBASE-15896 > URL: https://issues.apache.org/jira/browse/HBASE-15896 > Project: HBase > Issue Type: Sub-task >Reporter: Appy >Assignee: Appy > Attachments: HBASE-15896_master_v1.patch, > HBASE-15896_master_v2.patch, HBASE-15896_master_v3.patch > > > - Adds timed-out tests to flaky list. Dumpes two new files for reference, > 'timeout' and 'failed' for corresponding list of bad tests. > - Set --max-builds for different urls separately. This is needed so that we > can turn the knobs for post-commit job and flaky-tests job separately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15897) Fix a wrong comment about QOS order
Youngjoon Kim created HBASE-15897:
-
Summary: Fix a wrong comment about QOS order
Key: HBASE-15897
URL: https://issues.apache.org/jira/browse/HBASE-15897
Project: HBase
Issue Type: Bug
Reporter: Youngjoon Kim
Priority: Trivial
The following comment is wrong.
It should be 'normal_QOS < replication_QOS < replay_QOS < QOS_threshold <
admin_QOS < high_QOS'
{code:title=hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java}
// normal_QOS < QOS_threshold < replication_QOS < replay_QOS < admin_QOS <
high_QOS
public static final int NORMAL_QOS = 0;
public static final int QOS_THRESHOLD = 10;
public static final int HIGH_QOS = 200;
public static final int REPLICATION_QOS = 5;
public static final int REPLAY_QOS = 6;
public static final int ADMIN_QOS = 100;
public static final int SYSTEMTABLE_QOS = HIGH_QOS;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-10358) Shell changes for setting consistency per request
[ https://issues.apache.org/jira/browse/HBASE-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10358: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 1.4.0 1.3.0 Status: Resolved (was: Patch Available) Committed to 1.3+. Thanks [~easyliangjob] for the patch! > Shell changes for setting consistency per request > - > > Key: HBASE-10358 > URL: https://issues.apache.org/jira/browse/HBASE-10358 > Project: HBase > Issue Type: New Feature > Components: shell >Reporter: Enis Soztutar >Assignee: yi liang > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: Screen Shot 2016-04-21 at 3.09.52 PM.png, Screen Shot > 2016-05-05 at 10.38.27 AM.png, shell.patch, shell4.patch, shell_3.patch > > > We can add shell support to set consistency per request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15600) Add provision for adding mutations to memstore or able to write to same region in batchMutate coprocessor hooks
[
https://issues.apache.org/jira/browse/HBASE-15600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303218#comment-15303218
]
Enis Soztutar commented on HBASE-15600:
---
[~anoop.hbase], [~ramkrishna.s.vasude...@gmail.com] any more comments on v6?
I've talked to [~chrajeshbab...@gmail.com] offline, and he has a patch in
Phoenix to do the corresponding changes in local index code. So it seems that
we can go ahead with this patch.
> Add provision for adding mutations to memstore or able to write to same
> region in batchMutate coprocessor hooks
> ---
>
> Key: HBASE-15600
> URL: https://issues.apache.org/jira/browse/HBASE-15600
> Project: HBase
> Issue Type: Improvement
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
> Labels: phoenix
> Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.20
>
> Attachments: HBASE-15600.patch, HBASE-15600_v1.patch,
> HBASE-15600_v2.patch, hbase-15600_v3.patch, hbase-15600_v4.patch,
> hbase-15600_v5.patch, hbase-15600_v6.patch
>
>
> As part of PHOENIX-1734 we need to write the index updates to same region
> from coprocessors but writing from batchMutate API is not allowed because of
> mvcc.
> Raised PHOENIX-2742 to discuss any alternative way to write to the same
> region directly or not but not having any proper solution there.
> Currently we have provision to write wal edits from coprocessors. We can set
> wal edits in MiniBatchOperationInProgress.
> {noformat}
> /**
>* Sets the walEdit for the operation(Mutation) at the specified position.
>* @param index
>* @param walEdit
>*/
> public void setWalEdit(int index, WALEdit walEdit) {
> this.walEditsFromCoprocessors[getAbsoluteIndex(index)] = walEdit;
> }
> {noformat}
> Similarly we can allow to write mutations from coprocessors to memstore as
> well. Or else we should provide the batch mutation API allow write in batch
> mutate coprocessors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303214#comment-15303214 ] Hudson commented on HBASE-15837: FAILURE: Integrated in HBase-1.1-JDK7 #1723 (See [https://builds.apache.org/job/HBase-1.1-JDK7/1723/]) HBASE-15837 Memstore size accounting is wrong if postBatchMutate() (enis: rev fd818514c7f663e673febb016a774790b0b2e457) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303213#comment-15303213 ] Hudson commented on HBASE-15854: FAILURE: Integrated in HBase-1.1-JDK7 #1723 (See [https://builds.apache.org/job/HBase-1.1-JDK7/1723/]) HBASE-15854 Log the cause of SASL connection failures (Robert Yokota) (apurtell: rev 608259fbb1b803e740acb166cb6a86d7d54524bf) * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15895) remove unmaintained jenkins build analysis tool.
[
https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303208#comment-15303208
]
Hadoop QA commented on HBASE-15895:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 3s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
17s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 4s
{color} | {color:red} jenkins-tools in master failed with JDK v1.8.0. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 5s
{color} | {color:red} buildstats in master failed with JDK v1.8.0. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 3s
{color} | {color:red} jenkins-tools in master failed with JDK v1.7.0_79.
{color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 4s
{color} | {color:red} buildstats in master failed with JDK v1.7.0_79. {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
8s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} mvneclipse {color} | {color:red} 0m 4s
{color} | {color:red} jenkins-tools in master failed. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 0s
{color} | {color:blue} Skipped branch modules with no Java source:
dev-support/jenkins-tools {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 5s
{color} | {color:red} buildstats in master failed. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 4s
{color} | {color:red} jenkins-tools in master failed with JDK v1.8.0. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 8s
{color} | {color:red} buildstats in master failed with JDK v1.8.0. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 4s
{color} | {color:red} jenkins-tools in master failed with JDK v1.7.0_79.
{color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 6s
{color} | {color:red} buildstats in master failed with JDK v1.7.0_79. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
55s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 44s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 6m 14s {color}
| {color:red} root-jdk1.8.0 with JDK v1.8.0 generated 32 new + 0 unchanged - 0
fixed = 32 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 44s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 27s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 8m 41s {color}
| {color:red} root-jdk1.7.0_79 with JDK v1.7.0_79 generated 32 new + 0
unchanged - 0 fixed = 32 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 27s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
51s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
0s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 0s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 8m
53s {color} | {color:green} Patch does not cause any errors with Hadoop 2.4.1
2.5.2 2.6.0. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 0s
{color} | {color:blue} Skipped patch
[jira] [Commented] (HBASE-15790) Force "hbase" ownership on bulkload
[ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303197#comment-15303197 ] Matteo Bertozzi commented on HBASE-15790: - there are so many combinations where you can have bulk load succeed. the simples way if you want to try is have files owned by a user and then have hdfs call bulkload. file will be moved without problems and the permission will be the wrong one > Force "hbase" ownership on bulkload > --- > > Key: HBASE-15790 > URL: https://issues.apache.org/jira/browse/HBASE-15790 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 2.0.0, 1.2.1, 1.1.4, 0.98.19 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Minor > Attachments: HBASE-15790-v0.patch, HBASE-15790-v1.patch, > HBASE-15790-v2.patch, HBASE-15790-v3.patch > > > When a user different than "hbase" bulkload files, in general we end up with > files owned by a user different than hbase. sometimes this causes problems > with hbase not be able to move files around archiving/deleting. > A simple solution is probably to change the ownership of the files to "hbase" > during bulkload. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15790) Force "hbase" ownership on bulkload
[ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303181#comment-15303181 ] Jerry He commented on HBASE-15790: -- Hmm. Then how could the files be moved into hbase by bulk load? Would the bulk load fail in this case? If it is rename, hbase needs write permission on the files. If it is copy, hbase needs read, but then copy does change the owner. > Force "hbase" ownership on bulkload > --- > > Key: HBASE-15790 > URL: https://issues.apache.org/jira/browse/HBASE-15790 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 2.0.0, 1.2.1, 1.1.4, 0.98.19 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Minor > Attachments: HBASE-15790-v0.patch, HBASE-15790-v1.patch, > HBASE-15790-v2.patch, HBASE-15790-v3.patch > > > When a user different than "hbase" bulkload files, in general we end up with > files owned by a user different than hbase. sometimes this causes problems > with hbase not be able to move files around archiving/deleting. > A simple solution is probably to change the ownership of the files to "hbase" > during bulkload. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303177#comment-15303177 ] Hudson commented on HBASE-15837: SUCCESS: Integrated in HBase-1.1-JDK8 #1809 (See [https://builds.apache.org/job/HBase-1.1-JDK8/1809/]) HBASE-15837 Memstore size accounting is wrong if postBatchMutate() (enis: rev fd818514c7f663e673febb016a774790b0b2e457) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303172#comment-15303172 ] Hudson commented on HBASE-15854: SUCCESS: Integrated in HBase-1.2-IT #519 (See [https://builds.apache.org/job/HBase-1.2-IT/519/]) HBASE-15854 Log the cause of SASL connection failures (Robert Yokota) (apurtell: rev 52053cc90202d46fb28389e034d24db822ac5499) * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15879) Introduce Key interface
[
https://issues.apache.org/jira/browse/HBASE-15879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303163#comment-15303163
]
ramkrishna.s.vasudevan commented on HBASE-15879:
bq.Shouldn't fact that a Key implementation is made of contiguous bytes be an
implementation detail?
The thought was to have something like a Key Interface. But as we are saying it
is always easy to form a Key from a given cell what ever is the format of the
Cell. The intention here was to say that some of the Cell impls are trying to
have its key in a continuous structure and let those cells have this interface.
Because once we say Key then it means indirectly every Cell is also a Key.
bq.public class KeyValue implements Cell, HeapSize, Cloneable,
SettableSequenceId, SettableTimestamp, Streamable, ContiguousKey {
Remove them as part of this JIRA? Not very sure. Streamable interface tries to
again make use of the fact that things that are contiguous can be written at a
single shot rather than splitting them and writing them. SettableSequenceId and
SettableTimeStamp can be merged is one thing that is possible.
> Introduce Key interface
> ---
>
> Key: HBASE-15879
> URL: https://issues.apache.org/jira/browse/HBASE-15879
> Project: HBase
> Issue Type: Improvement
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
> Attachments: HBASE-15879.patch
>
>
> Introduce an interface called Key and allow Cell implementations to implement
> this Key interface for cases like KeyValue, OffheapKeyValue and DBE cells
> (Except prefix tree) so that we can avoid copies when we deal with only Cells
> in case of block index creations (like ROOT, Bloom etc). Helps in reduction
> of garbage also.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[
https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303162#comment-15303162
]
Hadoop QA commented on HBASE-15896:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} pylint {color} | {color:blue} 0m 5s
{color} | {color:blue} Pylint was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
27m 35s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
18s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 28m 11s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806506/HBASE-15896_master_v2.patch
|
| JIRA Issue | HBASE-15896 |
| Optional Tests | asflicense pylint |
| uname | Linux penates.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / fdaf3be |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2029/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> Add timeout tests to flaky list from report-flakies.py
> --
>
> Key: HBASE-15896
> URL: https://issues.apache.org/jira/browse/HBASE-15896
> Project: HBase
> Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
> Attachments: HBASE-15896_master_v1.patch, HBASE-15896_master_v2.patch
>
>
> - Adds timed-out tests to flaky list. Dumpes two new files for reference,
> 'timeout' and 'failed' for corresponding list of bad tests.
> - Set --max-builds for different urls separately. This is needed so that we
> can turn the knobs for post-commit job and flaky-tests job separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15292) Refined ZooKeeperWatcher to prevent ZooKeeper's callback while construction
[ https://issues.apache.org/jira/browse/HBASE-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-15292: --- Fix Version/s: 0.98.20 > Refined ZooKeeperWatcher to prevent ZooKeeper's callback while construction > --- > > Key: HBASE-15292 > URL: https://issues.apache.org/jira/browse/HBASE-15292 > Project: HBase > Issue Type: Bug > Components: Zookeeper >Reporter: Hiroshi Ikeda >Assignee: Hiroshi Ikeda >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.20 > > Attachments: HBASE-15292-V2.patch, HBASE-15292-V3.patch, > HBASE-15292-V4.patch, HBASE-15292-V5.patch, HBASE-15292.patch > > > The existing code is not just messy but also contains a subtle bug of > visibility due to missing synchronization between threads. > The root of the evil is that ZooKeeper uses a silly anti-pattern, starting a > thread within its constructor, and in practice all the developers are not > allowed to use ZooKeeper correctly without tedious code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15842) SnapshotInfo should display ownership information
[
https://issues.apache.org/jira/browse/HBASE-15842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-15842:
---
Fix Version/s: (was: 0.98.20)
> SnapshotInfo should display ownership information
> -
>
> Key: HBASE-15842
> URL: https://issues.apache.org/jira/browse/HBASE-15842
> Project: HBase
> Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 15842.v1.txt, 15842.v1.txt
>
>
> Currently SnapshotInfo doesn't show snapshot owner:
> {code}
> hbase org.apache.hadoop.hbase.snapshot.SnapshotInfo -snapshot
> snapshot_table_qm0uxvk19x -stats -schema
> ...
> Snapshot Info
>
>Name: snapshot_table_qm0uxvk19x
>Type: FLUSH
> Table: table_qm0uxvk19x
> Format: 2
> Created: 2016-05-16T20:54:08
> ...
> {code}
> This JIRA is to add ownership information to the display.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303156#comment-15303156 ] Hudson commented on HBASE-15837: FAILURE: Integrated in HBase-Trunk_matrix #950 (See [https://builds.apache.org/job/HBase-Trunk_matrix/950/]) HBASE-15837 Memstore size accounting is wrong if postBatchMutate() (enis: rev 43d1a999fe40ca5fd24fe57a189b10b9acfbbd30) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[
https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303146#comment-15303146
]
Hadoop QA commented on HBASE-15896:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} pylint {color} | {color:blue} 0m 3s
{color} | {color:blue} Pylint was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
33m 13s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
56s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 36m 43s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806489/HBASE-15896_master_v1.patch
|
| JIRA Issue | HBASE-15896 |
| Optional Tests | asflicense pylint |
| uname | Linux asf908.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / fdaf3be |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2028/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> Add timeout tests to flaky list from report-flakies.py
> --
>
> Key: HBASE-15896
> URL: https://issues.apache.org/jira/browse/HBASE-15896
> Project: HBase
> Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
> Attachments: HBASE-15896_master_v1.patch, HBASE-15896_master_v2.patch
>
>
> - Adds timed-out tests to flaky list. Dumpes two new files for reference,
> 'timeout' and 'failed' for corresponding list of bad tests.
> - Set --max-builds for different urls separately. This is needed so that we
> can turn the knobs for post-commit job and flaky-tests job separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15790) Force "hbase" ownership on bulkload
[ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303145#comment-15303145 ] Matteo Bertozzi commented on HBASE-15790: - the problem we have is that people does not use SecureBulkLoad and just bulkload the files as normal users. but the files may be owned by foo with permission rw- and those file will be moved into hbase. and hbase explodes when it tries to move the files away for example after a compaction. > Force "hbase" ownership on bulkload > --- > > Key: HBASE-15790 > URL: https://issues.apache.org/jira/browse/HBASE-15790 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 2.0.0, 1.2.1, 1.1.4, 0.98.19 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Minor > Attachments: HBASE-15790-v0.patch, HBASE-15790-v1.patch, > HBASE-15790-v2.patch, HBASE-15790-v3.patch > > > When a user different than "hbase" bulkload files, in general we end up with > files owned by a user different than hbase. sometimes this causes problems > with hbase not be able to move files around archiving/deleting. > A simple solution is probably to change the ownership of the files to "hbase" > during bulkload. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15790) Force "hbase" ownership on bulkload
[ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303139#comment-15303139 ] Jerry He commented on HBASE-15790: -- Could you give a specific example of the problem on the permissions from hbase bulk load. Yes. The SecureBulkLoad is the way to go. I have a JIRA to get it unified and be default HBASE-13701. I think I should start working on it ... > Force "hbase" ownership on bulkload > --- > > Key: HBASE-15790 > URL: https://issues.apache.org/jira/browse/HBASE-15790 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 2.0.0, 1.2.1, 1.1.4, 0.98.19 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Minor > Attachments: HBASE-15790-v0.patch, HBASE-15790-v1.patch, > HBASE-15790-v2.patch, HBASE-15790-v3.patch > > > When a user different than "hbase" bulkload files, in general we end up with > files owned by a user different than hbase. sometimes this causes problems > with hbase not be able to move files around archiving/deleting. > A simple solution is probably to change the ownership of the files to "hbase" > during bulkload. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15842) SnapshotInfo should display ownership information
[
https://issues.apache.org/jira/browse/HBASE-15842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-15842:
---
Fix Version/s: 0.98.20
> SnapshotInfo should display ownership information
> -
>
> Key: HBASE-15842
> URL: https://issues.apache.org/jira/browse/HBASE-15842
> Project: HBase
> Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 2.0.0, 1.4.0, 0.98.20
>
> Attachments: 15842.v1.txt, 15842.v1.txt
>
>
> Currently SnapshotInfo doesn't show snapshot owner:
> {code}
> hbase org.apache.hadoop.hbase.snapshot.SnapshotInfo -snapshot
> snapshot_table_qm0uxvk19x -stats -schema
> ...
> Snapshot Info
>
>Name: snapshot_table_qm0uxvk19x
>Type: FLUSH
> Table: table_qm0uxvk19x
> Format: 2
> Created: 2016-05-16T20:54:08
> ...
> {code}
> This JIRA is to add ownership information to the display.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15858) Some region server group shell commands don't work
[
https://issues.apache.org/jira/browse/HBASE-15858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-15858:
---
Status: Open (was: Patch Available)
> Some region server group shell commands don't work
> --
>
> Key: HBASE-15858
> URL: https://issues.apache.org/jira/browse/HBASE-15858
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
> Attachments: 15858.v1.patch, 15858.v2.patch
>
>
> [~cartershanklin] reported the following:
> {code}
> hbase(main):021:0> get_rsgroup 'test_group'
> GROUP INFORMATION
> ERROR: undefined local variable or method `group_admin' for
> #
> Here is some help for this command:
> Get a region server group's information.
> Example:
> hbase> get_rsgroup 'default'
> {code}
> {code}
> hbase(main):009:0> get_server_rsgroup
> 'hdp250-hbase-unsecure.example.com:16030'
> ERROR: undefined method `getGroupOfServer' for
> #
> Here is some help for this command:
> Get the group name the given region server is a member of.
> hbase> get_server_rsgroup 'server1:port1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15841) Performance Evaluation tool total rows may not be set correctly
[ https://issues.apache.org/jira/browse/HBASE-15841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-15841: --- Fix Version/s: 0.98.20 > Performance Evaluation tool total rows may not be set correctly > --- > > Key: HBASE-15841 > URL: https://issues.apache.org/jira/browse/HBASE-15841 > Project: HBase > Issue Type: Bug >Reporter: Jerry He >Assignee: Jerry He >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 0.98.20 > > Attachments: HBASE-15841-branch-1-v2.patch, > HBASE-15841-branch-1.patch, HBASE-15841-master-v2.patch, > HBASE-15841-master.patch > > > Carried my comment on HBASE-15403 to here: > Recently when I ran PerformanceEvaluation, I did notice some problem with the > number of rows. > hbase org.apache.hadoop.hbase.PerformanceEvaluation --table=TestTable1 > randomWrite 1 > hbase org.apache.hadoop.hbase.PerformanceEvaluation --table=TestTable5 > randomWrite 5 > hbase org.apache.hadoop.hbase.PerformanceEvaluation --table=TestTable10 > randomWrite 10 > hbase org.apache.hadoop.hbase.PerformanceEvaluation --table=TestTable10 > randomWrite 20 > All produced similar number of rows, and on the file system, they look like > in similar size as well: > hadoop fs -du -h /apps/hbase/data/data/default > 786.5 M /apps/hbase/data/data/default/TestTable1 > 786.0 M /apps/hbase/data/data/default/TestTable10 > 782.0 M /apps/hbase/data/data/default/TestTable20 > 713.4 M /apps/hbase/data/data/default/TestTable5 > HBase is 1.2.0. Looks like a regression somewhere. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14738) Backport HBASE-11927 (Use Native Hadoop Library for HFile checksum) to 0.98
[ https://issues.apache.org/jira/browse/HBASE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14738: --- Assignee: (was: Andrew Purtell) > Backport HBASE-11927 (Use Native Hadoop Library for HFile checksum) to 0.98 > --- > > Key: HBASE-14738 > URL: https://issues.apache.org/jira/browse/HBASE-14738 > Project: HBase > Issue Type: Task >Reporter: Andrew Purtell > Attachments: HBASE-14738-0.98.patch > > > Profiling 0.98.15 I see 20-30% of CPU time spent in Hadoop's PureJavaCrc32. > Not surprising given previous results described on HBASE-11927. Backport. > There are two issues with the backport: > # The patch on 11927 changes the default CRC type from CRC32 to CRC32C. > Although the changes are backwards compatible -files with either CRC type > will be handled correctly in a transparent manner - we should probably leave > the default alone in 0.98 and advise users on a site configuration change to > use CRC32C if desired, for potential hardware acceleration. > # Need a shim for differences between Hadoop's DataChecksum type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-15847: --- Fix Version/s: 0.98.20 > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > Fix For: 2.0.0, 1.4.0, 0.98.20 > > Attachments: HBASE-15847-0.98.patch, HBASE-15847-branch-1.patch, > HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[ https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-15896: - Attachment: HBASE-15896_master_v2.patch > Add timeout tests to flaky list from report-flakies.py > -- > > Key: HBASE-15896 > URL: https://issues.apache.org/jira/browse/HBASE-15896 > Project: HBase > Issue Type: Sub-task >Reporter: Appy >Assignee: Appy > Attachments: HBASE-15896_master_v1.patch, HBASE-15896_master_v2.patch > > > - Adds timed-out tests to flaky list. Dumpes two new files for reference, > 'timeout' and 'failed' for corresponding list of bad tests. > - Set --max-builds for different urls separately. This is needed so that we > can turn the knobs for post-commit job and flaky-tests job separately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303112#comment-15303112 ] Hudson commented on HBASE-15854: SUCCESS: Integrated in HBase-1.3-IT #681 (See [https://builds.apache.org/job/HBase-1.3-IT/681/]) HBASE-15854 Log the cause of SASL connection failures (Robert Yokota) (apurtell: rev b1e498e77097920990561071e02ff2afd9852161) * hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15580) Tag coprocessor limitedprivate scope to StoreFile.Reader
[
https://issues.apache.org/jira/browse/HBASE-15580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303096#comment-15303096
]
Andrew Purtell commented on HBASE-15580:
Needs updating for master [~ndimiduk], this is currently stale
> Tag coprocessor limitedprivate scope to StoreFile.Reader
>
>
> Key: HBASE-15580
> URL: https://issues.apache.org/jira/browse/HBASE-15580
> Project: HBase
> Issue Type: Improvement
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
> Fix For: 2.0.0, 1.0.4, 1.2.2, 0.98.20, 1.1.6
>
> Attachments: HBASE-15580.patch, HBASE-15580_branch-1.0.patch
>
>
> For phoenix local indexing we need to have custom storefile reader
> constructor(IndexHalfStoreFileReader) to distinguish from other storefile
> readers. So wanted to mark StoreFile.Reader scope as
> InterfaceAudience.LimitedPrivate("Coprocessor")
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[
https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303090#comment-15303090
]
Hadoop QA commented on HBASE-15896:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} pylint {color} | {color:blue} 0m 4s
{color} | {color:blue} Pylint was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 8m
33s {color} | {color:green} Patch does not cause any errors with Hadoop 2.4.1
2.5.2 2.6.0. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
12s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 8m 54s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806489/HBASE-15896_master_v1.patch
|
| JIRA Issue | HBASE-15896 |
| Optional Tests | asflicense pylint |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/yetus-0.2.1/lib/precommit/personality/hbase.sh
|
| git revision | master / fdaf3be |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2027/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> Add timeout tests to flaky list from report-flakies.py
> --
>
> Key: HBASE-15896
> URL: https://issues.apache.org/jira/browse/HBASE-15896
> Project: HBase
> Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
> Attachments: HBASE-15896_master_v1.patch
>
>
> - Adds timed-out tests to flaky list. Dumpes two new files for reference,
> 'timeout' and 'failed' for corresponding list of bad tests.
> - Set --max-builds for different urls separately. This is needed so that we
> can turn the knobs for post-commit job and flaky-tests job separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15887) Report Log Additions and Removals in Builds
[ https://issues.apache.org/jira/browse/HBASE-15887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clay B. updated HBASE-15887: Description: It would be very nice for the Apache Yetus verifications of HBase patches to report log item addition and deletions. This is not my idea but [~mbm] asked if we could modify the personality for reporting log additions and removals yesterday at an [HBase meetup at Splice machine|http://www.meetup.com/hbaseusergroup/events/230547750/] as [~aw] presented Apache Yetus for building HBase. was: It would be very nice for the Apache Yetus verifications of HBase patches to report log item addition and deletions. This is not my idea but Matthew Byng-Maddick asked if we could modify the personality for reporting log additions and removals yesterday at an [HBase meetup at Splice machine|http://www.meetup.com/hbaseusergroup/events/230547750/] as Allen Wittenauer presented Apache Yetus for building HBase. > Report Log Additions and Removals in Builds > --- > > Key: HBASE-15887 > URL: https://issues.apache.org/jira/browse/HBASE-15887 > Project: HBase > Issue Type: New Feature > Components: build >Reporter: Clay B. >Priority: Trivial > Attachments: HBASE-15887-v1.txt > > > It would be very nice for the Apache Yetus verifications of HBase patches to > report log item addition and deletions. > This is not my idea but [~mbm] asked if we could modify the personality for > reporting log additions and removals yesterday at an [HBase meetup at Splice > machine|http://www.meetup.com/hbaseusergroup/events/230547750/] as [~aw] > presented Apache Yetus for building HBase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-12733) High volume of "Couldn't find oldest seqNum" warnings if bypassing WAL
[
https://issues.apache.org/jira/browse/HBASE-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-12733.
---
Resolution: Won't Fix
Resolving won't fix. Old issue in a location that has undergone a bunch of
refactoring since original filed. If someone has later evidence, lets reopen.
> High volume of "Couldn't find oldest seqNum" warnings if bypassing WAL
> --
>
> Key: HBASE-12733
> URL: https://issues.apache.org/jira/browse/HBASE-12733
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Priority: Minor
> Labels: beginner
>
> When ingesting with the WAL bypassed, the RegionServer will log the following
> at every flush:
> {noformat}
> 2014-12-19 16:58:24,630 WARN [MemStoreFlusher.0] wal.FSHLog: Couldn't find
> oldest seqNum for the region we are about to flush:
> [86fc8c1374ebc29cc4a39a78966d48e0]
> {noformat}
> The WAL won't find a seqnum for the region until the first edit which does
> not bypass the WAL. That might not be for hundreds or thousands of flushes.
> This shouldn't be at WARN level since ingest with WAL bypass is legal if a
> bit unusual. It's concerning that the FSHLog code that emits that warning has
> a TODO above suggesting the warning should instead be an assertion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303069#comment-15303069 ] Hudson commented on HBASE-15837: FAILURE: Integrated in HBase-1.3 #716 (See [https://builds.apache.org/job/HBase-1.3/716/]) HBASE-15837 Memstore size accounting is wrong if postBatchMutate() (enis: rev ef72646b595cc2d3a69601cccf8df509d5a60fa5) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303053#comment-15303053 ] Hudson commented on HBASE-15837: FAILURE: Integrated in HBase-1.2 #636 (See [https://builds.apache.org/job/HBase-1.2/636/]) HBASE-15837 Memstore size accounting is wrong if postBatchMutate() (enis: rev bd6903b9e7bd7707a0c03f30f089b1d31f700411) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[
https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303046#comment-15303046
]
Hadoop QA commented on HBASE-15896:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} pylint {color} | {color:blue} 0m 3s
{color} | {color:blue} Pylint was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 8m
55s {color} | {color:green} Patch does not cause any errors with Hadoop 2.4.1
2.5.2 2.6.0. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 9m 22s {color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12806489/HBASE-15896_master_v1.patch
|
| JIRA Issue | HBASE-15896 |
| Optional Tests | asflicense pylint |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/yetus-0.2.1/lib/precommit/personality/hbase.sh
|
| git revision | master / fdaf3be |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2025/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> Add timeout tests to flaky list from report-flakies.py
> --
>
> Key: HBASE-15896
> URL: https://issues.apache.org/jira/browse/HBASE-15896
> Project: HBase
> Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
> Attachments: HBASE-15896_master_v1.patch
>
>
> - Adds timed-out tests to flaky list. Dumpes two new files for reference,
> 'timeout' and 'failed' for corresponding list of bad tests.
> - Set --max-builds for different urls separately. This is needed so that we
> can turn the knobs for post-commit job and flaky-tests job separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15895) remove unmaintained jenkins build analysis tool.
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303021#comment-15303021 ] Appy commented on HBASE-15895: -- +1 > remove unmaintained jenkins build analysis tool. > > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Minor > Attachments: HBASE-15895.1.patch > > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303020#comment-15303020 ] Hudson commented on HBASE-15837: SUCCESS: Integrated in HBase-1.4 #179 (See [https://builds.apache.org/job/HBase-1.4/179/]) HBASE-15837 Memstore size accounting is wrong if postBatchMutate() (enis: rev 02a641e2b103d075a60192c0bdb221fc93575df6) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[ https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-15896: - Attachment: HBASE-15896_master_v1.patch > Add timeout tests to flaky list from report-flakies.py > -- > > Key: HBASE-15896 > URL: https://issues.apache.org/jira/browse/HBASE-15896 > Project: HBase > Issue Type: Sub-task >Reporter: Appy >Assignee: Appy > Attachments: HBASE-15896_master_v1.patch > > > - Adds timed-out tests to flaky list. Dumpes two new files for reference, > 'timeout' and 'failed' for corresponding list of bad tests. > - Set --max-builds for different urls separately. This is needed so that we > can turn the knobs for post-commit job and flaky-tests job separately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[ https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-15896: - Status: Patch Available (was: Open) > Add timeout tests to flaky list from report-flakies.py > -- > > Key: HBASE-15896 > URL: https://issues.apache.org/jira/browse/HBASE-15896 > Project: HBase > Issue Type: Sub-task >Reporter: Appy >Assignee: Appy > Attachments: HBASE-15896_master_v1.patch > > > - Adds timed-out tests to flaky list. Dumpes two new files for reference, > 'timeout' and 'failed' for corresponding list of bad tests. > - Set --max-builds for different urls separately. This is needed so that we > can turn the knobs for post-commit job and flaky-tests job separately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
[ https://issues.apache.org/jira/browse/HBASE-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-15896: - Issue Type: Sub-task (was: Improvement) Parent: HBASE-15839 > Add timeout tests to flaky list from report-flakies.py > -- > > Key: HBASE-15896 > URL: https://issues.apache.org/jira/browse/HBASE-15896 > Project: HBase > Issue Type: Sub-task >Reporter: Appy >Assignee: Appy > > - Adds timed-out tests to flaky list. Dumpes two new files for reference, > 'timeout' and 'failed' for corresponding list of bad tests. > - Set --max-builds for different urls separately. This is needed so that we > can turn the knobs for post-commit job and flaky-tests job separately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
[ https://issues.apache.org/jira/browse/HBASE-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Helmling updated HBASE-15830: -- Status: Open (was: Patch Available) > Sasl encryption doesn't work with AsyncRpcChannelImpl > - > > Key: HBASE-15830 > URL: https://issues.apache.org/jira/browse/HBASE-15830 > Project: HBase > Issue Type: Bug >Reporter: Colin Ma > Attachments: HBASE-15830.001.patch, HBASE-15830.002.patch, > HBASE-15830.003.patch > > > Currently, sasl encryption doesn't work with AsyncRpcChannelImpl, there has 3 > problems: > 1. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslClientHandler.java#L308] > will throw the following exception: > java.lang.UnsupportedOperationException: direct buffer > at > io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199) > at > org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:308) > 2. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java#L212] > has deadlocks problem. > 3. TestAsyncSecureIPC doesn't cover the sasl encryption test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15830) Sasl encryption doesn't work with AsyncRpcChannelImpl
[ https://issues.apache.org/jira/browse/HBASE-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Helmling updated HBASE-15830: -- Status: Patch Available (was: Open) Trying to trigger a new test run > Sasl encryption doesn't work with AsyncRpcChannelImpl > - > > Key: HBASE-15830 > URL: https://issues.apache.org/jira/browse/HBASE-15830 > Project: HBase > Issue Type: Bug >Reporter: Colin Ma > Attachments: HBASE-15830.001.patch, HBASE-15830.002.patch, > HBASE-15830.003.patch > > > Currently, sasl encryption doesn't work with AsyncRpcChannelImpl, there has 3 > problems: > 1. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslClientHandler.java#L308] > will throw the following exception: > java.lang.UnsupportedOperationException: direct buffer > at > io.netty.buffer.UnpooledUnsafeDirectByteBuf.array(UnpooledUnsafeDirectByteBuf.java:199) > at > org.apache.hadoop.hbase.security.SaslClientHandler.write(SaslClientHandler.java:308) > 2. > [sourcecode|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcChannelImpl.java#L212] > has deadlocks problem. > 3. TestAsyncSecureIPC doesn't cover the sasl encryption test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15896) Add timeout tests to flaky list from report-flakies.py
Appy created HBASE-15896: Summary: Add timeout tests to flaky list from report-flakies.py Key: HBASE-15896 URL: https://issues.apache.org/jira/browse/HBASE-15896 Project: HBase Issue Type: Improvement Reporter: Appy Assignee: Appy - Adds timed-out tests to flaky list. Dumpes two new files for reference, 'timeout' and 'failed' for corresponding list of bad tests. - Set --max-builds for different urls separately. This is needed so that we can turn the knobs for post-commit job and flaky-tests job separately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-15854: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 1.1.6 0.98.20 1.2.2 1.3.0 2.0.0 Status: Resolved (was: Patch Available) Picked back to all active branches with fixup and pushed. Thanks for the patch [~rayokota]. Due to issues with JIRA spam lockdown I can't currently assign the issue to you but the commit was made with correct attribution. > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15698) Increment TimeRange not serialized to server
[
https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-15698:
---
Attachment: 15698.v1.txt
Patch with a test.
Without the fix, the test fails:
{code}
java.lang.AssertionError: expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at
org.apache.hadoop.hbase.coprocessor.TestIncrementTimeRange.checkHTableInterfaceMethods(TestIncrementTimeRange.java:177)
at
org.apache.hadoop.hbase.coprocessor.TestIncrementTimeRange.testHTableInterfaceMethods(TestIncrementTimeRange.java:146)
{code}
> Increment TimeRange not serialized to server
>
>
> Key: HBASE-15698
> URL: https://issues.apache.org/jira/browse/HBASE-15698
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.3.0
>Reporter: James Taylor
>Assignee: Sean Busbey
>Priority: Blocker
> Labels: phoenix
> Fix For: 1.3.0, 1.0.4, 1.2.2, 0.98.20, 1.1.6
>
> Attachments: 15698-suggest.txt, 15698.v1.txt, HBASE-15698.1.patch
>
>
> Before HBase-1.2, the Increment TimeRange set on the client was serialized
> over to the server. As of HBase 1.2, this appears to no longer be true, as my
> preIncrement coprocessor always gets HConstants.LATEST_TIMESTAMP as the value
> of increment.getTimeRange().getMax() regardless of what the client has
> specified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[
https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302980#comment-15302980
]
Hadoop QA commented on HBASE-15854:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
14s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 27s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 17s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
26s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
10s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
58s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 17s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 17s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
24s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
10s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 8m
57s {color} | {color:green} Patch does not cause any errors with Hadoop 2.4.1
2.5.2 2.6.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
23s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 21s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 2s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
7s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 20m 28s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12804723/HBASE-15854.1.patch |
| JIRA Issue | HBASE-15854 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf900.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/yetus-0.2.1/lib/precommit/personality/hbase.sh
|
| git revision | master / 43d1a99 |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v3.0.0 |
| Test
[jira] [Updated] (HBASE-15895) remove unmaintained jenkins build analysis tool.
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-15895: Status: Patch Available (was: Open) > remove unmaintained jenkins build analysis tool. > > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Minor > Attachments: HBASE-15895.1.patch > > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15895) remove unmaintained jenkins build analysis tool.
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-15895: Attachment: HBASE-15895.1.patch -01 - remove the dev-support/jenkins-tools directory Fine by you [~appy]? It's a java tool for analyzing the success / flakey rate of our jenkins build runs, that I think you aren't using in your current work to improve our builds? > remove unmaintained jenkins build analysis tool. > > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Minor > Attachments: HBASE-15895.1.patch > > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15895) "buildstats" module is not maintained
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-15895: Priority: Minor (was: Major) > "buildstats" module is not maintained > - > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Minor > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15895) remove unmaintained jenkins build analysis tool.
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-15895: Summary: remove unmaintained jenkins build analysis tool. (was: "buildstats" module is not maintained) > remove unmaintained jenkins build analysis tool. > > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Minor > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15895) "buildstats" module is not maintained
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-15895: Issue Type: Task (was: Bug) > "buildstats" module is not maintained > - > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Minor > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15854) Log the cause of SASL connection failures
[ https://issues.apache.org/jira/browse/HBASE-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302948#comment-15302948 ] Andrew Purtell commented on HBASE-15854: Committing... > Log the cause of SASL connection failures > - > > Key: HBASE-15854 > URL: https://issues.apache.org/jira/browse/HBASE-15854 > Project: HBase > Issue Type: Improvement > Components: security >Affects Versions: 1.2.1 >Reporter: Robert Yokota >Priority: Minor > Attachments: HBASE-15854.1.patch > > > This is the same fix as for HADOOP-11291 to add more info during logging of > SASL connection failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15112) Allow coprocessors to extend 'software attributes' list
[
https://issues.apache.org/jira/browse/HBASE-15112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302931#comment-15302931
]
Nick Dimiduk commented on HBASE-15112:
--
Good points on the perf impact of ServiceLoader. A similar refresh interval of
5-10 minutes should be more than adequate for this implementation as well.
> Allow coprocessors to extend 'software attributes' list
> ---
>
> Key: HBASE-15112
> URL: https://issues.apache.org/jira/browse/HBASE-15112
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
>Reporter: Nick Dimiduk
>
> Over on the {{/master-status}} and {{/rs-status}} pages we have a list of
> release properties, giving details about the cluster deployment. We should
> make this an extension point, allowing coprocessors to register information
> about themselves as well. For example, Phoenix, Trafodion, Tephra, might
> want to advertise installed version and build details as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302900#comment-15302900 ] Enis Soztutar commented on HBASE-15837: --- Pushed to 0.98 as well. Thanks [~apurtell]. > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15112) Allow coprocessors to extend 'software attributes' list
[
https://issues.apache.org/jira/browse/HBASE-15112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302898#comment-15302898
]
Andrew Purtell commented on HBASE-15112:
We already use Service interfaces in the compat modules FWIW, but what
ServiceLoader does is expensive (as I discovered here:
https://issues.apache.org/jira/browse/HBASE-14738?focusedCommentId=14984882=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14984882)
so as long as instances are infrequently resolved that would be fine.
> Allow coprocessors to extend 'software attributes' list
> ---
>
> Key: HBASE-15112
> URL: https://issues.apache.org/jira/browse/HBASE-15112
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
>Reporter: Nick Dimiduk
>
> Over on the {{/master-status}} and {{/rs-status}} pages we have a list of
> release properties, giving details about the cluster deployment. We should
> make this an extension point, allowing coprocessors to register information
> about themselves as well. For example, Phoenix, Trafodion, Tephra, might
> want to advertise installed version and build details as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15112) Allow coprocessors to extend 'software attributes' list
[
https://issues.apache.org/jira/browse/HBASE-15112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302882#comment-15302882
]
Nick Dimiduk commented on HBASE-15112:
--
Actually I don't think we need to touch anything else here. Instead we could
add a [Service
Interface|https://docs.oracle.com/javase/tutorial/ext/basics/spi.html]; any jar
on the classpath would contribute implementations.
> Allow coprocessors to extend 'software attributes' list
> ---
>
> Key: HBASE-15112
> URL: https://issues.apache.org/jira/browse/HBASE-15112
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
>Reporter: Nick Dimiduk
>
> Over on the {{/master-status}} and {{/rs-status}} pages we have a list of
> release properties, giving details about the cluster deployment. We should
> make this an extension point, allowing coprocessors to register information
> about themselves as well. For example, Phoenix, Trafodion, Tephra, might
> want to advertise installed version and build details as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-4368) Expose processlist in shell (per regionserver and perhaps by cluster)
[ https://issues.apache.org/jira/browse/HBASE-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302865#comment-15302865 ] Mikhail Antonov commented on HBASE-4368: [~stack] glanced over the patch - yeah, please also commit to 1.3. Thanks! > Expose processlist in shell (per regionserver and perhaps by cluster) > - > > Key: HBASE-4368 > URL: https://issues.apache.org/jira/browse/HBASE-4368 > Project: HBase > Issue Type: Task > Components: shell >Reporter: stack >Assignee: Talat UYARER > Labels: beginner > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-4368.patch, HBASE-4368v2-withunittest.patch, > HBASE-4368v2.patch, HBASE-4368v3.patch, HBASE-4368v4.patch, > HBASE-4368v5-branch-1.patch > > > HBASE-4057 adds processlist and it shows in the RS UI. This issue is about > getting the processlist to show in the shell, like it does in mysql. > Labelling it noob; this is a pretty substantial issue but it shouldn't be too > hard -- it'd mostly be plumbing from RS into the shell. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (HBASE-15861) Add support for table sets in restore operation
[ https://issues.apache.org/jira/browse/HBASE-15861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-15861 started by Vladimir Rodionov. - > Add support for table sets in restore operation > --- > > Key: HBASE-15861 > URL: https://issues.apache.org/jira/browse/HBASE-15861 > Project: HBase > Issue Type: Task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14030) HBase Backup/Restore Phase 1
[ https://issues.apache.org/jira/browse/HBASE-14030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-14030: --- Resolution: Fixed Status: Resolved (was: Patch Available) > HBase Backup/Restore Phase 1 > > > Key: HBASE-14030 > URL: https://issues.apache.org/jira/browse/HBASE-14030 > Project: HBase > Issue Type: Umbrella >Affects Versions: 2.0.0 >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Fix For: 2.0.0 > > Attachments: HBASE-14030-v0.patch, HBASE-14030-v1.patch, > HBASE-14030-v10.patch, HBASE-14030-v11.patch, HBASE-14030-v12.patch, > HBASE-14030-v13.patch, HBASE-14030-v14.patch, HBASE-14030-v15.patch, > HBASE-14030-v17.patch, HBASE-14030-v18.patch, HBASE-14030-v2.patch, > HBASE-14030-v20.patch, HBASE-14030-v21.patch, HBASE-14030-v22.patch, > HBASE-14030-v23.patch, HBASE-14030-v24.patch, HBASE-14030-v25.patch, > HBASE-14030-v26.patch, HBASE-14030-v27.patch, HBASE-14030-v28.patch, > HBASE-14030-v3.patch, HBASE-14030-v30.patch, HBASE-14030-v35.patch, > HBASE-14030-v37.patch, HBASE-14030-v4.patch, HBASE-14030-v5.patch, > HBASE-14030-v6.patch, HBASE-14030-v7.patch, HBASE-14030-v8.patch, > HBASE-14030.v38.patch, HBASE-14030.v39.patch, HBASE-14030.v40.patch, > HBASE-14030.v41.patch, HBASE-14030.v42.patch, HBASE-14030.v43.patch, > hbase-14030_v36.patch > > > This is the umbrella ticket for Backup/Restore Phase 1. See HBASE-7912 design > doc for the phase description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15895) "buildstats" module is not maintained
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302781#comment-15302781 ] Elliott Clark commented on HBASE-15895: --- Kill it with fire. > "buildstats" module is not maintained > - > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302780#comment-15302780 ] Hudson commented on HBASE-15837: SUCCESS: Integrated in HBase-1.2-IT #518 (See [https://builds.apache.org/job/HBase-1.2-IT/518/]) HBASE-15837 Memstore size accounting is wrong if postBatchMutate() (enis: rev bd6903b9e7bd7707a0c03f30f089b1d31f700411) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15895) "buildstats" module is not maintained
[ https://issues.apache.org/jira/browse/HBASE-15895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302769#comment-15302769 ] Dima Spivak commented on HBASE-15895: - +1 on removal. No patch from me, [~stack]; guessing you're referring to HBASE-15729? > "buildstats" module is not maintained > - > > Key: HBASE-15895 > URL: https://issues.apache.org/jira/browse/HBASE-15895 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey > > See HBASE-15889. We don't actually maintain the "buildstats" module any more. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15892) Single command line to make patch, upload it to jira, and update review board
[ https://issues.apache.org/jira/browse/HBASE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302738#comment-15302738 ] Hudson commented on HBASE-15892: FAILURE: Integrated in HBase-Trunk_matrix #949 (See [https://builds.apache.org/job/HBase-Trunk_matrix/949/]) HBASE-15892 Script to create patch, upload it to jira, and update review (stack: rev 3ffaa116fe5ab10492b01a6334b4341439aa7a03) * dev-support/python-requirements.txt * dev-support/submit-patch.py > Single command line to make patch, upload it to jira, and update review board > - > > Key: HBASE-15892 > URL: https://issues.apache.org/jira/browse/HBASE-15892 > Project: HBase > Issue Type: New Feature >Reporter: Appy >Assignee: Appy >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-15892_branch-1_v1.patch, > HBASE-15892_master_v1.patch, HBASE-15892_master_v2.patch, > HBASE-15892_master_v3.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15790) Force "hbase" ownership on bulkload
[ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302724#comment-15302724 ] Matteo Bertozzi commented on HBASE-15790: - yeah, it will throw exception. any idea on how change it? I basically want to prevent the ability to bulkload files hbase is not able to interact with. as enis mentioned SecureBulkLoad is the way to go since it works in both secure and unsecure way, but some people still don't use it since it is something that we still have to enable by hand. > Force "hbase" ownership on bulkload > --- > > Key: HBASE-15790 > URL: https://issues.apache.org/jira/browse/HBASE-15790 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 2.0.0, 1.2.1, 1.1.4, 0.98.19 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Minor > Attachments: HBASE-15790-v0.patch, HBASE-15790-v1.patch, > HBASE-15790-v2.patch, HBASE-15790-v3.patch > > > When a user different than "hbase" bulkload files, in general we end up with > files owned by a user different than hbase. sometimes this causes problems > with hbase not be able to move files around archiving/deleting. > A simple solution is probably to change the ownership of the files to "hbase" > during bulkload. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302696#comment-15302696 ] Andrew Purtell commented on HBASE-15847: Thanks [~gjacoby], I will apply it today > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-15847-0.98.patch, HBASE-15847-branch-1.patch, > HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-15837: --- Fix Version/s: 0.98.20 Please, thanks [~enis] > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 0.98.20, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15837) Memstore size accounting is wrong if postBatchMutate() throws exception
[ https://issues.apache.org/jira/browse/HBASE-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-15837: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I've committed this. Thanks [~elserj]. [~apurtell] do you want this in 0.98? > Memstore size accounting is wrong if postBatchMutate() throws exception > --- > > Key: HBASE-15837 > URL: https://issues.apache.org/jira/browse/HBASE-15837 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.0.0, 1.3.0, 1.2.2, 1.1.6 > > Attachments: HBASE-15837.001.patch, hbase-15837-v1.patch, > hbase-15837.branch-1.patch, hbase-memstore-size-accounting.patch > > > Over in PHOENIX-2883, I've been trying to figure out how to track down the > root cause of an issue we were seeing where a negative memstoreSize was > ultimately causing an RS to abort. The tl;dr version is > * Something causes memstoreSize to be negative (not sure what is doing this > yet) > * All subsequent flushes short-circuit and don't run because they think there > is no data to flush > * The region is eventually closed (commonly, for a move). > * A final flush is attempted on each store before closing (which also > short-circuit for the same reason), leaving unflushed data in each store. > * The sanity check that each store's size is zero fails and the RS aborts. > I have a little patch which I think should improve our failure case around > this, preventing the RS abort safely (forcing a flush when memstoreSize is > negative) and logging a calltrace when an update to memstoreSize make it > negative (to find culprits in the future). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
