[jira] [Updated] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17890:
---
Status: Open (was: Patch Available)
All failed tests pass locally. retry
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 1.2.5, 2.0.0
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch,
> HBASE-17890.v1.patch, HBASE-17890.v2.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17890:
---
Status: Patch Available (was: Open)
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 1.2.5, 2.0.0
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch,
> HBASE-17890.v1.patch, HBASE-17890.v2.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17890:
---
Attachment: HBASE-17890.v2.patch
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 2.0.0, 1.2.5
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch,
> HBASE-17890.v1.patch, HBASE-17890.v2.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17904) Get runs into NoSuchElementException when using Read Replica, with hbase. ipc.client.specificThreadForWriting to be true and hbase.rpc.client.impl to be org.apache.had
[
https://issues.apache.org/jira/browse/HBASE-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967125#comment-15967125
]
Hadoop QA commented on HBASE-17904:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 25s
{color} | {color:blue} Docker mode activated. {color} |
| {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
1s {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 44s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
56s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 59s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
35s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
45s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
31s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 38s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 23s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
8s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 8s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 8s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
34s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
43s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
57m 33s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 21s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m 8s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 175m 20s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
28s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 273m 37s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.snapshot.TestExportSnapshot |
| | hadoop.hbase.client.TestAsyncBalancerAdminApi |
| | hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | hadoop.hbase.snapshot.TestMobExportSnapshot |
| | hadoop.hbase.snapshot.TestMobSecureExportSnapshot |
| Timed out junit tests |
org.apache.hadoop.hbase.replication.regionserver.TestWALEntryStream |
| | org.apache.hadoop.hbase.backup.TestBackupDeleteRestore |
| | org.apache.hadoop.hbase.backup.TestHFileArchiving |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12863172/HBASE-17904-master-v001.patch
|
| JIRA Issue | HBASE-17904 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux b12c4d0b511c 4.8.3-std-1 #1 SMP Fri Oct 21 11:15:43 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Updated] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14614: -- Attachment: HBASE-14614.master.036.patch > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch, HBASE-14614.master.035.patch, > HBASE-14614.master.036.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17125) Inconsistent result when use filter to read data
[
https://issues.apache.org/jira/browse/HBASE-17125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967101#comment-15967101
]
Guanghao Zhang commented on HBASE-17125:
Add 007 patch which implement a new SpecifiedNumVersionsColumnFilter. And the
ut testSpecifiedNumVersionsColumnFilter shows how to use this filter.
> Inconsistent result when use filter to read data
>
>
> Key: HBASE-17125
> URL: https://issues.apache.org/jira/browse/HBASE-17125
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: example.diff, HBASE-17125.master.001.patch,
> HBASE-17125.master.002.patch, HBASE-17125.master.002.patch,
> HBASE-17125.master.003.patch, HBASE-17125.master.004.patch,
> HBASE-17125.master.005.patch, HBASE-17125.master.006.patch,
> HBASE-17125.master.007.patch
>
>
> Assume a cloumn's max versions is 3, then we write 4 versions of this column.
> The oldest version doesn't remove immediately. But from the user view, the
> oldest version has gone. When user use a filter to query, if the filter skip
> a new version, then the oldest version will be seen again. But after compact
> the region, then the oldest version will never been seen. So it is weird for
> user. The query will get inconsistent result before and after region
> compaction.
> The reason is matchColumn method of UserScanQueryMatcher. It first check the
> cell by filter, then check the number of versions needed. So if the filter
> skip the new version, then the oldest version will be seen again when it is
> not removed.
> Have a discussion offline with [~Apache9] and [~fenghh], now we have two
> solution for this problem. The first idea is check the number of versions
> first, then check the cell by filter. As the comment of setFilter, the filter
> is called after all tests for ttl, column match, deletes and max versions
> have been run.
> {code}
> /**
>* Apply the specified server-side filter when performing the Query.
>* Only {@link Filter#filterKeyValue(Cell)} is called AFTER all tests
>* for ttl, column match, deletes and max versions have been run.
>* @param filter filter to run on the server
>* @return this for invocation chaining
>*/
> public Query setFilter(Filter filter) {
> this.filter = filter;
> return this;
> }
> {code}
> But this idea has another problem, if a column's max version is 5 and the
> user query only need 3 versions. It first check the version's number, then
> check the cell by filter. So the cells number of the result may less than 3.
> But there are 2 versions which don't read anymore.
> So the second idea has three steps.
> 1. check by the max versions of this column
> 2. check the kv by filter
> 3. check the versions which user need.
> But this will lead the ScanQueryMatcher more complicated. And this will break
> the javadoc of Query.setFilter.
> Now we don't have a final solution for this problem. Suggestions are welcomed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17125) Inconsistent result when use filter to read data
[
https://issues.apache.org/jira/browse/HBASE-17125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-17125:
---
Attachment: HBASE-17125.master.007.patch
> Inconsistent result when use filter to read data
>
>
> Key: HBASE-17125
> URL: https://issues.apache.org/jira/browse/HBASE-17125
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: example.diff, HBASE-17125.master.001.patch,
> HBASE-17125.master.002.patch, HBASE-17125.master.002.patch,
> HBASE-17125.master.003.patch, HBASE-17125.master.004.patch,
> HBASE-17125.master.005.patch, HBASE-17125.master.006.patch,
> HBASE-17125.master.007.patch
>
>
> Assume a cloumn's max versions is 3, then we write 4 versions of this column.
> The oldest version doesn't remove immediately. But from the user view, the
> oldest version has gone. When user use a filter to query, if the filter skip
> a new version, then the oldest version will be seen again. But after compact
> the region, then the oldest version will never been seen. So it is weird for
> user. The query will get inconsistent result before and after region
> compaction.
> The reason is matchColumn method of UserScanQueryMatcher. It first check the
> cell by filter, then check the number of versions needed. So if the filter
> skip the new version, then the oldest version will be seen again when it is
> not removed.
> Have a discussion offline with [~Apache9] and [~fenghh], now we have two
> solution for this problem. The first idea is check the number of versions
> first, then check the cell by filter. As the comment of setFilter, the filter
> is called after all tests for ttl, column match, deletes and max versions
> have been run.
> {code}
> /**
>* Apply the specified server-side filter when performing the Query.
>* Only {@link Filter#filterKeyValue(Cell)} is called AFTER all tests
>* for ttl, column match, deletes and max versions have been run.
>* @param filter filter to run on the server
>* @return this for invocation chaining
>*/
> public Query setFilter(Filter filter) {
> this.filter = filter;
> return this;
> }
> {code}
> But this idea has another problem, if a column's max version is 5 and the
> user query only need 3 versions. It first check the version's number, then
> check the cell by filter. So the cells number of the result may less than 3.
> But there are 2 versions which don't read anymore.
> So the second idea has three steps.
> 1. check by the max versions of this column
> 2. check the kv by filter
> 3. check the versions which user need.
> But this will lead the ScanQueryMatcher more complicated. And this will break
> the javadoc of Query.setFilter.
> Now we don't have a final solution for this problem. Suggestions are welcomed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17888) Add generic methods for updating metrics on start and end of a procedure execution
[ https://issues.apache.org/jira/browse/HBASE-17888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967098#comment-15967098 ] stack commented on HBASE-17888: --- Patch looks good. I'll fix this stuff on commit in javadoc: 'e - R'; i.e. the hyphen between param name and description. It comes out wonky when you render. I was going to add note that currently we need to do start and finish in two places but will be addressed in a follow-on. That right? Thanks [~uagashe] You good [~appy]? > Add generic methods for updating metrics on start and end of a procedure > execution > -- > > Key: HBASE-17888 > URL: https://issues.apache.org/jira/browse/HBASE-17888 > Project: HBase > Issue Type: Improvement > Components: proc-v2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Attachments: HBASE-17888.v1.patch, HBASE-17888.v2.patch > > > For all procedures in Procv2 framework, Procedure class can have generic > methods to update metrics on start and end of a procedure execution. Specific > procedure can override these and implement/ update respective metrics. > Default implementation needs to be provided so override and implementation is > optional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967068#comment-15967068 ] Albert Lee commented on HBASE-17906: Thanks Ted, let me see it. > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Labels: patch > Fix For: 1.2.2, 0.98.21 > > Attachments: HBASE-17906.patch > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17888) Add generic methods for updating metrics on start and end of a procedure execution
[
https://issues.apache.org/jira/browse/HBASE-17888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966956#comment-15966956
]
Hadoop QA commented on HBASE-17888:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 31m 13s
{color} | {color:blue} Docker mode activated. {color} |
| {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 2 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 17s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
8s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
48s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
42s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
37s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 47s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 19s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
53s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 50s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 50s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
51s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
41s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
60m 26s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
53s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m 10s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 32s
{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 47s
{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
33s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 117m 26s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12863156/HBASE-17888.v2.patch |
| JIRA Issue | HBASE-17888 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 7ee5a3948696 4.8.3-std-1 #1 SMP Fri Oct 21 11:15:43 UTC 2016
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 / da5fb27 |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/6408/testReport/ |
| modules | C: hbase-procedure hbase-hadoop-compat hbase-hadoop2-compat U: . |
| Console output |
[jira] [Commented] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966936#comment-15966936
]
Hudson commented on HBASE-16775:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2847 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/2847/])
HBASE-16775 Fix flaky TestExportSnapshot#testExportRetry. (appy: rev
da5fb27eabed4a4b4d251be973ee945fb52895bf)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestMobExportSnapshot.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestSecureExportSnapshot.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshotNoCluster.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestMobSecureExportSnapshot.java
> Flakey test with TestExportSnapshot#testExportRetry and
> TestMobExportSnapshot#testExportRetry
> --
>
> Key: HBASE-16775
> URL: https://issues.apache.org/jira/browse/HBASE-16775
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: Appy
> Attachments: disable.patch, HBASE-16775.master.001.patch,
> HBASE-16775.master.002.patch, HBASE-16775.master.003.patch,
> HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
> HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
>
>
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not
> taken by the mapper job, so the retry is actually 0. Debugging to see why
> this is the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17909) Redundant exclusion of jruby-complete in pom of hbase-spark
[ https://issues.apache.org/jira/browse/HBASE-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966903#comment-15966903 ] stack commented on HBASE-17909: --- My guess is a copy/paste of another pom pulled in the exclusion. A cleanup would be appreciated. > Redundant exclusion of jruby-complete in pom of hbase-spark > --- > > Key: HBASE-17909 > URL: https://issues.apache.org/jira/browse/HBASE-17909 > Project: HBase > Issue Type: Bug > Components: spark >Reporter: Xiang Li >Assignee: Xiang Li >Priority: Minor > > In pom.xml of hbase-spark, jruby-complete is excluded from some of HBase > child modules, there are 2 issues: > 1. jruby-complete is excluded from the following child modules, > - hbase-client > - hbase-hadoop-compat > - hbase-hadoop2-compat > but those child modules does not introduce jruby-complete. jruby-complete is > only introduced by hbase-shell, and by transitive dependency, it is also > introduced by hbase-assembly, as hbase-assembly depends on hbase-shell. > But none of 3 modules listed above introduces jruby-complete. > 2. The exclusion of jruby-complete is stated twice in each of the 3 child > modules listed in 1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17904) Get runs into NoSuchElementException when using Read Replica, with hbase. ipc.client.specificThreadForWriting to be true and hbase.rpc.client.impl to be org.apache.hadoo
[
https://issues.apache.org/jira/browse/HBASE-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun updated HBASE-17904:
-
Status: Patch Available (was: Open)
> Get runs into NoSuchElementException when using Read Replica, with hbase.
> ipc.client.specificThreadForWriting to be true and hbase.rpc.client.impl to
> be org.apache.hadoop.hbase.ipc.RpcClientImpl
> --
>
> Key: HBASE-17904
> URL: https://issues.apache.org/jira/browse/HBASE-17904
> Project: HBase
> Issue Type: Bug
> Components: Client
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: huaxiang sun
> Attachments: HBASE-17904-master-v001.patch
>
>
> When testing read replica with 2.0.0 code, with the following config
> {code}
>
> hbase.ipc.client.specificThreadForWriting
> true
>
>
> hbase.rpc.client.impl
> org.apache.hadoop.hbase.ipc.RpcClientImpl
>
> {code}
> The hbase client runs into the following exception
> {code}
> Exception in thread "main" java.util.NoSuchElementException
> at java.util.ArrayDeque.removeFirst(ArrayDeque.java:280)
> at java.util.ArrayDeque.remove(ArrayDeque.java:447)
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$CallSender.remove(BlockingRpcConnection.java:159)
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$3.run(BlockingRpcConnection.java:760)
> at
> org.apache.hadoop.hbase.ipc.HBaseRpcControllerImpl.startCancel(HBaseRpcControllerImpl.java:229)
> at
> org.apache.hadoop.hbase.client.CancellableRegionServerCallable.cancel(CancellableRegionServerCallable.java:86)
> at
> org.apache.hadoop.hbase.client.ResultBoundedCompletionService$QueueingFuture.cancel(ResultBoundedCompletionService.java:106)
> at
> org.apache.hadoop.hbase.client.ResultBoundedCompletionService.cancelAll(ResultBoundedCompletionService.java:274)
> at
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.call(RpcRetryingCallerWithReadReplicas.java:224)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:445)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:409)
> at HBaseThreadedGet.doWork(HBaseThreadedGet.java:45)
> at HBaseThreadedGet.main(HBaseThreadedGet.java:19)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17904) Get runs into NoSuchElementException when using Read Replica, with hbase. ipc.client.specificThreadForWriting to be true and hbase.rpc.client.impl to be org.apache.hadoo
[
https://issues.apache.org/jira/browse/HBASE-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun updated HBASE-17904:
-
Attachment: HBASE-17904-master-v001.patch
Attach a first patch. Add the BlockingQueue back, the cancel path is not
protected by any lock.
> Get runs into NoSuchElementException when using Read Replica, with hbase.
> ipc.client.specificThreadForWriting to be true and hbase.rpc.client.impl to
> be org.apache.hadoop.hbase.ipc.RpcClientImpl
> --
>
> Key: HBASE-17904
> URL: https://issues.apache.org/jira/browse/HBASE-17904
> Project: HBase
> Issue Type: Bug
> Components: Client
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: huaxiang sun
> Attachments: HBASE-17904-master-v001.patch
>
>
> When testing read replica with 2.0.0 code, with the following config
> {code}
>
> hbase.ipc.client.specificThreadForWriting
> true
>
>
> hbase.rpc.client.impl
> org.apache.hadoop.hbase.ipc.RpcClientImpl
>
> {code}
> The hbase client runs into the following exception
> {code}
> Exception in thread "main" java.util.NoSuchElementException
> at java.util.ArrayDeque.removeFirst(ArrayDeque.java:280)
> at java.util.ArrayDeque.remove(ArrayDeque.java:447)
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$CallSender.remove(BlockingRpcConnection.java:159)
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$3.run(BlockingRpcConnection.java:760)
> at
> org.apache.hadoop.hbase.ipc.HBaseRpcControllerImpl.startCancel(HBaseRpcControllerImpl.java:229)
> at
> org.apache.hadoop.hbase.client.CancellableRegionServerCallable.cancel(CancellableRegionServerCallable.java:86)
> at
> org.apache.hadoop.hbase.client.ResultBoundedCompletionService$QueueingFuture.cancel(ResultBoundedCompletionService.java:106)
> at
> org.apache.hadoop.hbase.client.ResultBoundedCompletionService.cancelAll(ResultBoundedCompletionService.java:274)
> at
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.call(RpcRetryingCallerWithReadReplicas.java:224)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:445)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:409)
> at HBaseThreadedGet.doWork(HBaseThreadedGet.java:45)
> at HBaseThreadedGet.main(HBaseThreadedGet.java:19)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-14614) Procedure v2: Core Assignment Manager
[
https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966792#comment-15966792
]
Hadoop QA commented on HBASE-14614:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 19s
{color} | {color:blue} Docker mode activated. {color} |
| {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 98 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m 58s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
18s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 22s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 26m
7s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
25s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m 1s
{color} | {color:red} hbase-protocol-shaded in master has 24 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 56s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 11s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
38s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 24s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 2m 24s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 24s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 27m
49s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
21s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch has 128 line(s) that end in whitespace. Use git
apply --whitespace=fix. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
32m 25s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 2m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 8m
18s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 26s
{color} | {color:red} hbase-server generated 21 new + 0 unchanged - 0 fixed =
21 total (was 0) {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 28s
{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 40s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 10s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 17s
{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 20s
{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 94m 13s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 39s
{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
36s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} |
[jira] [Commented] (HBASE-17904) Get runs into NoSuchElementException when using Read Replica, with hbase. ipc.client.specificThreadForWriting to be true and hbase.rpc.client.impl to be org.apache.had
[
https://issues.apache.org/jira/browse/HBASE-17904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966781#comment-15966781
]
huaxiang sun commented on HBASE-17904:
--
add a new test case in TestReplicaWithCluster to explore the issue.
{code}
@Test
public void testReplicaGetWithRpcClientImpl() throws IOException {
HTU.getConfiguration().setBoolean("hbase.ipc.client.specificThreadForWriting",
true);
HTU.getConfiguration().set("hbase.rpc.client.impl",
"org.apache.hadoop.hbase.ipc.RpcClientImpl");
// Create table then get the single region for our new table.
HTableDescriptor hdt =
HTU.createTableDescriptor("testReplicaGetWithRpcClientImpl");
hdt.setRegionReplication(NB_SERVERS);
hdt.addCoprocessor(SlowMeCopro.class.getName());
try {
Table table = HTU.createTable(hdt, new byte[][] { f }, null);
Put p = new Put(row);
p.addColumn(f, row, row);
table.put(p);
// Flush so it can be picked by the replica refresher thread
HTU.flush(table.getName());
// Sleep for some time until data is picked up by replicas
try {
Thread.sleep(2 * REFRESH_PERIOD);
} catch (InterruptedException e1) {
LOG.error(e1);
}
try {
// Create the new connection so new config can kick in
Connection connection =
ConnectionFactory.createConnection(HTU.getConfiguration());
Table t = connection.getTable(hdt.getTableName());
// But if we ask for stale we will get it
SlowMeCopro.cdl.set(new CountDownLatch(1));
Get g = new Get(row);
g.setConsistency(Consistency.TIMELINE);
Result r = t.get(g);
Assert.assertTrue(r.isStale());
SlowMeCopro.cdl.get().countDown();
} finally {
SlowMeCopro.cdl.get().countDown();
SlowMeCopro.sleepTime.set(0);
}
} finally {
HTU.getConfiguration().unset("hbase.ipc.client.specificThreadForWriting");
HTU.getConfiguration().unset("hbase.rpc.client.impl");
HTU.getAdmin().disableTable(hdt.getTableName());
HTU.deleteTable(hdt.getTableName());
}
}
{code}
> Get runs into NoSuchElementException when using Read Replica, with hbase.
> ipc.client.specificThreadForWriting to be true and hbase.rpc.client.impl to
> be org.apache.hadoop.hbase.ipc.RpcClientImpl
> --
>
> Key: HBASE-17904
> URL: https://issues.apache.org/jira/browse/HBASE-17904
> Project: HBase
> Issue Type: Bug
> Components: Client
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>
> When testing read replica with 2.0.0 code, with the following config
> {code}
>
> hbase.ipc.client.specificThreadForWriting
> true
>
>
> hbase.rpc.client.impl
> org.apache.hadoop.hbase.ipc.RpcClientImpl
>
> {code}
> The hbase client runs into the following exception
> {code}
> Exception in thread "main" java.util.NoSuchElementException
> at java.util.ArrayDeque.removeFirst(ArrayDeque.java:280)
> at java.util.ArrayDeque.remove(ArrayDeque.java:447)
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$CallSender.remove(BlockingRpcConnection.java:159)
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$3.run(BlockingRpcConnection.java:760)
> at
> org.apache.hadoop.hbase.ipc.HBaseRpcControllerImpl.startCancel(HBaseRpcControllerImpl.java:229)
> at
> org.apache.hadoop.hbase.client.CancellableRegionServerCallable.cancel(CancellableRegionServerCallable.java:86)
> at
> org.apache.hadoop.hbase.client.ResultBoundedCompletionService$QueueingFuture.cancel(ResultBoundedCompletionService.java:106)
> at
> org.apache.hadoop.hbase.client.ResultBoundedCompletionService.cancelAll(ResultBoundedCompletionService.java:274)
> at
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.call(RpcRetryingCallerWithReadReplicas.java:224)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:445)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:409)
> at HBaseThreadedGet.doWork(HBaseThreadedGet.java:45)
> at HBaseThreadedGet.main(HBaseThreadedGet.java:19)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17888) Add generic methods for updating metrics on start and end of a procedure execution
[ https://issues.apache.org/jira/browse/HBASE-17888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-17888: - Attachment: HBASE-17888.v2.patch Changes per review comments > Add generic methods for updating metrics on start and end of a procedure > execution > -- > > Key: HBASE-17888 > URL: https://issues.apache.org/jira/browse/HBASE-17888 > Project: HBase > Issue Type: Improvement > Components: proc-v2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Attachments: HBASE-17888.v1.patch, HBASE-17888.v2.patch > > > For all procedures in Procv2 framework, Procedure class can have generic > methods to update metrics on start and end of a procedure execution. Specific > procedure can override these and implement/ update respective metrics. > Default implementation needs to be provided so override and implementation is > optional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-15143) Procedure v2 - Web UI displaying queues
[
https://issues.apache.org/jira/browse/HBASE-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966728#comment-15966728
]
Hadoop QA commented on HBASE-15143:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 25s
{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} rubocop {color} | {color:blue} 0m 0s
{color} | {color:blue} rubocop was not available. {color} |
| {color:blue}0{color} | {color:blue} ruby-lint {color} | {color:blue} 0m 0s
{color} | {color:blue} Ruby-lint was not available. {color} |
| {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 6 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 50s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
15s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 59s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
52s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
1s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m 53s
{color} | {color:red} hbase-protocol-shaded in master has 24 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 20s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
0s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 50s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m 50s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 50s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
54s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
1s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch has 25 line(s) that end in whitespace. Use git
apply --whitespace=fix. {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 1s
{color} | {color:red} The patch 13 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
27m 15s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 1m
37s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m 7s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 15s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 58s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 25s
{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 44s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 16s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 99m 13s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 5m 10s
{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color}
[jira] [Commented] (HBASE-12870) "Major compaction triggered" and "Skipping major compaction" messages lack the region information
[
https://issues.apache.org/jira/browse/HBASE-12870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966708#comment-15966708
]
Hadoop QA commented on HBASE-12870:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 34s
{color} | {color:blue} Docker mode activated. {color} |
| {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} 6m
55s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 48s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
58s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 40s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
55s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 46s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 46s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
51s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
34m 20s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m 16s
{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed = 1
total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 34s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 101m 36s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
30s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 154m 57s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | Possible null pointer dereference of CompactionPolicy.storeConfigInfo in
org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy.shouldPerformMajorCompaction(Collection)
Dereferenced at
RatioBasedCompactionPolicy.java:CompactionPolicy.storeConfigInfo in
org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy.shouldPerformMajorCompaction(Collection)
Dereferenced at RatioBasedCompactionPolicy.java:[line 75] |
| Failed junit tests | hadoop.hbase.util.TestHBaseFsckTwoRS |
| Timed out junit tests | org.apache.hadoop.hbase.client.TestFromClientSide |
| | org.apache.hadoop.hbase.client.TestIncrementFromClientSideWithCoprocessor
|
| | org.apache.hadoop.hbase.TestAcidGuarantees |
| | org.apache.hadoop.hbase.util.TestHBaseFsckTwoRS |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.0 Server=1.12.0 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12863107/HBASE-12870.patch |
| JIRA Issue | HBASE-12870 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux ef818c2d58ab 3.13.0-108-generic #155-Ubuntu SMP Wed Jan 11
16:58:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
|
[jira] [Commented] (HBASE-17366) Run TestHFile#testReaderWithoutBlockCache failes
[
https://issues.apache.org/jira/browse/HBASE-17366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966463#comment-15966463
]
Hadoop QA commented on HBASE-17366:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 14s
{color} | {color:blue} Docker mode activated. {color} |
| {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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
12s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} master passed {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
17s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 7s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
43s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
47s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
29m 14s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 2s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 112m 53s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 155m 23s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12863085/HBASE-17366-master-002.patch
|
| JIRA Issue | HBASE-17366 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux e7635e5960fe 3.13.0-106-generic #153-Ubuntu SMP Tue Dec 6
15:44:32 UTC 2016 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 / cf3215d |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/6402/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/6402/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Run TestHFile#testReaderWithoutBlockCache failes
>
>
> Key: HBASE-17366
> URL: https://issues.apache.org/jira/browse/HBASE-17366
> Project: HBase
> Issue Type: Bug
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: HBASE-17366-master-001.patch,
>
[jira] [Comment Edited] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966398#comment-15966398 ] stack edited comment on HBASE-14614 at 4/12/17 6:59 PM: v035 is v034 w/ added log message. Trying to see which are flakies. was (Author: stack): v036 is v035 w/ added log message. Trying to see which are flakies. > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch, HBASE-14614.master.035.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966398#comment-15966398 ] stack commented on HBASE-14614: --- v036 is v035 w/ added log message. Trying to see which are flakies. > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch, HBASE-14614.master.035.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14614: -- Attachment: HBASE-14614.master.035.patch > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch, HBASE-14614.master.035.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966394#comment-15966394 ] stack commented on HBASE-14614: --- Ok. All these tests pass locally. There is an outstanding issue where we trip a stuck region assign. It is hard to reproduce. It currently is in the way of my getting a good run up on a cluster. This could explain some of the failures seen here. Will keep working on it. Meantime, let me work on trying to cut up this patch into smaller pieces. Will need reviews on core. Let me also work on doc. and description of what this patch contains. The current changeset comment has gone stale. > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-12870) "Major compaction triggered" and "Skipping major compaction" messages lack the region information
[
https://issues.apache.org/jira/browse/HBASE-12870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966371#comment-15966371
]
Andrew Purtell commented on HBASE-12870:
Cam we also include the region information for "Timed out waiting for lock for
row". Been dealing with them for the last couple of days. We can find the info
with a stack dump but would be better if the WARN level log line alerting us to
the condition also carries that information.
> "Major compaction triggered" and "Skipping major compaction" messages lack
> the region information
> -
>
> Key: HBASE-12870
> URL: https://issues.apache.org/jira/browse/HBASE-12870
> Project: HBase
> Issue Type: Improvement
> Components: Compaction
>Affects Versions: 1.3.1
>Reporter: Hari Krishna Dara
>Assignee: Chinmay Kulkarni
> Labels: compaction, patch
> Fix For: 1.3.1
>
> Attachments: HBASE-12870.patch
>
>
> The below messages coming from {{RatioBasedCompactionPolicy}} log the default
> {{.toString()}} output of itself, which is not useful:
> {noformat}
> 2015-01-16 06:15:07,166 DEBUG
> org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy:
> Major compaction triggered on store
> org.apache.hadoop.hbase.regionserver.compactions.ExploringCompactionPolicy@4acab1f5;
> time since last major compaction 339994249ms
> {noformat}
> {noformat}
> 2015-01-16 09:49:12,872 DEBUG
> org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy:
> Skipping major compaction of
> org.apache.hadoop.hbase.regionserver.compactions.ExploringCompactionPolicy@7b9f47bb
> because one (major) compacted file only and oldestTime 6795587394ms is <
> ttl=1555200
> {noformat}
> It should log the store/region information instead. Unfortunately, this
> information seems to be unavailable at this point, so more context needs to
> be supplied while calling {{RatioBasedCompactionPolicy.isMajorCompaction()}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14614: -- Attachment: (was: HBASE-14614.master.002.patch) > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14614: -- Attachment: (was: HBASE-14614.master.016.patch) > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14614: -- Attachment: (was: HBASE-14614.master.001.patch) > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch, HBASE-14614.master.009.patch, > HBASE-14614.master.010.patch, HBASE-14614.master.011.patch, > HBASE-14614.master.012.patch, HBASE-14614.master.012.patch, > HBASE-14614.master.013.patch, HBASE-14614.master.014.patch, > HBASE-14614.master.015.patch, HBASE-14614.master.017.patch, > HBASE-14614.master.018.patch, HBASE-14614.master.019.patch, > HBASE-14614.master.020.patch, HBASE-14614.master.021.patch, > HBASE-14614.master.022.patch, HBASE-14614.master.023.patch, > HBASE-14614.master.024.patch, HBASE-14614.master.025.patch, > HBASE-14614.master.026.patch, HBASE-14614.master.027.patch, > HBASE-14614.master.028.patch, HBASE-14614.master.029.patch, > HBASE-14614.master.030.patch, HBASE-14614.master.031.patch, > HBASE-14614.master.032.patch, HBASE-14614.master.033.patch, > HBASE-14614.master.034.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-15143) Procedure v2 - Web UI displaying queues
[ https://issues.apache.org/jira/browse/HBASE-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15143: -- Attachment: HBASE-15143-BM-0011.patch Retry > Procedure v2 - Web UI displaying queues > --- > > Key: HBASE-15143 > URL: https://issues.apache.org/jira/browse/HBASE-15143 > Project: HBase > Issue Type: Sub-task > Components: proc-v2, UI >Reporter: Matteo Bertozzi >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15143-BM-0001.patch, HBASE-15143-BM-0002.patch, > HBASE-15143-BM-0003.patch, HBASE-15143-BM-0004.patch, > HBASE-15143-BM-0005.patch, HBASE-15143-BM-0006.patch, > HBASE-15143-BM-0006.patch, HBASE-15143-BM-0007.patch, > HBASE-15143-BM-0008.patch, HBASE-15143-BM-0009.patch, > HBASE-15143-BM-0010.patch, HBASE-15143-BM-0011.patch, > HBASE-15143-BM-0011.patch, screenshot.png > > > We can query MasterProcedureScheduler to display the various procedures and > who is holding table/region locks. > Each procedure is in a TableQueue or ServerQueue, so it is easy to display > the procedures in its own group. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-12870) "Major compaction triggered" and "Skipping major compaction" messages lack the region information
[
https://issues.apache.org/jira/browse/HBASE-12870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated HBASE-12870:
-
Labels: compaction patch (was: )
Fix Version/s: 1.3.1
Affects Version/s: (was: 0.98.9)
1.3.1
Status: Patch Available (was: Open)
Added region name information to debug log statements.
> "Major compaction triggered" and "Skipping major compaction" messages lack
> the region information
> -
>
> Key: HBASE-12870
> URL: https://issues.apache.org/jira/browse/HBASE-12870
> Project: HBase
> Issue Type: Improvement
> Components: Compaction
>Affects Versions: 1.3.1
>Reporter: Hari Krishna Dara
>Assignee: Chinmay Kulkarni
> Labels: patch, compaction
> Fix For: 1.3.1
>
> Attachments: HBASE-12870.patch
>
>
> The below messages coming from {{RatioBasedCompactionPolicy}} log the default
> {{.toString()}} output of itself, which is not useful:
> {noformat}
> 2015-01-16 06:15:07,166 DEBUG
> org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy:
> Major compaction triggered on store
> org.apache.hadoop.hbase.regionserver.compactions.ExploringCompactionPolicy@4acab1f5;
> time since last major compaction 339994249ms
> {noformat}
> {noformat}
> 2015-01-16 09:49:12,872 DEBUG
> org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy:
> Skipping major compaction of
> org.apache.hadoop.hbase.regionserver.compactions.ExploringCompactionPolicy@7b9f47bb
> because one (major) compacted file only and oldestTime 6795587394ms is <
> ttl=1555200
> {noformat}
> It should log the store/region information instead. Unfortunately, this
> information seems to be unavailable at this point, so more context needs to
> be supplied while calling {{RatioBasedCompactionPolicy.isMajorCompaction()}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-12870) "Major compaction triggered" and "Skipping major compaction" messages lack the region information
[
https://issues.apache.org/jira/browse/HBASE-12870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated HBASE-12870:
-
Attachment: HBASE-12870.patch
> "Major compaction triggered" and "Skipping major compaction" messages lack
> the region information
> -
>
> Key: HBASE-12870
> URL: https://issues.apache.org/jira/browse/HBASE-12870
> Project: HBase
> Issue Type: Improvement
> Components: Compaction
>Affects Versions: 0.98.9
>Reporter: Hari Krishna Dara
>Assignee: Chinmay Kulkarni
> Attachments: HBASE-12870.patch
>
>
> The below messages coming from {{RatioBasedCompactionPolicy}} log the default
> {{.toString()}} output of itself, which is not useful:
> {noformat}
> 2015-01-16 06:15:07,166 DEBUG
> org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy:
> Major compaction triggered on store
> org.apache.hadoop.hbase.regionserver.compactions.ExploringCompactionPolicy@4acab1f5;
> time since last major compaction 339994249ms
> {noformat}
> {noformat}
> 2015-01-16 09:49:12,872 DEBUG
> org.apache.hadoop.hbase.regionserver.compactions.RatioBasedCompactionPolicy:
> Skipping major compaction of
> org.apache.hadoop.hbase.regionserver.compactions.ExploringCompactionPolicy@7b9f47bb
> because one (major) compacted file only and oldestTime 6795587394ms is <
> ttl=1555200
> {noformat}
> It should log the store/region information instead. Unfortunately, this
> information seems to be unavailable at this point, so more context needs to
> be supplied while calling {{RatioBasedCompactionPolicy.isMajorCompaction()}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966325#comment-15966325
]
Hadoop QA commented on HBASE-17890:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 12s
{color} | {color:blue} Docker mode activated. {color} |
| {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 10s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
59s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
43s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
34s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 43s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
59s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
44s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
27m 5s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
49s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 9s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 101m 40s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
29s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 147m 7s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12863072/HBASE-17890.v1.patch |
| JIRA Issue | HBASE-17890 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 9da881a57410 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20
09:57:27 UTC 2016 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 / cf3215d |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/6401/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/6401/testReport/ |
| modules | C: hbase-client hbase-server U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/6401/console |
| Powered by | Apache Yetus 0.3.0
[jira] [Commented] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966318#comment-15966318
]
Appy commented on HBASE-16775:
--
Pushed to master after updating comments as Jon asked.
> Flakey test with TestExportSnapshot#testExportRetry and
> TestMobExportSnapshot#testExportRetry
> --
>
> Key: HBASE-16775
> URL: https://issues.apache.org/jira/browse/HBASE-16775
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: Appy
> Attachments: disable.patch, HBASE-16775.master.001.patch,
> HBASE-16775.master.002.patch, HBASE-16775.master.003.patch,
> HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
> HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
>
>
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not
> taken by the mapper job, so the retry is actually 0. Debugging to see why
> this is the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Appy updated HBASE-16775:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Flakey test with TestExportSnapshot#testExportRetry and
> TestMobExportSnapshot#testExportRetry
> --
>
> Key: HBASE-16775
> URL: https://issues.apache.org/jira/browse/HBASE-16775
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: Appy
> Attachments: disable.patch, HBASE-16775.master.001.patch,
> HBASE-16775.master.002.patch, HBASE-16775.master.003.patch,
> HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
> HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
>
>
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not
> taken by the mapper job, so the retry is actually 0. Debugging to see why
> this is the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-16215: Status: Patch Available (was: In Progress) > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > Attachments: HBASE-16215.0.patch > > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-16215: Attachment: HBASE-16215.0.patch -00 - updates to ref guide to remove 0.98, 0.94, and 1.0 prereqs - updates ref guide to remove many references to EOM version specific behavior - updates site to remove link to 0.94 docs (but leaves the docs themselves in place to avoid breaking external linkers) > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > Attachments: HBASE-16215.0.patch > > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17879) Avoid NPE in snapshot.jsp when accessing without any request parameter
[ https://issues.apache.org/jira/browse/HBASE-17879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966265#comment-15966265 ] Ted Yu commented on HBASE-17879: I noticed misspelling in the patched case. Can you fix that ? Thanks > Avoid NPE in snapshot.jsp when accessing without any request parameter > -- > > Key: HBASE-17879 > URL: https://issues.apache.org/jira/browse/HBASE-17879 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.3.0 >Reporter: Abhishek Kumar >Priority: Trivial > Attachments: HBASE-17879.patch, NPE_screenshot.png, > patched_screenshot.png > > > When accessing snapshot jsp with below url inadvertently NPE comes in UI: > Requested URL: > http://:/snapshot.jsp? > Response: > java.lang.NullPointerException > at > org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17879) Avoid NPE in snapshot.jsp when accessing without any request parameter
[ https://issues.apache.org/jira/browse/HBASE-17879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966255#comment-15966255 ] Abhishek Kumar commented on HBASE-17879: screenshot attached, pls take a look. > Avoid NPE in snapshot.jsp when accessing without any request parameter > -- > > Key: HBASE-17879 > URL: https://issues.apache.org/jira/browse/HBASE-17879 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.3.0 >Reporter: Abhishek Kumar >Priority: Trivial > Attachments: HBASE-17879.patch, NPE_screenshot.png, > patched_screenshot.png > > > When accessing snapshot jsp with below url inadvertently NPE comes in UI: > Requested URL: > http://:/snapshot.jsp? > Response: > java.lang.NullPointerException > at > org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17879) Avoid NPE in snapshot.jsp when accessing without any request parameter
[ https://issues.apache.org/jira/browse/HBASE-17879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated HBASE-17879: --- Attachment: patched_screenshot.png > Avoid NPE in snapshot.jsp when accessing without any request parameter > -- > > Key: HBASE-17879 > URL: https://issues.apache.org/jira/browse/HBASE-17879 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.3.0 >Reporter: Abhishek Kumar >Priority: Trivial > Attachments: HBASE-17879.patch, NPE_screenshot.png, > patched_screenshot.png > > > When accessing snapshot jsp with below url inadvertently NPE comes in UI: > Requested URL: > http://:/snapshot.jsp? > Response: > java.lang.NullPointerException > at > org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17879) Avoid NPE in snapshot.jsp when accessing without any request parameter
[ https://issues.apache.org/jira/browse/HBASE-17879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated HBASE-17879: --- Attachment: NPE_screenshot.png > Avoid NPE in snapshot.jsp when accessing without any request parameter > -- > > Key: HBASE-17879 > URL: https://issues.apache.org/jira/browse/HBASE-17879 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.3.0 >Reporter: Abhishek Kumar >Priority: Trivial > Attachments: HBASE-17879.patch, NPE_screenshot.png > > > When accessing snapshot jsp with below url inadvertently NPE comes in UI: > Requested URL: > http://:/snapshot.jsp? > Response: > java.lang.NullPointerException > at > org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (HBASE-17393) Logic in TimeRange#includesTimeRange is incorrect
[ https://issues.apache.org/jira/browse/HBASE-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun resolved HBASE-17393. -- Resolution: Invalid The definition of TimeRange is different from the client side and the server side. At the client side, it is [start, end), at the server side, it is [start, end]. Comments have been added at the server side. > Logic in TimeRange#includesTimeRange is incorrect > - > > Key: HBASE-17393 > URL: https://issues.apache.org/jira/browse/HBASE-17393 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Minor > > In the code, > https://github.com/apache/hbase/blob/master/hbase-common/src/main/java/org/apache/hadoop/hbase/io/TimeRange.java#L181 > > return getMin() < tr.getMax() && getMax() >= tr.getMin(); > Given that TimeRange is defined as [minStamp,maxStamp), > Assume that TimeRange(4, 5). includesTimeRange(TimeRange(5,6)). > So it will be (4 < 6) && (5 >=5), the result is true. > Same for TimeRangeTracker#includesTimeRange -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17366) Run TestHFile#testReaderWithoutBlockCache failes
[ https://issues.apache.org/jira/browse/HBASE-17366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966216#comment-15966216 ] huaxiang sun commented on HBASE-17366: -- Hi [~vrodionov], can you help to take a look to see if the v2 patch addresses your comment? Thanks. > Run TestHFile#testReaderWithoutBlockCache failes > > > Key: HBASE-17366 > URL: https://issues.apache.org/jira/browse/HBASE-17366 > Project: HBase > Issue Type: Bug >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-17366-master-001.patch, > HBASE-17366-master-002.patch > > > Running TestHFile#testReaderWithoutBlockCache failes because cacheConf is not > initialized. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17366) Run TestHFile#testReaderWithoutBlockCache failes
[ https://issues.apache.org/jira/browse/HBASE-17366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-17366: - Attachment: HBASE-17366-master-002.patch v2 patch to address review comments. > Run TestHFile#testReaderWithoutBlockCache failes > > > Key: HBASE-17366 > URL: https://issues.apache.org/jira/browse/HBASE-17366 > Project: HBase > Issue Type: Bug >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-17366-master-001.patch, > HBASE-17366-master-002.patch > > > Running TestHFile#testReaderWithoutBlockCache failes because cacheConf is not > initialized. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17301) TestSimpleRpcScheduler#testCoDelScheduling is broken in master
[ https://issues.apache.org/jira/browse/HBASE-17301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966184#comment-15966184 ] huaxiang sun commented on HBASE-17301: -- Thanks [~chia7712] > TestSimpleRpcScheduler#testCoDelScheduling is broken in master > -- > > Key: HBASE-17301 > URL: https://issues.apache.org/jira/browse/HBASE-17301 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Minor > Attachments: HBASE-17301-master-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966179#comment-15966179
]
Appy commented on HBASE-16775:
--
Thanks for reviews [~huaxiang] and [~jmhsieh].
> Flakey test with TestExportSnapshot#testExportRetry and
> TestMobExportSnapshot#testExportRetry
> --
>
> Key: HBASE-16775
> URL: https://issues.apache.org/jira/browse/HBASE-16775
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: Appy
> Attachments: disable.patch, HBASE-16775.master.001.patch,
> HBASE-16775.master.002.patch, HBASE-16775.master.003.patch,
> HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
> HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
>
>
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not
> taken by the mapper job, so the retry is actually 0. Debugging to see why
> this is the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966178#comment-15966178
]
Appy commented on HBASE-16775:
--
bq. Hey Appy, to clarify, when you say they are running parallely, do you mean
that TestExportSnapshot#testConsecutiveExport and TestMobExportSnapshot#
testConsecutiveExport were stepping on each other when run in parallel or do
you mean the different test cases within each Test*ExportSnapshot class (e.g.
TestExportSnapshot#testConsecutiveExport and
TestExportSnapshot#testExportFileSystemStateWithSkipTemp ) were stepping on
each other?
Yes, it's former. Different test classes (Test*ExportSnapshot) stepping on each
other. JUnit does not run test cases within a single Test*.java class in
parallel. They are always sequential.
Your analysis in second comment is absolutely correct. So i'll update the
comment and commit.
bq. As a follow up, is there any reason why this should't always be run
whenever a miniMR cluster is setup?
I have the same question. Don't know. Will ask on slack later and create jira.
> Flakey test with TestExportSnapshot#testExportRetry and
> TestMobExportSnapshot#testExportRetry
> --
>
> Key: HBASE-16775
> URL: https://issues.apache.org/jira/browse/HBASE-16775
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: Appy
> Attachments: disable.patch, HBASE-16775.master.001.patch,
> HBASE-16775.master.002.patch, HBASE-16775.master.003.patch,
> HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
> HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
>
>
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not
> taken by the mapper job, so the retry is actually 0. Debugging to see why
> this is the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-15936) Sort out how to push to apache/ repositories on Docker Hub
[ https://issues.apache.org/jira/browse/HBASE-15936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966172#comment-15966172 ] Cosmin Lehene commented on HBASE-15936: --- [~dimaspivak] got it. I'm actually thinking about supporting a docker based distro (for reference see https://github.com/hstack/elastic-hbase/). If there's interest I'd gladly discuss on a separate issue. > Sort out how to push to apache/ repositories on Docker Hub > -- > > Key: HBASE-15936 > URL: https://issues.apache.org/jira/browse/HBASE-15936 > Project: HBase > Issue Type: Sub-task > Components: build >Reporter: Dima Spivak >Assignee: Dima Spivak > Labels: docker > > It looks like there's already a [Docker Hub username for Apache > stuff|https://hub.docker.com/r/apache/]. We should figure out how to use it > to push the Docker images we use/build for testing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17909) Redundant exclusion of jruby-complete in pom of hbase-spark
[ https://issues.apache.org/jira/browse/HBASE-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966142#comment-15966142 ] Xiang Li commented on HBASE-17909: -- Will upload the patch if the JIRA is valid. > Redundant exclusion of jruby-complete in pom of hbase-spark > --- > > Key: HBASE-17909 > URL: https://issues.apache.org/jira/browse/HBASE-17909 > Project: HBase > Issue Type: Bug > Components: spark >Reporter: Xiang Li >Assignee: Xiang Li >Priority: Minor > > In pom.xml of hbase-spark, jruby-complete is excluded from some of HBase > child modules, there are 2 issues: > 1. jruby-complete is excluded from the following child modules, > - hbase-client > - hbase-hadoop-compat > - hbase-hadoop2-compat > but those child modules does not introduce jruby-complete. jruby-complete is > only introduced by hbase-shell, and by transitive dependency, it is also > introduced by hbase-assembly, as hbase-assembly depends on hbase-shell. > But none of 3 modules listed above introduces jruby-complete. > 2. The exclusion of jruby-complete is stated twice in each of the 3 child > modules listed in 1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17909) Redundant exclusion of jruby-complete in pom of hbase-spark
[ https://issues.apache.org/jira/browse/HBASE-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiang Li updated HBASE-17909: - Description: In pom.xml of hbase-spark, jruby-complete is excluded from some of HBase child modules, there are 2 issues: 1. jruby-complete is excluded from the following child modules, - hbase-client - hbase-hadoop-compat - hbase-hadoop2-compat but those child modules does not introduce jruby-complete. jruby-complete is only introduced by hbase-shell, and by transitive dependency, it is also introduced by hbase-assembly, as hbase-assembly depends on hbase-shell. But none of 3 modules listed above introduces jruby-complete. 2. The exclusion of jruby-complete is stated twice in each of the 3 child modules listed in 1. was: In pom.xml of hbase-spark, jruby-complete is excluded from some of HBase child modules, there are 2 problems: 1. jruby-complete is excluded from the following child modules, - hbase-client - hbase-hadoop-compat - hbase-hadoop2-compat but those child modules does not introduce jruby-complete. jruby-complete is only introduced by hbase-shell, and by transitive dependency, it is also introduced by hbase-assembly, as hbase-assembly depends on hbase-shell. But none of 3 modules listed above introduces jruby-complete. 2. The exclusion of jruby-complete is stated twice in each of the 3 child modules listed in 1. > Redundant exclusion of jruby-complete in pom of hbase-spark > --- > > Key: HBASE-17909 > URL: https://issues.apache.org/jira/browse/HBASE-17909 > Project: HBase > Issue Type: Bug > Components: spark >Reporter: Xiang Li >Assignee: Xiang Li >Priority: Minor > > In pom.xml of hbase-spark, jruby-complete is excluded from some of HBase > child modules, there are 2 issues: > 1. jruby-complete is excluded from the following child modules, > - hbase-client > - hbase-hadoop-compat > - hbase-hadoop2-compat > but those child modules does not introduce jruby-complete. jruby-complete is > only introduced by hbase-shell, and by transitive dependency, it is also > introduced by hbase-assembly, as hbase-assembly depends on hbase-shell. > But none of 3 modules listed above introduces jruby-complete. > 2. The exclusion of jruby-complete is stated twice in each of the 3 child > modules listed in 1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17909) Redundant exclusion of jruby-complete in pom of hbase-spark
[ https://issues.apache.org/jira/browse/HBASE-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966128#comment-15966128 ] Xiang Li commented on HBASE-17909: -- [~ted.m] could those exclusions be removed? > Redundant exclusion of jruby-complete in pom of hbase-spark > --- > > Key: HBASE-17909 > URL: https://issues.apache.org/jira/browse/HBASE-17909 > Project: HBase > Issue Type: Bug > Components: spark >Reporter: Xiang Li >Assignee: Xiang Li >Priority: Minor > > In pom.xml of hbase-spark, jruby-complete is excluded from some of HBase > child modules, there are 2 problems: > 1. jruby-complete is excluded from the following child modules, > - hbase-client > - hbase-hadoop-compat > - hbase-hadoop2-compat > but those child modules does not introduce jruby-complete. jruby-complete is > only introduced by hbase-shell, and by transitive dependency, it is also > introduced by hbase-assembly, as hbase-assembly depends on hbase-shell. > But none of 3 modules listed above introduces jruby-complete. > 2. The exclusion of jruby-complete is stated twice in each of the 3 child > modules listed in 1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17909) Redundant exclusion of jruby-complete in pom of hbase-spark
Xiang Li created HBASE-17909: Summary: Redundant exclusion of jruby-complete in pom of hbase-spark Key: HBASE-17909 URL: https://issues.apache.org/jira/browse/HBASE-17909 Project: HBase Issue Type: Bug Components: spark Reporter: Xiang Li Assignee: Xiang Li Priority: Minor In pom.xml of hbase-spark, jruby-complete is excluded from some of HBase child modules, there are 2 problems: 1. jruby-complete is excluded from the following child modules, - hbase-client - hbase-hadoop-compat - hbase-hadoop2-compat but those child modules does not introduce jruby-complete. jruby-complete is only introduced by hbase-shell, and by transitive dependency, it is also introduced by hbase-assembly, as hbase-assembly depends on hbase-shell. But none of 3 modules listed above introduces jruby-complete. 2. The exclusion of jruby-complete is stated twice in each of the 3 child modules listed in 1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966105#comment-15966105 ] Ted Yu commented on HBASE-17906: HTablePool is gone in master branch, FYI > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Labels: patch > Fix For: 1.2.2, 0.98.21 > > Attachments: HBASE-17906.patch > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17890:
---
Attachment: HBASE-17890.v1.patch
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 2.0.0, 1.2.5
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch,
> HBASE-17890.v1.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17890:
---
Status: Patch Available (was: Open)
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 1.2.5, 2.0.0
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch,
> HBASE-17890.v1.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17890:
---
Status: Open (was: Patch Available)
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 1.2.5, 2.0.0
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[
https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966043#comment-15966043
]
Hadoop QA commented on HBASE-17906:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 20s {color}
| {color:red} HBASE-17906 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12863069/HBASE-17906.patch |
| JIRA Issue | HBASE-17906 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/6400/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> When a huge amount of data writing to hbase through thrift2, there will be a
> deadlock error.
>
>
> Key: HBASE-17906
> URL: https://issues.apache.org/jira/browse/HBASE-17906
> Project: HBase
> Issue Type: Bug
> Components: Client
>Affects Versions: 0.98.21
> Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77
>Reporter: Albert Lee
> Labels: patch
> Fix For: 1.2.2, 0.98.21
>
> Attachments: HBASE-17906.patch
>
>
> When a huge amount of data writing to hbase through thrift2, there will be a
> deadlock error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-15143) Procedure v2 - Web UI displaying queues
[
https://issues.apache.org/jira/browse/HBASE-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966039#comment-15966039
]
Hadoop QA commented on HBASE-15143:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 12s
{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} rubocop {color} | {color:blue} 0m 0s
{color} | {color:blue} rubocop was not available. {color} |
| {color:blue}0{color} | {color:blue} ruby-lint {color} | {color:blue} 0m 0s
{color} | {color:blue} Ruby-lint was not available. {color} |
| {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 6 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 29s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
13s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 56s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
58s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
2s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m 58s
{color} | {color:red} hbase-protocol-shaded in master has 24 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 21s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 11s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
7s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 57s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
59s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
1s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch has 25 line(s) that end in whitespace. Use git
apply --whitespace=fix. {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 1s
{color} | {color:red} The patch 13 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
27m 27s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 1m
33s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
24s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 21s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 45s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 27s
{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 43s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 9s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 105m 56s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m 34s
{color} | {color:green} hbase-shell in the patch passed. {color} |
|
[jira] [Commented] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966040#comment-15966040 ] Ted Yu commented on HBASE-17906: Currently hbase QA bot doesn't check pull requests. Do you mind following http://hbase.apache.org/book.html#submitting.patches and attaching patch here ? > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Labels: patch > Fix For: 1.2.2, 0.98.21 > > Attachments: HBASE-17906.patch > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated HBASE-17906: --- Attachment: HBASE-17906.patch > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Labels: patch > Fix For: 1.2.2, 0.98.21 > > Attachments: HBASE-17906.patch > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated HBASE-17906: --- Labels: patch (was: ) Status: Patch Available (was: Open) https://patch-diff.githubusercontent.com/raw/apache/hbase/pull/48.patch > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Labels: patch > Fix For: 0.98.21, 1.2.2 > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966020#comment-15966020 ] Albert Lee edited comment on HBASE-17906 at 4/12/17 3:11 PM: - I find because the htablePools cache and connection cache have the same timeout. I add a refresh mechanism and it works for me now. Here is my patch https://patch-diff.githubusercontent.com/raw/apache/hbase/pull/48.patch was (Author: albertlee...@gmail.com): I find because the htablePools cache and connection cache have the same timeout. I add a refresh mechanism and it works for me now. > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Fix For: 1.2.2, 0.98.21 > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966020#comment-15966020 ] Albert Lee commented on HBASE-17906: I find because the htablePools cache and connection cache have the same timeout. I add a refresh mechanism and it works for me now. > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Fix For: 1.2.2, 0.98.21 > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966020#comment-15966020 ] Albert Lee edited comment on HBASE-17906 at 4/12/17 3:08 PM: - I find because the htablePools cache and connection cache have the same timeout. I add a refresh mechanism and it works for me now. was (Author: albertlee...@gmail.com): I find because the htablePools cache and connection cache have the same timeout. I add a refresh mechanism and it works for me now. > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Fix For: 1.2.2, 0.98.21 > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966016#comment-15966016
]
Chia-Ping Tsai commented on HBASE-17890:
bq. So here the test code explicitly calls the unsafe path or non unsafe path.
(Non public methods).. We should fix this?
The difference between the "unsafe" and "non unsafe" is the "mask".
|| ||unsafe||non unsafe||
|mask for fixed byte|-1|0|
The failure happen when some tests pass the mask which work for unsafe into the
non unsafe function. So i switch the mask according to the state of unsafe.
bq. As such this patch I felt difficult to read and understand.
Okay. Let me simplify it.
Thanks for the feedback. [~anoop.hbase]
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 2.0.0, 1.2.5
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17878) java.lang.NoSuchMethodError: org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter when starting HBase with hbase.rootdir on S3
[
https://issues.apache.org/jira/browse/HBASE-17878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965987#comment-15965987
]
Xiang Li commented on HBASE-17878:
--
1. The joda-time can not be excluded, or there will be some test failures in
hbase-shell, as Zach mentioned.
2. If joda-time is not excluded, I found another error (when running UT
TestShell),
{code}
testRunShellTests(org.apache.hadoop.hbase.client.TestShell) Time elapsed:
0.119 sec <<< ERROR!
org.jruby.embed.EvalFailedException: (LoadError) no such file to load --
rubygems
at
org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:136)
at
org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1263)
at
org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1308)
at
org.apache.hadoop.hbase.client.TestShell.testRunShellTests(TestShell.java:36)
Caused by: org.jruby.exceptions.RaiseException: (LoadError) no such file to
load -- rubygems
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1062)
at (Anonymous).(root)(src/test/ruby/tests_runner.rb:20)
Results :
Tests in error:
TestShell.testRunShellTests:36 » EvalFailed (LoadError) no such file to load
-...
{code}
My basic idea is to use jruby-core instead of jruby-complete, because
jruby-complete is an all-in-one package, one jar to contains all, while by
using jruby-core, exclusion(joda-time or others) can be performed. But it
appears jruby-complete contains more, other than jruby-core and the
dependencies of jruby-core, at least it contains rubygems.
> java.lang.NoSuchMethodError:
> org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter
> when starting HBase with hbase.rootdir on S3
> -
>
> Key: HBASE-17878
> URL: https://issues.apache.org/jira/browse/HBASE-17878
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-17878.master.000.patch, jruby-core-dep-tree.txt
>
>
> When setting up HBASE-17437 (Support specifying a WAL directory outside of
> the root directory), we specify
> (1) hbase.rootdir on s3a
> (2) hbase.wal.dir on HDFS
> When starting HBase, the following exception is thrown:
> {code}
> Caused by: java.lang.NoSuchMethodError:
> org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter;
> at
> com.amazonaws.auth.internal.AWS4SignerUtils.(AWS4SignerUtils.java:26)
> at
> com.amazonaws.auth.internal.AWS4SignerRequestParams.(AWS4SignerRequestParams.java:85)
> at com.amazonaws.auth.AWS4Signer.sign(AWS4Signer.java:184)
> at
> com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:709)
> at
> com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
> at
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
> at
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
> at
> com.amazonaws.services.s3.AmazonS3Client.headBucket(AmazonS3Client.java:1107)
> at
> com.amazonaws.services.s3.AmazonS3Client.doesBucketExist(AmazonS3Client.java:1070)
> at
> org.apache.hadoop.fs.s3a.S3AFileSystem.initialize(S3AFileSystem.java:232)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2669)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:94)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2703)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2685)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:373)
> at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295)
> at org.apache.hadoop.hbase.util.FSUtils.getRootDir(FSUtils.java:1007)
> at
> org.apache.hadoop.hbase.util.FSUtils.isValidWALRootDir(FSUtils.java:1050)
> at
> org.apache.hadoop.hbase.util.FSUtils.getWALRootDir(FSUtils.java:1032)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.initializeFileSystem(HRegionServer.java:627)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:570)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:393)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
>
[jira] [Commented] (HBASE-17890) FuzzyRow tests fail if unaligned support is false
[
https://issues.apache.org/jira/browse/HBASE-17890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965963#comment-15965963
]
Anoop Sam John commented on HBASE-17890:
So here the test code explicitly calls the unsafe path or non unsafe path. (Non
public methods).. We should fix this? The test code wanted to make sure that
both the paths are executed from UTs. Now we have a way to turn off Unsafe
avail. May be , like u did for some other tests, we will have test here which
uses the public method path alone but have a way to execute tests with Unsafe
toggle?
As such this patch I felt difficult to read and understand.
> FuzzyRow tests fail if unaligned support is false
> -
>
> Key: HBASE-17890
> URL: https://issues.apache.org/jira/browse/HBASE-17890
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 2.0.0, 1.2.5
>Reporter: Jerry He
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.1.10, 1.2.6, 1.3.2
>
> Attachments: HBASE-17890.v0.branch-1.patch, HBASE-17890.v0.patch
>
>
> When unaligned support is false, FuzzyRow tests fail:
> {noformat}
> Failed tests:
> TestFuzzyRowAndColumnRangeFilter.Test:134->runTest:157->runScanner:186
> expected:<10> but was:<0>
> TestFuzzyRowFilter.testSatisfiesForward:81 expected: but was:
> TestFuzzyRowFilter.testSatisfiesReverse:121 expected: but
> was:
> TestFuzzyRowFilterEndToEnd.testEndToEnd:247->runTest1:278->runScanner:343
> expected:<6250> but was:<0>
> TestFuzzyRowFilterEndToEnd.testFilterList:385->runTest:417->runScanner:445
> expected:<5> but was:<0>
> TestFuzzyRowFilterEndToEnd.testHBASE14782:204 expected:<6> but was:<0>
> {noformat}
> This can be reproduced in the case described in HBASE-17869. Or on a platform
> really without unaligned support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965834#comment-15965834 ] Sean Busbey edited comment on HBASE-16215 at 4/12/17 2:18 PM: -- * all but the most recent unreleased JIRA version for each line have been removed (with issues attached to later unreleased versions moved to said version). each has a note about EOM (e.g. there's still a 0.98.25 version and it says the line is EOM) edit: this was poorly phrased. released JIRA versions haven't been changed, just to be clear. was (Author: busbey): * all but the most recent unreleased JIRA version for each line have been removed (with issues attached to later unreleased versions moved to said version). each has a note about EOM (e.g. there's still a 0.98.25 version and it says the line is EOM) > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17878) java.lang.NoSuchMethodError: org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter when starting HBase with hbase.rootdir on S3
[
https://issues.apache.org/jira/browse/HBASE-17878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiang Li updated HBASE-17878:
-
Status: Open (was: Patch Available)
Cancelling the patch and need to think it over. Not as I am expecting.
> java.lang.NoSuchMethodError:
> org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter
> when starting HBase with hbase.rootdir on S3
> -
>
> Key: HBASE-17878
> URL: https://issues.apache.org/jira/browse/HBASE-17878
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-17878.master.000.patch, jruby-core-dep-tree.txt
>
>
> When setting up HBASE-17437 (Support specifying a WAL directory outside of
> the root directory), we specify
> (1) hbase.rootdir on s3a
> (2) hbase.wal.dir on HDFS
> When starting HBase, the following exception is thrown:
> {code}
> Caused by: java.lang.NoSuchMethodError:
> org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter;
> at
> com.amazonaws.auth.internal.AWS4SignerUtils.(AWS4SignerUtils.java:26)
> at
> com.amazonaws.auth.internal.AWS4SignerRequestParams.(AWS4SignerRequestParams.java:85)
> at com.amazonaws.auth.AWS4Signer.sign(AWS4Signer.java:184)
> at
> com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:709)
> at
> com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
> at
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
> at
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
> at
> com.amazonaws.services.s3.AmazonS3Client.headBucket(AmazonS3Client.java:1107)
> at
> com.amazonaws.services.s3.AmazonS3Client.doesBucketExist(AmazonS3Client.java:1070)
> at
> org.apache.hadoop.fs.s3a.S3AFileSystem.initialize(S3AFileSystem.java:232)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2669)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:94)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2703)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2685)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:373)
> at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295)
> at org.apache.hadoop.hbase.util.FSUtils.getRootDir(FSUtils.java:1007)
> at
> org.apache.hadoop.hbase.util.FSUtils.isValidWALRootDir(FSUtils.java:1050)
> at
> org.apache.hadoop.hbase.util.FSUtils.getWALRootDir(FSUtils.java:1032)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.initializeFileSystem(HRegionServer.java:627)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:570)
> at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:393)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2456)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-15583) Any HTableDescriptor we give out should be immutable
[ https://issues.apache.org/jira/browse/HBASE-15583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965909#comment-15965909 ] Chia-Ping Tsai commented on HBASE-15583: Ping~ > Any HTableDescriptor we give out should be immutable > > > Key: HBASE-15583 > URL: https://issues.apache.org/jira/browse/HBASE-15583 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.0.0 >Reporter: Gabor Liptak >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15583.v0.patch, HBASE-15583.v1.patch > > > From [~enis] in https://issues.apache.org/jira/browse/HBASE-15505: > PS Should UnmodifyableHTableDescriptor be renamed to > UnmodifiableHTableDescriptor? > It should be named ImmutableHTableDescriptor to be consistent with > collections naming. Let's do this as a subtask of the parent jira, not here. > Thinking about it though, why would we return an Immutable HTD in > HTable.getTableDescriptor() versus a mutable HTD in > Admin.getTableDescriptor(). It does not make sense. Should we just get rid of > the Immutable ones? > We also have UnmodifyableHRegionInfo which is not used at the moment it > seems. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965877#comment-15965877
]
Jonathan Hsieh commented on HBASE-16775:
Hm.. this is pretty subtle. Looking at the test case and if I understand
correctly, we have different export to directories and different table names in
each case and on the surface the test looks to be doing reasonable things to
try isolate concurrent runs of versions of the test. (and failing because mr
tmp dirs are trampling each other).
This makes most important change in the patch the HTU#getDataTestDir call which
calls HTU#setupDataTestDir which setup MR localizing properties[1].
If that is the case I'm +1 for the patch if you add more comments about this
specific trampling scenario in each place where you currently have this comment
"// This will setup separate directory for use in MR cluster."
As a follow up, is there any reason why this should't always be run whenever a
miniMR cluster is setup?
[1]
https://github.com/apache/hbase/blob/master/hbase-common/src/test/java/org/apache/hadoop/hbase/HBaseCommonTestingUtility.java#L102
> Flakey test with TestExportSnapshot#testExportRetry and
> TestMobExportSnapshot#testExportRetry
> --
>
> Key: HBASE-16775
> URL: https://issues.apache.org/jira/browse/HBASE-16775
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: Appy
> Attachments: disable.patch, HBASE-16775.master.001.patch,
> HBASE-16775.master.002.patch, HBASE-16775.master.003.patch,
> HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
> HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
>
>
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not
> taken by the mapper job, so the retry is actually 0. Debugging to see why
> this is the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-16459) Remove unused hbase shell --format option
[
https://issues.apache.org/jira/browse/HBASE-16459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965846#comment-15965846
]
Chia-Ping Tsai commented on HBASE-16459:
[~dimaspivak] Do you want to commit it?
> Remove unused hbase shell --format option
> -
>
> Key: HBASE-16459
> URL: https://issues.apache.org/jira/browse/HBASE-16459
> Project: HBase
> Issue Type: Task
> Components: shell
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Trivial
> Labels: beginner
> Attachments: HBASE-16459.patch, HBASE-16459_v2.patch
>
>
> The usage information when running {{hbase shell}} refers to a formatter
> option that has yet to implemented in over 8 years and which will ostensibly
> never be implemented. As such, let's cleanup the [help
> message|https://github.com/apache/hbase/blob/master/bin/hirb.rb#L57-L59] and
> remove some extraneous lines of code from
> {{[hirb.rb|https://github.com/apache/hbase/blob/master/bin/hirb.rb#L74-L83]}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (HBASE-17076) implement getAndPut() and getAndDelete()
[ https://issues.apache.org/jira/browse/HBASE-17076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-17076: --- Resolution: Won't Do Status: Resolved (was: Patch Available) > implement getAndPut() and getAndDelete() > > > Key: HBASE-17076 > URL: https://issues.apache.org/jira/browse/HBASE-17076 > Project: HBase > Issue Type: New Feature >Affects Versions: 2.0.0 >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-17076-v0.patch, HBASE-17076-v1.patch, > HBASE-17076-v2.patch, HBASE-17076-v3.patch > > > We implement the getAndPut() and getAndDelete() by coprocessor, but there are > a lot of duplicate effort (e.g., data checks, row lock, returned value, and > wal). It is cool if we provide the compare-and-swap primitive. > The draft patch is attached. Any advice and suggestions will be greatly > appreciated. > Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-16888) Avoid unnecessary tags copy in Append
[
https://issues.apache.org/jira/browse/HBASE-16888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-16888:
---
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
> Avoid unnecessary tags copy in Append
> -
>
> Key: HBASE-16888
> URL: https://issues.apache.org/jira/browse/HBASE-16888
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16888.v0.patch, HBASE-16888.v1.patch,
> HBASE-16888.v1.patch
>
>
> a) If the delta has tags and the mutation doesn’t apply the TTL, we shouldn’t
> create the TagRewriteCell.
> {noformat}
> List tags = TagUtil.carryForwardTags(delta);
> long ts = now;
> Cell newCell = null;
> byte [] row = mutation.getRow();
> if (currentValue != null) {
> ...
> } else {
> // Append's KeyValue.Type==Put and ts==HConstants.LATEST_TIMESTAMP
> CellUtil.updateLatestStamp(delta, now);
> newCell = delta;
> tags = TagUtil.carryForwardTTLTag(tags, mutation.getTTL());
> if (tags != null) {
> newCell = CellUtil.createCell(delta, tags);
> }
> }
> {noformat}
> b) If the cell has tags, the ShareableMemoryTagRewriteCell will make
> duplicate copy of tags.
> {noformat}
> Cell clonedBaseCell = ((ShareableMemory) this.cell).cloneToCell();
> return new TagRewriteCell(clonedBaseCell, this.tags);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-16775) Flakey test with TestExportSnapshot#testExportRetry and TestMobExportSnapshot#testExportRetry
[
https://issues.apache.org/jira/browse/HBASE-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965837#comment-15965837
]
Jonathan Hsieh commented on HBASE-16775:
Hey Appy, to clarify, when you say they are running parallely, do you mean that
TestExportSnapshot#testConsecutiveExport and TestMobExportSnapshot#
testConsecutiveExport were stepping on each other when run in parallel or do
you mean the different test cases within each Test*ExportSnapshot class (e.g.
TestExportSnapshot#testConsecutiveExport and
TestExportSnapshot#testExportFileSystemStateWithSkipTemp ) were stepping on
each other?
I think from the failure report here it is the former case.
https://builds.apache.org/job/PreCommit-HBASE-Build/6337/testReport/
> Flakey test with TestExportSnapshot#testExportRetry and
> TestMobExportSnapshot#testExportRetry
> --
>
> Key: HBASE-16775
> URL: https://issues.apache.org/jira/browse/HBASE-16775
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: huaxiang sun
>Assignee: Appy
> Attachments: disable.patch, HBASE-16775.master.001.patch,
> HBASE-16775.master.002.patch, HBASE-16775.master.003.patch,
> HBASE-16775.master.004.patch, HBASE-16775.master.005.patch,
> HBASE-16775.master.006.patch, HBASE-16775.master.007.patch
>
>
> The root cause is that conf.setInt("mapreduce.map.maxattempts", 10) is not
> taken by the mapper job, so the retry is actually 0. Debugging to see why
> this is the case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17877) Replace/improve HBase's byte[] comparator
[ https://issues.apache.org/jira/browse/HBASE-17877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965838#comment-15965838 ] Anoop Sam John commented on HBASE-17877: FYI. In master, we have similar compare logic in BBUtils also. And we make use of it.. Need similar correction there as well. > Replace/improve HBase's byte[] comparator > - > > Key: HBASE-17877 > URL: https://issues.apache.org/jira/browse/HBASE-17877 > Project: HBase > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Vikas Vishwakarma > Attachments: 17877-1.2.patch, 17877-v2-1.3.patch, > ByteComparatorJiraHBASE-17877.pdf > > > [~vik.karma] did some extensive tests and found that Hadoop's version is > faster - dramatically faster in some cases. > Patch forthcoming. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965836#comment-15965836 ] Sean Busbey commented on HBASE-16215: - * builds.a.o jobs have been disabled (only 0.98 still had some) > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17908) Upgrade guava
[ https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-17908: Description: Currently we are using guava 12.0.1, but the latest version is 21.0. Upgrading guava is always a hassle because it is not always backward compatible with itself. Currently I think there are to approaches: 1. Upgrade guava to the newest version (21.0) and shade it. 2. Upgrade guava to a version which does not break or builds (15.0). If we can update it, some dependencies should be removed: commons-collections, commons-codec, ... was: Currently we are using guava 12.0.1, but the latest version is 21.0. Upgrading guava is always a hassle because it is not always backward compatible with itself. Currently I think there are to approaches: 1. Upgrade guava to the newest version (21.0) and shade it. 2. Upgrade guava to a version which does not break or builds (15.0). > Upgrade guava > - > > Key: HBASE-17908 > URL: https://issues.apache.org/jira/browse/HBASE-17908 > Project: HBase > Issue Type: Sub-task >Reporter: Balazs Meszaros > > Currently we are using guava 12.0.1, but the latest version is 21.0. > Upgrading guava is always a hassle because it is not always backward > compatible with itself. > Currently I think there are to approaches: > 1. Upgrade guava to the newest version (21.0) and shade it. > 2. Upgrade guava to a version which does not break or builds (15.0). > If we can update it, some dependencies should be removed: > commons-collections, commons-codec, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965834#comment-15965834 ] Sean Busbey commented on HBASE-16215: - * all but the most recent unreleased JIRA version for each line have been removed (with issues attached to later unreleased versions moved to said version). each has a note about EOM (e.g. there's still a 0.98.25 version and it says the line is EOM) > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17908) Upgrade guava
Balazs Meszaros created HBASE-17908: --- Summary: Upgrade guava Key: HBASE-17908 URL: https://issues.apache.org/jira/browse/HBASE-17908 Project: HBase Issue Type: Sub-task Reporter: Balazs Meszaros Currently we are using guava 12.0.1, but the latest version is 21.0. Upgrading guava is always a hassle because it is not always backward compatible with itself. Currently I think there are to approaches: 1. Upgrade guava to the newest version (21.0) and shade it. 2. Upgrade guava to a version which does not break or builds (15.0). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965830#comment-15965830 ] Sean Busbey commented on HBASE-16215: - * [asf dist|http://www.apache.org/dist/hbase/] has been updated > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17034) avoid unnecessary Get copy in HTable#exist
[
https://issues.apache.org/jira/browse/HBASE-17034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-17034:
---
Resolution: Not A Problem
Status: Resolved (was: Patch Available)
> avoid unnecessary Get copy in HTable#exist
> --
>
> Key: HBASE-17034
> URL: https://issues.apache.org/jira/browse/HBASE-17034
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-17034.v0.patch
>
>
> {code:title=HTable.java|borderStyle=solid}
> private Result get(Get get, final boolean checkExistenceOnly) throws
> IOException {
> if (get.isCheckExistenceOnly() != checkExistenceOnly ||
> get.getConsistency() == null) {
> get = ReflectionUtils.newInstance(get.getClass(), get);
> get.setCheckExistenceOnly(checkExistenceOnly);
> if (get.getConsistency() == null){
> get.setConsistency(defaultConsistency);
> }
> }
> ...
> }
> {code}
> Can the passed Get be modified? If so, we can just change the passed Get. If
> not, we can record the values returned by isCheckExistenceOnly() and
> getConsistency() for avoiding the Get copy.
> It seems to me that it is ok to modify the passed Get.
> Any comment? Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-16875) Cleanup docs' use of try-with-resources
[
https://issues.apache.org/jira/browse/HBASE-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965823#comment-15965823
]
Chia-Ping Tsai commented on HBASE-16875:
{noformat}
+try (Connection connection = ConnectionFactory.createConnection(conf);
+ Table table = connection.getTable(TableName.valueOf(tablename)) {
{noformat}
lose a right bracket ?
> Cleanup docs' use of try-with-resources
> ---
>
> Key: HBASE-16875
> URL: https://issues.apache.org/jira/browse/HBASE-16875
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Dima Spivak
>Assignee: Jan Hentschel
>Priority: Trivial
> Labels: beginner
> Attachments: HBASE-16875.master.001.patch
>
>
> In a
> [number|https://github.com/apache/hbase/blame/bb3d9ccd489fb64e3cb2020583935a393382a678/src/main/asciidoc/_chapters/security.adoc#L205-L206]
>
> [of|https://github.com/apache/hbase/blame/bb3d9ccd489fb64e3cb2020583935a393382a678/src/main/asciidoc/_chapters/security.adoc#L1019-L1020]
>
> [places|https://github.com/apache/hbase/blame/bb3d9ccd489fb64e3cb2020583935a393382a678/src/main/asciidoc/_chapters/architecture.adoc#L222-L223],
> we show examples that lend themselves to using Java 7's try-with-resources
> statement, but we use the statement in a less-than-ideal nested way. Let's
> change our docs throughout to do it [the recommended
> way|https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Work started] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-16215 started by Sean Busbey. --- > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965797#comment-15965797 ] Sean Busbey commented on HBASE-16215: - updated the description to make clear that we tabled the whole git branch thing. > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-16215) clean up references for EOM release lines
[ https://issues.apache.org/jira/browse/HBASE-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-16215: Description: I've seen us state a few places that 1.0.z is EOM. We should clean up remaining references * remove 1.0.z artifact from dist.apache * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) * remove unreleased 1.0.z versions from JIRA * archive released 1.0.z versions in JIRA edit: expanded to include * 0.94.y [first EOM DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], [second EOM DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] * 0.98.y [EOM DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] was: I've seen us state a few places that 1.0.z is EOM. We should clean up remaining references * remove 1.0.z artifact from dist.apache * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) * remove branch-1.0 from git * remove unreleased 1.0.z versions from JIRA * archive released 1.0.z versions in JIRA edit: expanded to include * 0.94.y [first EOM DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], [second EOM DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] * 0.98.y [EOM DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] > clean up references for EOM release lines > - > > Key: HBASE-16215 > URL: https://issues.apache.org/jira/browse/HBASE-16215 > Project: HBase > Issue Type: Task > Components: community, website >Reporter: Sean Busbey >Assignee: Sean Busbey > > I've seen us state a few places that 1.0.z is EOM. We should clean up > remaining references > * remove 1.0.z artifact from dist.apache > * remove it from the ref guide (java prereqs, hadoop prereqs, RM list) > * remove unreleased 1.0.z versions from JIRA > * archive released 1.0.z versions in JIRA > edit: expanded to include > * 0.94.y [first EOM > DISCUSS|https://lists.apache.org/thread.html/547058fc59cb48130b35c80f86d41c28038195c99f5ed94e834e291c@%3Cdev.hbase.apache.org%3E], > [second EOM > DISCUSS|https://lists.apache.org/thread.html/5ed4ae42ee9be61f963dd0a49f6896fb7771cd8d319d2d86b3c3cc76@%3Cdev.hbase.apache.org%3E] > * 0.98.y [EOM > DISCUSS|https://lists.apache.org/thread.html/fa968458e0f7f224cf906a259448a207b1230548ce6f2c0d50ceeb12@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17301) TestSimpleRpcScheduler#testCoDelScheduling is broken in master
[ https://issues.apache.org/jira/browse/HBASE-17301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-17301: --- Resolution: Duplicate Status: Resolved (was: Patch Available) The bug is fixed by HBASE-17746 > TestSimpleRpcScheduler#testCoDelScheduling is broken in master > -- > > Key: HBASE-17301 > URL: https://issues.apache.org/jira/browse/HBASE-17301 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Minor > Attachments: HBASE-17301-master-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-15143) Procedure v2 - Web UI displaying queues
[ https://issues.apache.org/jira/browse/HBASE-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-15143: Status: Patch Available (was: Open) After rebase, some tests broke. TestInterfaceAudienceAnnotations was fixed, but TestAsyncTableAdminApi was not because it runs on my local machine. > Procedure v2 - Web UI displaying queues > --- > > Key: HBASE-15143 > URL: https://issues.apache.org/jira/browse/HBASE-15143 > Project: HBase > Issue Type: Sub-task > Components: proc-v2, UI >Reporter: Matteo Bertozzi >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15143-BM-0001.patch, HBASE-15143-BM-0002.patch, > HBASE-15143-BM-0003.patch, HBASE-15143-BM-0004.patch, > HBASE-15143-BM-0005.patch, HBASE-15143-BM-0006.patch, > HBASE-15143-BM-0006.patch, HBASE-15143-BM-0007.patch, > HBASE-15143-BM-0008.patch, HBASE-15143-BM-0009.patch, > HBASE-15143-BM-0010.patch, HBASE-15143-BM-0011.patch, screenshot.png > > > We can query MasterProcedureScheduler to display the various procedures and > who is holding table/region locks. > Each procedure is in a TableQueue or ServerQueue, so it is easy to display > the procedures in its own group. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-15143) Procedure v2 - Web UI displaying queues
[ https://issues.apache.org/jira/browse/HBASE-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-15143: Attachment: HBASE-15143-BM-0011.patch > Procedure v2 - Web UI displaying queues > --- > > Key: HBASE-15143 > URL: https://issues.apache.org/jira/browse/HBASE-15143 > Project: HBase > Issue Type: Sub-task > Components: proc-v2, UI >Reporter: Matteo Bertozzi >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15143-BM-0001.patch, HBASE-15143-BM-0002.patch, > HBASE-15143-BM-0003.patch, HBASE-15143-BM-0004.patch, > HBASE-15143-BM-0005.patch, HBASE-15143-BM-0006.patch, > HBASE-15143-BM-0006.patch, HBASE-15143-BM-0007.patch, > HBASE-15143-BM-0008.patch, HBASE-15143-BM-0009.patch, > HBASE-15143-BM-0010.patch, HBASE-15143-BM-0011.patch, screenshot.png > > > We can query MasterProcedureScheduler to display the various procedures and > who is holding table/region locks. > Each procedure is in a TableQueue or ServerQueue, so it is easy to display > the procedures in its own group. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-15143) Procedure v2 - Web UI displaying queues
[ https://issues.apache.org/jira/browse/HBASE-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-15143: Status: Open (was: Patch Available) > Procedure v2 - Web UI displaying queues > --- > > Key: HBASE-15143 > URL: https://issues.apache.org/jira/browse/HBASE-15143 > Project: HBase > Issue Type: Sub-task > Components: proc-v2, UI >Reporter: Matteo Bertozzi >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15143-BM-0001.patch, HBASE-15143-BM-0002.patch, > HBASE-15143-BM-0003.patch, HBASE-15143-BM-0004.patch, > HBASE-15143-BM-0005.patch, HBASE-15143-BM-0006.patch, > HBASE-15143-BM-0006.patch, HBASE-15143-BM-0007.patch, > HBASE-15143-BM-0008.patch, HBASE-15143-BM-0009.patch, > HBASE-15143-BM-0010.patch, screenshot.png > > > We can query MasterProcedureScheduler to display the various procedures and > who is holding table/region locks. > Each procedure is in a TableQueue or ServerQueue, so it is easy to display > the procedures in its own group. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17907) [C++] ScanCallerBuilder
[ https://issues.apache.org/jira/browse/HBASE-17907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-17907: -- Attachment: hbase-17907-v1.patch v1 patch, changes as per above. Also retry timer changes. > [C++] ScanCallerBuilder > --- > > Key: HBASE-17907 > URL: https://issues.apache.org/jira/browse/HBASE-17907 > Project: HBase > Issue Type: Sub-task >Reporter: Enis Soztutar > Fix For: HBASE-14850 > > Attachments: hbase-17907-v1.patch > > > ScanCallerBuilder, related classes and changes needed for scan support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17907) [C++] ScanCallerBuilder
Enis Soztutar created HBASE-17907: - Summary: [C++] ScanCallerBuilder Key: HBASE-17907 URL: https://issues.apache.org/jira/browse/HBASE-17907 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Fix For: HBASE-14850 ScanCallerBuilder, related classes and changes needed for scan support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16438) Create a cell type so that chunk id is embedded in it
[
https://issues.apache.org/jira/browse/HBASE-16438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965628#comment-15965628
]
Hadoop QA commented on HBASE-16438:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 19s
{color} | {color:blue} Docker mode activated. {color} |
| {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 28 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 26s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
4s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 53s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
23s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 44s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 11s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
58s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
40s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
24s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
27m 42s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
40s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 49s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 107m 35s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
30s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 153m 35s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12862980/HBASE-16438_13_ChunkCreatorwrappingChunkPool_withchunkRef.patch
|
| JIRA Issue | HBASE-16438 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 525fecfa32a4 3.13.0-106-generic #153-Ubuntu SMP Tue Dec 6
15:44:32 UTC 2016 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 / cf3215d |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/6398/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/6398/testReport/ |
| modules | C: hbase-common hbase-server U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/6398/console |
|
[jira] [Commented] (HBASE-17879) Avoid NPE in snapshot.jsp when accessing without any request parameter
[ https://issues.apache.org/jira/browse/HBASE-17879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965626#comment-15965626 ] Chia-Ping Tsai commented on HBASE-17879: Would you please attach the screenshots as evidence? > Avoid NPE in snapshot.jsp when accessing without any request parameter > -- > > Key: HBASE-17879 > URL: https://issues.apache.org/jira/browse/HBASE-17879 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.3.0 >Reporter: Abhishek Kumar >Priority: Trivial > Attachments: HBASE-17879.patch > > > When accessing snapshot jsp with below url inadvertently NPE comes in UI: > Requested URL: > http://:/snapshot.jsp? > Response: > java.lang.NullPointerException > at > org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-15535) HBase Reference Guide has an incorrect link for Trafodion
[ https://issues.apache.org/jira/browse/HBASE-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965581#comment-15965581 ] Chia-Ping Tsai commented on HBASE-15535: These failed tests are unrelated to the patch. [~stack] Any more comments? > HBase Reference Guide has an incorrect link for Trafodion > - > > Key: HBASE-15535 > URL: https://issues.apache.org/jira/browse/HBASE-15535 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 2.0.0 >Reporter: Atanu Mishra >Assignee: Gabor Liptak >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15535.1.patch > > > Appendix F in the HBase Reference Guide available here > (https://hbase.apache.org/book.html#sql) has an incorrect link to the site > for Trafodion. > The new Trafodion URL is: http://trafodion.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated HBASE-17906: --- Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 (was: hadoop 2.5.2) > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2, hbase 0.98.20 jdk1.8.0_77 >Reporter: Albert Lee > Fix For: 1.2.2, 0.98.21 > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
[ https://issues.apache.org/jira/browse/HBASE-17906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated HBASE-17906: --- Description: When a huge amount of data writing to hbase through thrift2, there will be a deadlock error. > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. > > > Key: HBASE-17906 > URL: https://issues.apache.org/jira/browse/HBASE-17906 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.98.21 > Environment: hadoop 2.5.2 >Reporter: Albert Lee > Fix For: 1.2.2, 0.98.21 > > > When a huge amount of data writing to hbase through thrift2, there will be a > deadlock error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17906) When a huge amount of data writing to hbase through thrift2, there will be a deadlock error.
Albert Lee created HBASE-17906: -- Summary: When a huge amount of data writing to hbase through thrift2, there will be a deadlock error. Key: HBASE-17906 URL: https://issues.apache.org/jira/browse/HBASE-17906 Project: HBase Issue Type: Bug Components: Client Affects Versions: 0.98.21 Environment: hadoop 2.5.2 Reporter: Albert Lee Fix For: 0.98.21, 1.2.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-15535) HBase Reference Guide has an incorrect link for Trafodion
[
https://issues.apache.org/jira/browse/HBASE-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965554#comment-15965554
]
Hadoop QA commented on HBASE-15535:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 31s
{color} | {color:blue} Docker mode activated. {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} 7m
38s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
11s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m 19s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
50s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 4s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
66m 45s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha2. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m 6s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 135m 28s
{color} | {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
39s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 236m 5s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient |
| | org.apache.hadoop.hbase.client.TestSnapshotFromClient |
| | org.apache.hadoop.hbase.TestPartialResultsFromClientSide |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12796185/HBASE-15535.1.patch |
| JIRA Issue | HBASE-15535 |
| Optional Tests | asflicense javac javadoc unit xml |
| uname | Linux 27239f9f156b 4.8.3-std-1 #1 SMP Fri Oct 21 11:15:43 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / cf3215d |
| Default Java | 1.8.0_121 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/6397/artifact/patchprocess/patch-unit-root.txt
|
| unit test logs |
https://builds.apache.org/job/PreCommit-HBASE-Build/6397/artifact/patchprocess/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/6397/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/6397/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> HBase Reference Guide has an incorrect link for Trafodion
> -
>
> Key: HBASE-15535
> URL: https://issues.apache.org/jira/browse/HBASE-15535
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.0.0
>Reporter: Atanu Mishra
>Assignee: Gabor Liptak
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-15535.1.patch
>
>
> Appendix F in the HBase Reference Guide available here
> (https://hbase.apache.org/book.html#sql) has an incorrect link to the site
> for Trafodion.
> The new Trafodion URL is: http://trafodion.incubator.apache.org/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17895) TestAsyncProcess#testAction fails if unsafe support is false
[
https://issues.apache.org/jira/browse/HBASE-17895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965538#comment-15965538
]
Hudson commented on HBASE-17895:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2843 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/2843/])
HBASE-17895 TestAsyncProcess#testAction fails if unsafe support is false
(chia7712: rev 23249eb0f5466b3608d80847b398b38b698fcf95)
* (edit)
hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestAsyncProcess.java
> TestAsyncProcess#testAction fails if unsafe support is false
>
>
> Key: HBASE-17895
> URL: https://issues.apache.org/jira/browse/HBASE-17895
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Affects Versions: 2.0.0
>Reporter: Chia-Ping Tsai
>Assignee: Wen-Hsiu,Chang
>Priority: Trivial
> Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-17895-v0.patch, HBASE-17895-v1.patch
>
>
> {noformat}
> assertEquals(-1, action_0.compareTo(action_1));
> assertEquals(1, action_1.compareTo(action_0));
> {noformat}
> The correction is shown below.
> {noformat}
> assertTrue(action_0.compareTo(action_1) < 0);
> assertTrue(action_1.compareTo(action_0) > 0);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17896) The FIXED_OVERHEAD of Segment is incorrect
[
https://issues.apache.org/jira/browse/HBASE-17896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965537#comment-15965537
]
Hudson commented on HBASE-17896:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2843 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/2843/])
HBASE-17896 The FIXED_OVERHEAD of Segment is incorrect (chia7712: rev
3aadc675b0f02c3c13be625b40d72fbf6a844964)
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java
* (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/ClassSize.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Segment.java
> The FIXED_OVERHEAD of Segment is incorrect
> --
>
> Key: HBASE-17896
> URL: https://issues.apache.org/jira/browse/HBASE-17896
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-17896.v0.patch, HBASE-17896.v1.patch
>
>
> {noformat}
> 5 * ClassSize.REFERENCE // cellSet, comparator, memStoreLAB, size,
> timeRangeTracker
> {noformat}
> In fact, the Segment has 6 references.
> # cellSet
> # comparator
> # memStoreLAB
> # dataSize
> # heapSize
> # timeRangeTracker
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
