[jira] [Commented] (HBASE-18264) Update pom plugins
[
https://issues.apache.org/jira/browse/HBASE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071526#comment-16071526
]
Hadoop QA commented on HBASE-18264:
---
| (x) *{color:red}-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} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
24s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 11m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 7m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 8m
1s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 10m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 9m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
15s{color} | {color:green} hbase-common generated 0 new + 26 unchanged - 26
fixed = 26 total (was 52) {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
29s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
9s{color} | {color:green} hbase-metrics-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
11s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
9s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
9s{color} | {color:green} hbase-metrics in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
11s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
18s{color} | {color:green} hbase-protocol in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
18s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
10s{color} | {color:green} hbase-prefix-tree in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
38s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
21s{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
16s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
13s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
15s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
16s{color} | {color:green} hbase-it in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
14s{color} | {color:green} hbase-examples in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
17s{color} | {color:green} hbase-rest in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
11s{color} | {color:green} hbase-external-blockcache in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
53s{color} | {color:green}
[jira] [Updated] (HBASE-17537) Remove Queue#isAvailable() since we have waits/wakes after HBASE-17067
[
https://issues.apache.org/jira/browse/HBASE-17537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-17537:
--
Status: Open (was: Patch Available)
> Remove Queue#isAvailable() since we have waits/wakes after HBASE-17067
> --
>
> Key: HBASE-17537
> URL: https://issues.apache.org/jira/browse/HBASE-17537
> Project: HBase
> Issue Type: Sub-task
> Components: master, proc-v2
>Reporter: Appy
>Assignee: Appy
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-17537.master.001.patch,
> HBASE-17537.master.002.patch
>
>
> Earlier, run-queues could have empty queues or queues for which exclusive
> locks are already taken. Thus poll() on table/server run-queue might have
> returned a Queue which didn't have any valid procs to run.
> With wait/wake on exclusive locks doing {removeFrom|addTo}RunQueue and poll
> removing queues when last element is removed, i think we can remove this
> function now.
> (am finding these things when working on a larger patch, but there are
> changes like this which seem too critical to mess up, so am creating smaller
> focused patches for them).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-11993) Expose the set of tables available in TableStateManager
[ https://issues.apache.org/jira/browse/HBASE-11993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-11993: -- Resolution: Won't Fix Fix Version/s: (was: 2.0.0) Status: Resolved (was: Patch Available) This is all different now. Resolving as won't fix. > Expose the set of tables available in TableStateManager > --- > > Key: HBASE-11993 > URL: https://issues.apache.org/jira/browse/HBASE-11993 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 2.0.0 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Trivial > Attachments: HBASE-11993-v0.patch > > > TableStateManager has the full set of TableNames already in memory, > we should expose the set of table names and use it instead of going to query > the fs descriptors. > (Is there any reason why we don't have the descriptors in-memory too? saving > memory with tons of tables? do we even support tons of tables?) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18264) Update pom plugins
[ https://issues.apache.org/jira/browse/HBASE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18264: -- Attachment: HBASE-18264.master.003.patch Retry. Flakies claims this MasterWAL fails 25% of the time. This patch is unlucky. > Update pom plugins > -- > > Key: HBASE-18264 > URL: https://issues.apache.org/jira/browse/HBASE-18264 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: Peter Somogyi > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18264.master.001.patch, > HBASE-18264.master.002.patch, HBASE-18264.master.003.patch, > HBASE-18264.master.003.patch, HBASE-18264.master.003.patch, > HBASE-18264.master.003.patch > > > A bunch are old. Lets update. [~balazs.meszaros] you want to have a go at > this sir? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15702) Improve PerClientRandomNonceGenerator
[
https://issues.apache.org/jira/browse/HBASE-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071508#comment-16071508
]
Hadoop QA commented on HBASE-15702:
---
| (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 7s{color}
| {color:red} HBASE-15702 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-15702 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12801400/HBASE-15702_v4.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7451/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Improve PerClientRandomNonceGenerator
> -
>
> Key: HBASE-15702
> URL: https://issues.apache.org/jira/browse/HBASE-15702
> Project: HBase
> Issue Type: Improvement
>Reporter: Hiroshi Ikeda
>Assignee: Heng Chen
>Priority: Trivial
> Attachments: HBASE-15702.patch, HBASE-15702_v1.patch,
> HBASE-15702_v2.patch, HBASE-15702_v3.patch, HBASE-15702_v4.patch
>
>
> PerClientRandomNonceGenerator can be exposed to all the threads via the
> static field ConnectionManager.nonceGenerator, but
> PerClientRandomNonceGenerator uses Random, which should be ThreadLocalRandom
> or something. (See javadoc of Random.)
> Moreover, ConnectionManager creates or refers the singleton instance of
> PerClientThreadLocalRandom with a lock or volatile, but it should be created
> as a static final field in PerClientThreadLocalRandom itself, and the
> creation will be postponed until the field is actually refereed and the class
> is being initialized.
> The same can be said for ConnectionManager.NoNonceGenerator.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-15702) Improve PerClientRandomNonceGenerator
[ https://issues.apache.org/jira/browse/HBASE-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071505#comment-16071505 ] stack commented on HBASE-15702: --- Any hope of finishing this one up [~chenheng] You and [~ikeda] had a good thing going. > Improve PerClientRandomNonceGenerator > - > > Key: HBASE-15702 > URL: https://issues.apache.org/jira/browse/HBASE-15702 > Project: HBase > Issue Type: Improvement >Reporter: Hiroshi Ikeda >Assignee: Heng Chen >Priority: Trivial > Attachments: HBASE-15702.patch, HBASE-15702_v1.patch, > HBASE-15702_v2.patch, HBASE-15702_v3.patch, HBASE-15702_v4.patch > > > PerClientRandomNonceGenerator can be exposed to all the threads via the > static field ConnectionManager.nonceGenerator, but > PerClientRandomNonceGenerator uses Random, which should be ThreadLocalRandom > or something. (See javadoc of Random.) > Moreover, ConnectionManager creates or refers the singleton instance of > PerClientThreadLocalRandom with a lock or volatile, but it should be created > as a static final field in PerClientThreadLocalRandom itself, and the > creation will be postponed until the field is actually refereed and the class > is being initialized. > The same can be said for ConnectionManager.NoNonceGenerator. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-15702) Improve PerClientRandomNonceGenerator
[ https://issues.apache.org/jira/browse/HBASE-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-15702: - Assignee: Heng Chen > Improve PerClientRandomNonceGenerator > - > > Key: HBASE-15702 > URL: https://issues.apache.org/jira/browse/HBASE-15702 > Project: HBase > Issue Type: Improvement >Reporter: Hiroshi Ikeda >Assignee: Heng Chen >Priority: Trivial > Attachments: HBASE-15702.patch, HBASE-15702_v1.patch, > HBASE-15702_v2.patch, HBASE-15702_v3.patch, HBASE-15702_v4.patch > > > PerClientRandomNonceGenerator can be exposed to all the threads via the > static field ConnectionManager.nonceGenerator, but > PerClientRandomNonceGenerator uses Random, which should be ThreadLocalRandom > or something. (See javadoc of Random.) > Moreover, ConnectionManager creates or refers the singleton instance of > PerClientThreadLocalRandom with a lock or volatile, but it should be created > as a static final field in PerClientThreadLocalRandom itself, and the > creation will be postponed until the field is actually refereed and the class > is being initialized. > The same can be said for ConnectionManager.NoNonceGenerator. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-15702) Improve PerClientRandomNonceGenerator
[ https://issues.apache.org/jira/browse/HBASE-15702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15702: -- Fix Version/s: (was: 2.0.0) > Improve PerClientRandomNonceGenerator > - > > Key: HBASE-15702 > URL: https://issues.apache.org/jira/browse/HBASE-15702 > Project: HBase > Issue Type: Improvement >Reporter: Hiroshi Ikeda >Priority: Trivial > Attachments: HBASE-15702.patch, HBASE-15702_v1.patch, > HBASE-15702_v2.patch, HBASE-15702_v3.patch, HBASE-15702_v4.patch > > > PerClientRandomNonceGenerator can be exposed to all the threads via the > static field ConnectionManager.nonceGenerator, but > PerClientRandomNonceGenerator uses Random, which should be ThreadLocalRandom > or something. (See javadoc of Random.) > Moreover, ConnectionManager creates or refers the singleton instance of > PerClientThreadLocalRandom with a lock or volatile, but it should be created > as a static final field in PerClientThreadLocalRandom itself, and the > creation will be postponed until the field is actually refereed and the class > is being initialized. > The same can be said for ConnectionManager.NoNonceGenerator. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-12031) Parallel Scanners inside Region
[
https://issues.apache.org/jira/browse/HBASE-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071502#comment-16071502
]
Hadoop QA commented on HBASE-12031:
---
| (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 4s{color}
| {color:red} HBASE-12031 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-12031 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12670749/HBASE-12031.3.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7449/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Parallel Scanners inside Region
> ---
>
> Key: HBASE-12031
> URL: https://issues.apache.org/jira/browse/HBASE-12031
> Project: HBase
> Issue Type: New Feature
> Components: Performance, Scanners
>Affects Versions: 0.98.6
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
> Attachments: HBASE-12031.2.patch, HBASE-12031.3.patch,
> HBASE-12031.patch, hbase-12031-tests.tar.gz, ParallelScannerDesign.pdf
>
>
> This JIRA to improve performance of multiple scanners running on a same
> region in parallel. The scenarios where we will get the performance benefits:
> * New TableInputFormat with input splits smaller than HBase Region.
> * Scanning during compaction (Compaction scanner and application scanner over
> the same Region).
> Some JIRAs related to this one:
> https://issues.apache.org/jira/browse/HBASE-7336
> https://issues.apache.org/jira/browse/HBASE-5979
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-10390) expose checkAndPut/Delete custom comparators in HTable
[
https://issues.apache.org/jira/browse/HBASE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071503#comment-16071503
]
Hadoop QA commented on HBASE-10390:
---
| (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 7s{color}
| {color:red} HBASE-10390 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-10390 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12777557/HBASE-10390-v3.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7448/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> expose checkAndPut/Delete custom comparators in HTable
> --
>
> Key: HBASE-10390
> URL: https://issues.apache.org/jira/browse/HBASE-10390
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Sergey Shelukhin
>Assignee: Vladimir Rodionov
> Attachments: HBASE-10390-v1.patch, HBASE-10390-v2.patch,
> HBASE-10390-v3.patch
>
>
> checkAndPut/Delete appear to support custom comparators. However, thru
> HTable, there's no way to pass one, it always creates BinaryComparator from
> value. It would be good to expose the custom ones in the API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-10147) Canary additions
[
https://issues.apache.org/jira/browse/HBASE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071504#comment-16071504
]
Hadoop QA commented on HBASE-10147:
---
| (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 4s{color}
| {color:red} HBASE-10147 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-10147 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12622175/HBASE-10147-v5.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7450/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Canary additions
>
>
> Key: HBASE-10147
> URL: https://issues.apache.org/jira/browse/HBASE-10147
> Project: HBase
> Issue Type: Improvement
>Reporter: stack
>Assignee: Gustavo Anatoly
> Attachments: HBASE-10147.patch, HBASE-10147.patch, HBASE-10147.patch,
> HBASE-10147.patch, HBASE-10147-v2.patch, HBASE-10147-v3.patch,
> HBASE-10147-v4.patch, HBASE-10147-v5.patch
>
>
> I've been using the canary to quickly identify the dodgy machine in my
> cluster. It is useful for this. What would make it better would be:
> + Rather than saying how long it took to get a region after you have gotten
> the region, it'd be sweet to log BEFORE you went to get the region the
> regionname and the server it is on. I ask for this because as is, I have to
> wait for the canary to timeout which can be a while.
> + Second ask is that when I pass the -t, that when it fails, it says what it
> failed against -- what region and hopefully what server location (might be
> hard).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-16730) Exclude junit as a transitive dependency from hadoop-common
[ https://issues.apache.org/jira/browse/HBASE-16730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-16730: -- Attachment: HBASE-16730.master.002.patch Retry. Not sure why it didn't pick up last time. > Exclude junit as a transitive dependency from hadoop-common > --- > > Key: HBASE-16730 > URL: https://issues.apache.org/jira/browse/HBASE-16730 > Project: HBase > Issue Type: Improvement > Components: hbase >Reporter: Nils Larsgård >Assignee: Jan Hentschel >Priority: Trivial > Labels: hbase-client, junit > Fix For: 2.0.0 > > Attachments: HBASE-16730.master.001.patch, > HBASE-16730.master.002.patch, HBASE-16730.master.002.patch, > HBASE-16730.master.002.patch > > Original Estimate: 20m > Remaining Estimate: 20m > > add exclusion to the hadoop-common dependency in hbase-client: exclude junit -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12031) Parallel Scanners inside Region
[ https://issues.apache.org/jira/browse/HBASE-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12031: -- Fix Version/s: (was: 2.0.0) > Parallel Scanners inside Region > --- > > Key: HBASE-12031 > URL: https://issues.apache.org/jira/browse/HBASE-12031 > Project: HBase > Issue Type: New Feature > Components: Performance, Scanners >Affects Versions: 0.98.6 >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-12031.2.patch, HBASE-12031.3.patch, > HBASE-12031.patch, hbase-12031-tests.tar.gz, ParallelScannerDesign.pdf > > > This JIRA to improve performance of multiple scanners running on a same > region in parallel. The scenarios where we will get the performance benefits: > * New TableInputFormat with input splits smaller than HBase Region. > * Scanning during compaction (Compaction scanner and application scanner over > the same Region). > Some JIRAs related to this one: > https://issues.apache.org/jira/browse/HBASE-7336 > https://issues.apache.org/jira/browse/HBASE-5979 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-12031) Parallel Scanners inside Region
[ https://issues.apache.org/jira/browse/HBASE-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071499#comment-16071499 ] stack commented on HBASE-12031: --- Unscheduling. No progress made in years. > Parallel Scanners inside Region > --- > > Key: HBASE-12031 > URL: https://issues.apache.org/jira/browse/HBASE-12031 > Project: HBase > Issue Type: New Feature > Components: Performance, Scanners >Affects Versions: 0.98.6 >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-12031.2.patch, HBASE-12031.3.patch, > HBASE-12031.patch, hbase-12031-tests.tar.gz, ParallelScannerDesign.pdf > > > This JIRA to improve performance of multiple scanners running on a same > region in parallel. The scenarios where we will get the performance benefits: > * New TableInputFormat with input splits smaller than HBase Region. > * Scanning during compaction (Compaction scanner and application scanner over > the same Region). > Some JIRAs related to this one: > https://issues.apache.org/jira/browse/HBASE-7336 > https://issues.apache.org/jira/browse/HBASE-5979 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-10390) expose checkAndPut/Delete custom comparators in HTable
[ https://issues.apache.org/jira/browse/HBASE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071497#comment-16071497 ] stack commented on HBASE-10390: --- Unscheduling from 2.0.0. No work done since 2015. > expose checkAndPut/Delete custom comparators in HTable > -- > > Key: HBASE-10390 > URL: https://issues.apache.org/jira/browse/HBASE-10390 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Vladimir Rodionov > Attachments: HBASE-10390-v1.patch, HBASE-10390-v2.patch, > HBASE-10390-v3.patch > > > checkAndPut/Delete appear to support custom comparators. However, thru > HTable, there's no way to pass one, it always creates BinaryComparator from > value. It would be good to expose the custom ones in the API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-10390) expose checkAndPut/Delete custom comparators in HTable
[ https://issues.apache.org/jira/browse/HBASE-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10390: -- Fix Version/s: (was: 2.0.0) > expose checkAndPut/Delete custom comparators in HTable > -- > > Key: HBASE-10390 > URL: https://issues.apache.org/jira/browse/HBASE-10390 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Sergey Shelukhin >Assignee: Vladimir Rodionov > Attachments: HBASE-10390-v1.patch, HBASE-10390-v2.patch, > HBASE-10390-v3.patch > > > checkAndPut/Delete appear to support custom comparators. However, thru > HTable, there's no way to pass one, it always creates BinaryComparator from > value. It would be good to expose the custom ones in the API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-10147) Canary additions
[ https://issues.apache.org/jira/browse/HBASE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10147: -- Fix Version/s: (was: 2.0.0) > Canary additions > > > Key: HBASE-10147 > URL: https://issues.apache.org/jira/browse/HBASE-10147 > Project: HBase > Issue Type: Improvement >Reporter: stack >Assignee: Gustavo Anatoly > Attachments: HBASE-10147.patch, HBASE-10147.patch, HBASE-10147.patch, > HBASE-10147.patch, HBASE-10147-v2.patch, HBASE-10147-v3.patch, > HBASE-10147-v4.patch, HBASE-10147-v5.patch > > > I've been using the canary to quickly identify the dodgy machine in my > cluster. It is useful for this. What would make it better would be: > + Rather than saying how long it took to get a region after you have gotten > the region, it'd be sweet to log BEFORE you went to get the region the > regionname and the server it is on. I ask for this because as is, I have to > wait for the canary to timeout which can be a while. > + Second ask is that when I pass the -t, that when it fails, it says what it > failed against -- what region and hopefully what server location (might be > hard). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-10147) Canary additions
[ https://issues.apache.org/jira/browse/HBASE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071496#comment-16071496 ] stack commented on HBASE-10147: --- Patch has gone stale (my fault). Code is different now. Unscheduling unless gets picked up for a rebase (still a good idea) > Canary additions > > > Key: HBASE-10147 > URL: https://issues.apache.org/jira/browse/HBASE-10147 > Project: HBase > Issue Type: Improvement >Reporter: stack >Assignee: Gustavo Anatoly > Fix For: 2.0.0 > > Attachments: HBASE-10147.patch, HBASE-10147.patch, HBASE-10147.patch, > HBASE-10147.patch, HBASE-10147-v2.patch, HBASE-10147-v3.patch, > HBASE-10147-v4.patch, HBASE-10147-v5.patch > > > I've been using the canary to quickly identify the dodgy machine in my > cluster. It is useful for this. What would make it better would be: > + Rather than saying how long it took to get a region after you have gotten > the region, it'd be sweet to log BEFORE you went to get the region the > regionname and the server it is on. I ask for this because as is, I have to > wait for the canary to timeout which can be a while. > + Second ask is that when I pass the -t, that when it fails, it says what it > failed against -- what region and hopefully what server location (might be > hard). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18264) Update pom plugins
[
https://issues.apache.org/jira/browse/HBASE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071495#comment-16071495
]
Hadoop QA commented on HBASE-18264:
---
| (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} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
13s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 9m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 5m
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 6m
17s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
13s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 9m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 9m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 9m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 5m
34s{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
31s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
29m 0s{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-alpha3. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 6m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
23s{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} 0m
10s{color} | {color:green} hbase-metrics-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
2s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
22s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
16s{color} | {color:green} hbase-metrics in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
27s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
17s{color} | {color:green} hbase-protocol in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
43s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
25s{color} | {color:green} hbase-prefix-tree in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}114m 57s{color}
| {color:red} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m
59s{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
31s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 7m
5s{color} | {color:green} hbase-shell in the patch passed.
[jira] [Commented] (HBASE-18301) Procedure V2 (AM) - Enable TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster that was disabled by HBASE-14614
[
https://issues.apache.org/jira/browse/HBASE-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071494#comment-16071494
]
Hadoop QA commented on HBASE-18301:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
23s{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} 8m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
56s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 7m
20s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
34s{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}
73m 21s{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-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 7m
50s{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:red}-1{color} | {color:red} unit {color} | {color:red}166m 54s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
0s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}278m 44s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestRegionReplicaFailover |
| | hadoop.hbase.regionserver.TestPerColumnFamilyFlush |
| | hadoop.hbase.security.access.TestCoprocessorWhitelistMasterObserver |
| | hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort |
| Timed out junit tests |
org.apache.hadoop.hbase.replication.regionserver.TestWALEntryStream |
| |
org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDefaultVisLabelService
|
| | org.apache.hadoop.hbase.quotas.TestSpaceQuotas |
| | org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithACL |
| |
org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDeletes |
| | org.apache.hadoop.hbase.replication.TestReplicationSmallTests |
| | org.apache.hadoop.hbase.filter.TestFuzzyRowFilterEndToEnd |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18301 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875390/HBASE-18301.v1-master.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 517e126f5477 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
[jira] [Commented] (HBASE-15806) An endpoint-based export tool
[ https://issues.apache.org/jira/browse/HBASE-15806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071489#comment-16071489 ] stack commented on HBASE-15806: --- Missing from release note is advantage of going this route. You have it in rb. Stick it in release note too. Added a few comments on rb. > An endpoint-based export tool > - > > Key: HBASE-15806 > URL: https://issues.apache.org/jira/browse/HBASE-15806 > Project: HBase > Issue Type: New Feature >Affects Versions: 2.0.0 >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Critical > Fix For: 2.0.0 > > Attachments: Experiment.png, HBASE-15806.patch, HBASE-15806-v1.patch, > HBASE-15806-v2.patch, HBASE-15806-v3.patch, HBASE-15806.v4.patch, > HBASE-15806.v5.patch, HBASE-15806.v6.patch, HBASE-15806.v7.patch > > > The time for exporting table can be reduced, if we use the endpoint technique > to export the hdfs files by the region server rather than by hbase client. > In my experiments, the elapsed time of endpoint-based export can be less than > half of current export tool (enable the hdfs compression) > But the shortcomings is we need to alter table for deploying the endpoint > any comments about this? thanks -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18307) Share the same EventLoopGroup for NettyRpcServer, NettyRpcClient and AsyncFSWALProvider at RS side
Duo Zhang created HBASE-18307: - Summary: Share the same EventLoopGroup for NettyRpcServer, NettyRpcClient and AsyncFSWALProvider at RS side Key: HBASE-18307 URL: https://issues.apache.org/jira/browse/HBASE-18307 Project: HBase Issue Type: Improvement Components: io, rpc, wal Affects Versions: 2.0.0-alpha-1, 3.0.0 Reporter: Duo Zhang Fix For: 3.0.0, 2.0.0-alpha-2 Need a find a proper way to pass a EventLoopGroup instance through a Configuration object. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18283) Provide a construct method which accept a thread pool for AsyncAdmin
[ https://issues.apache.org/jira/browse/HBASE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071478#comment-16071478 ] Duo Zhang commented on HBASE-18283: --- Are the failed UTs related? [~zghaobac] > Provide a construct method which accept a thread pool for AsyncAdmin > > > Key: HBASE-18283 > URL: https://issues.apache.org/jira/browse/HBASE-18283 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 3.0.0, 2.0.0-alpha-2 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18283.master.001.patch, > HBASE-18283.master.002.patch > > > Similar to AsyncTable, provide a construct method which accept a thread pool > for normal user. User need provide a thread pool to get a AsyncAdmin > instance. Then the callbacks registered to the returned CompletableFuture can > be executed in that thread pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-11707) Using Map instead of list in FailedServers of RpcClient
[
https://issues.apache.org/jira/browse/HBASE-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071458#comment-16071458
]
Hudson commented on HBASE-11707:
FAILURE: Integrated in Jenkins build HBase-2.0 #141 (See
[https://builds.apache.org/job/HBase-2.0/141/])
HBASE-11707 Using Map instead of list in FailedServers of RpcClient (Liu
(stack: rev f4c99a6a89b8c766eb4617df7c2e1520f56d209b)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/FailedServers.java
> Using Map instead of list in FailedServers of RpcClient
> ---
>
> Key: HBASE-11707
> URL: https://issues.apache.org/jira/browse/HBASE-11707
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-11707.master.001.patch, HBASE-11707-trunk-v1.diff,
> HBASE-11707-trunk-v2.diff
>
>
> Currently, FailedServers uses a list to record the black list of servers and
> iterate the list to check if a server is in list. It's not efficient when the
> list is very large. And the list is not thread safe for the add and iteration
> operations.
> RpcClient.java#175
> {code}
> // iterate, looking for the search entry and cleaning expired entries
> Iterator> it = failedServers.iterator();
> while (it.hasNext()) {
> Pair cur = it.next();
> if (cur.getFirst() < now) {
> it.remove();
> } else {
> if (lookup.equals(cur.getSecond())) {
> return true;
> }
> }
> {code}
> A simple change is to change this list to ConcurrentHashMap.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-11707) Using Map instead of list in FailedServers of RpcClient
[
https://issues.apache.org/jira/browse/HBASE-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071456#comment-16071456
]
Hudson commented on HBASE-11707:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3294 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3294/])
HBASE-11707 Using Map instead of list in FailedServers of RpcClient (Liu
(stack: rev f1b97a6aa0206636cdfeafaad70af914e91979d3)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/FailedServers.java
> Using Map instead of list in FailedServers of RpcClient
> ---
>
> Key: HBASE-11707
> URL: https://issues.apache.org/jira/browse/HBASE-11707
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-11707.master.001.patch, HBASE-11707-trunk-v1.diff,
> HBASE-11707-trunk-v2.diff
>
>
> Currently, FailedServers uses a list to record the black list of servers and
> iterate the list to check if a server is in list. It's not efficient when the
> list is very large. And the list is not thread safe for the add and iteration
> operations.
> RpcClient.java#175
> {code}
> // iterate, looking for the search entry and cleaning expired entries
> Iterator> it = failedServers.iterator();
> while (it.hasNext()) {
> Pair cur = it.next();
> if (cur.getFirst() < now) {
> it.remove();
> } else {
> if (lookup.equals(cur.getSecond())) {
> return true;
> }
> }
> {code}
> A simple change is to change this list to ConcurrentHashMap.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18301) Procedure V2 (AM) - Enable TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster that was disabled by HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18301: -- Attachment: HBASE-18301.v1-master.patch Failures seem unrelated. Retry. +1 if passes [~syuanjiang] > Procedure V2 (AM) - Enable > TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster > that was disabled by HBASE-14614 > - > > Key: HBASE-18301 > URL: https://issues.apache.org/jira/browse/HBASE-18301 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Fix For: 2.0.0 > > Attachments: HBASE-18301.v1-master.patch, HBASE-18301.v1-master.patch > > > Enable > TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster > that was temporally disabled by HBASE-14614 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18301) Procedure V2 (AM) - Enable TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster that was disabled by HBASE-14614
[
https://issues.apache.org/jira/browse/HBASE-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071444#comment-16071444
]
Hadoop QA commented on HBASE-18301:
---
| (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} 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} 6m
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 5m
28s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
25s{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 52s{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-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
56s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}125m 20s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 2m
43s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}214m 52s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestRegionReplicaFailover |
| | hadoop.hbase.regionserver.TestPerColumnFamilyFlush |
| Timed out junit tests |
org.apache.hadoop.hbase.quotas.TestSnapshotQuotaObserverChore |
| | org.apache.hadoop.hbase.replication.regionserver.TestWALEntryStream |
| | org.apache.hadoop.hbase.quotas.TestSpaceQuotas |
| | org.apache.hadoop.hbase.quotas.TestQuotaObserverChoreWithMiniCluster |
| | org.apache.hadoop.hbase.replication.TestReplicationSmallTests |
| | org.apache.hadoop.hbase.filter.TestFuzzyRowFilterEndToEnd |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18301 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875381/HBASE-18301.v1-master.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 86080df31af9 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 / f1b97a6 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7442/artifact/patchprocess/branch-findbugs-hbase-server-warnings.html
|
| unit |
[jira] [Commented] (HBASE-15751) Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use zookeeper 3.5
[ https://issues.apache.org/jira/browse/HBASE-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071441#comment-16071441 ] stack commented on HBASE-15751: --- Moved this out. ZK 3.5 is still not released. Feel free to pull in if situation changes before hbase2 goes out. > Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use > zookeeper 3.5 > > > Key: HBASE-15751 > URL: https://issues.apache.org/jira/browse/HBASE-15751 > Project: HBase > Issue Type: Improvement > Components: dependencies, Zookeeper >Reporter: Yufeng Jiang >Assignee: Yufeng Jiang >Priority: Critical > Attachments: HBASE-15751.patch > > > From zookeeper 3.5 and onwards, runFromConfig(QuorumPeerConfig config) method > throws AdminServerException. > HBase uses runFromConfig in HQuorumPeer.java and hence needs to throw this > exception as well. > I've created a patch to make HBase compatible with zookeeper-3.5.1-alpha. > However, since zookeeper 3.5+ does not have a stable version yet, I don't > think we should commit this patch. Instead, I suggest using this JIRA to > track this issue. Once zookeeper releases stable version of 3.5+, I could > create another patch to bump the zookeeper version in HBase trunk. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-15751) Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use zookeeper 3.5
[ https://issues.apache.org/jira/browse/HBASE-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15751: -- Fix Version/s: (was: 2.0.0) > Fixed HBase compilation failure with Zookeeper 3.5 and bumped HBase to use > zookeeper 3.5 > > > Key: HBASE-15751 > URL: https://issues.apache.org/jira/browse/HBASE-15751 > Project: HBase > Issue Type: Improvement > Components: dependencies, Zookeeper >Reporter: Yufeng Jiang >Assignee: Yufeng Jiang >Priority: Critical > Attachments: HBASE-15751.patch > > > From zookeeper 3.5 and onwards, runFromConfig(QuorumPeerConfig config) method > throws AdminServerException. > HBase uses runFromConfig in HQuorumPeer.java and hence needs to throw this > exception as well. > I've created a patch to make HBase compatible with zookeeper-3.5.1-alpha. > However, since zookeeper 3.5+ does not have a stable version yet, I don't > think we should commit this patch. Instead, I suggest using this JIRA to > track this issue. Once zookeeper releases stable version of 3.5+, I could > create another patch to bump the zookeeper version in HBase trunk. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17442) Move most of the replication related classes to hbase-server package
[ https://issues.apache.org/jira/browse/HBASE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17442: -- Priority: Critical (was: Major) > Move most of the replication related classes to hbase-server package > > > Key: HBASE-17442 > URL: https://issues.apache.org/jira/browse/HBASE-17442 > Project: HBase > Issue Type: Sub-task > Components: build, Replication >Affects Versions: 2.0.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Critical > Fix For: 2.0.0 > > Attachments: 0001-hbase-replication-module.patch > > > After the replication requests are routed through master, replication > implementation details didn't need be exposed to client. We should move most > of the replication related classes to hbase-server package. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-17442) Move most of the replication related classes to hbase-server package
[ https://issues.apache.org/jira/browse/HBASE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071440#comment-16071440 ] stack edited comment on HBASE-17442 at 7/1/17 11:24 PM: Or hang on... let me try again the replication module. see if it easier now you've moved stuff behind master [~zghaobac]. was (Author: stack): Or hang on... let me try and make a replication module. > Move most of the replication related classes to hbase-server package > > > Key: HBASE-17442 > URL: https://issues.apache.org/jira/browse/HBASE-17442 > Project: HBase > Issue Type: Sub-task > Components: build, Replication >Affects Versions: 2.0.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: 0001-hbase-replication-module.patch > > > After the replication requests are routed through master, replication > implementation details didn't need be exposed to client. We should move most > of the replication related classes to hbase-server package. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17442) Move most of the replication related classes to hbase-server package
[ https://issues.apache.org/jira/browse/HBASE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071440#comment-16071440 ] stack commented on HBASE-17442: --- Or hang on... let me try and make a replication module. > Move most of the replication related classes to hbase-server package > > > Key: HBASE-17442 > URL: https://issues.apache.org/jira/browse/HBASE-17442 > Project: HBase > Issue Type: Sub-task > Components: build, Replication >Affects Versions: 2.0.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: 0001-hbase-replication-module.patch > > > After the replication requests are routed through master, replication > implementation details didn't need be exposed to client. We should move most > of the replication related classes to hbase-server package. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-7386) Investigate providing some supervisor support for znode deletion
[ https://issues.apache.org/jira/browse/HBASE-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071439#comment-16071439 ] stack commented on HBASE-7386: -- What you think of this [~asamir] Is it salvageable? > Investigate providing some supervisor support for znode deletion > > > Key: HBASE-7386 > URL: https://issues.apache.org/jira/browse/HBASE-7386 > Project: HBase > Issue Type: Task > Components: master, regionserver, scripts >Reporter: Gregory Chanan >Assignee: stack >Priority: Blocker > Attachments: HBASE-7386-bin.patch, HBASE-7386-bin-v2.patch, > HBASE-7386-bin-v3.patch, HBASE-7386-conf.patch, HBASE-7386-conf-v2.patch, > HBASE-7386-conf-v3.patch, HBASE-7386-src.patch, HBASE-7386-v0.patch, > supervisordconfigs-v0.patch > > > There a couple of JIRAs for deleting the znode on a process failure: > HBASE-5844 (RS) > HBASE-5926 (Master) > which are pretty neat; on process failure, they delete the znode of the > underlying process so HBase can recover faster. > These JIRAs were implemented via the startup scripts; i.e. the script hangs > around and waits for the process to exit, then deletes the znode. > There are a few problems associated with this approach, as listed in the > below JIRAs: > 1) Hides startup output in script > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463401=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463401 > 2) two hbase processes listed per launched daemon > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463409=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463409 > 3) Not run by a real supervisor > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463409=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463409 > 4) Weird output after kill -9 actual process in standalone mode > https://issues.apache.org/jira/browse/HBASE-5926?focusedCommentId=13506801=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13506801 > 5) Can kill existing RS if called again > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463401=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463401 > 6) Hides stdout/stderr[6] > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13506832=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13506832 > I suspect running in via something like supervisor.d can solve these issues > if we provide the right support. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-7386) Investigate providing some supervisor support for znode deletion
[ https://issues.apache.org/jira/browse/HBASE-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-7386: - Fix Version/s: (was: 2.0.0) > Investigate providing some supervisor support for znode deletion > > > Key: HBASE-7386 > URL: https://issues.apache.org/jira/browse/HBASE-7386 > Project: HBase > Issue Type: Task > Components: master, regionserver, scripts >Reporter: Gregory Chanan >Assignee: stack >Priority: Blocker > Attachments: HBASE-7386-bin.patch, HBASE-7386-bin-v2.patch, > HBASE-7386-bin-v3.patch, HBASE-7386-conf.patch, HBASE-7386-conf-v2.patch, > HBASE-7386-conf-v3.patch, HBASE-7386-src.patch, HBASE-7386-v0.patch, > supervisordconfigs-v0.patch > > > There a couple of JIRAs for deleting the znode on a process failure: > HBASE-5844 (RS) > HBASE-5926 (Master) > which are pretty neat; on process failure, they delete the znode of the > underlying process so HBase can recover faster. > These JIRAs were implemented via the startup scripts; i.e. the script hangs > around and waits for the process to exit, then deletes the znode. > There are a few problems associated with this approach, as listed in the > below JIRAs: > 1) Hides startup output in script > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463401=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463401 > 2) two hbase processes listed per launched daemon > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463409=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463409 > 3) Not run by a real supervisor > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463409=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463409 > 4) Weird output after kill -9 actual process in standalone mode > https://issues.apache.org/jira/browse/HBASE-5926?focusedCommentId=13506801=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13506801 > 5) Can kill existing RS if called again > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463401=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463401 > 6) Hides stdout/stderr[6] > https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13506832=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13506832 > I suspect running in via something like supervisor.d can solve these issues > if we provide the right support. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17908) Upgrade guava
[ https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17908: -- Attachment: HBASE-17908.master.014.patch > Upgrade guava > - > > Key: HBASE-17908 > URL: https://issues.apache.org/jira/browse/HBASE-17908 > Project: HBase > Issue Type: Sub-task > Components: dependencies >Reporter: Balazs Meszaros >Assignee: stack >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-17908.master.001.patch, > HBASE-17908.master.002.patch, HBASE-17908.master.003.patch, > HBASE-17908.master.004.patch, HBASE-17908.master.005.patch, > HBASE-17908.master.006.patch, HBASE-17908.master.007.patch, > HBASE-17908.master.008.patch, HBASE-17908.master.009.patch, > HBASE-17908.master.010.patch, HBASE-17908.master.011.patch, > HBASE-17908.master.012.patch, HBASE-17908.master.013.patch, > HBASE-17908.master.013.patch, HBASE-17908.master.014.patch > > > 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.4.14#64029)
[jira] [Updated] (HBASE-11707) Using Map instead of list in FailedServers of RpcClient
[
https://issues.apache.org/jira/browse/HBASE-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-11707:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Pushed to master and branch-2. Thanks for the patch [~liushaohui] and reviews
[~nkeywal]
> Using Map instead of list in FailedServers of RpcClient
> ---
>
> Key: HBASE-11707
> URL: https://issues.apache.org/jira/browse/HBASE-11707
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-11707.master.001.patch, HBASE-11707-trunk-v1.diff,
> HBASE-11707-trunk-v2.diff
>
>
> Currently, FailedServers uses a list to record the black list of servers and
> iterate the list to check if a server is in list. It's not efficient when the
> list is very large. And the list is not thread safe for the add and iteration
> operations.
> RpcClient.java#175
> {code}
> // iterate, looking for the search entry and cleaning expired entries
> Iterator> it = failedServers.iterator();
> while (it.hasNext()) {
> Pair cur = it.next();
> if (cur.getFirst() < now) {
> it.remove();
> } else {
> if (lookup.equals(cur.getSecond())) {
> return true;
> }
> }
> {code}
> A simple change is to change this list to ConcurrentHashMap.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[
https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071384#comment-16071384
]
Hadoop QA commented on HBASE-18010:
---
| (x) *{color:red}-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 10 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
15s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
55s{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
39s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
35s{color} | {color:red} hbase-common in master has 2 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
48s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
50s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
57s{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}
34m 10s{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-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
5s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 97m 1s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
38s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}156m 47s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestMasterProcedureWalLease |
| Timed out junit tests |
org.apache.hadoop.hbase.backup.TestRepairAfterFailedDelete |
| | org.apache.hadoop.hbase.backup.TestIncrementalBackupWithFailures |
| | org.apache.hadoop.hbase.backup.TestRestoreBoundaryTests |
| | org.apache.hadoop.hbase.backup.TestBackupMultipleDeletes |
| | org.apache.hadoop.hbase.master.assignment.TestSplitTableRegionProcedure |
| | org.apache.hadoop.hbase.backup.TestBackupShowHistory |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18010 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875376/HBASE-18010-V10.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname |
[jira] [Updated] (HBASE-18248) Warn if monitored task has been tied up beyond a configurable threshold
[ https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18248: --- Status: Open (was: Patch Available) > Warn if monitored task has been tied up beyond a configurable threshold > --- > > Key: HBASE-18248 > URL: https://issues.apache.org/jira/browse/HBASE-18248 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18248-branch-1.3.patch, > HBASE-18248-branch-1.3.patch, HBASE-18248-branch-1.patch, > HBASE-18248-branch-1.patch, HBASE-18248-branch-2.patch, > HBASE-18248-branch-2.patch, HBASE-18248.patch, HBASE-18248.patch > > > Warn if monitored task has been tied up beyond a configurable threshold. We > especially want to do this for RPC tasks. Use a separate threshold for > warning about stuck RPC tasks versus other types of tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18248) Warn if monitored task has been tied up beyond a configurable threshold
[ https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18248: --- Status: Patch Available (was: Open) > Warn if monitored task has been tied up beyond a configurable threshold > --- > > Key: HBASE-18248 > URL: https://issues.apache.org/jira/browse/HBASE-18248 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18248-branch-1.3.patch, > HBASE-18248-branch-1.3.patch, HBASE-18248-branch-1.patch, > HBASE-18248-branch-1.patch, HBASE-18248-branch-2.patch, > HBASE-18248-branch-2.patch, HBASE-18248.patch, HBASE-18248.patch > > > Warn if monitored task has been tied up beyond a configurable threshold. We > especially want to do this for RPC tasks. Use a separate threshold for > warning about stuck RPC tasks versus other types of tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18264) Update pom plugins
[ https://issues.apache.org/jira/browse/HBASE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18264: -- Attachment: HBASE-18264.master.003.patch Retry... >From console [INFO] Results: [INFO] [ERROR] Errors: [ERROR] org.apache.hadoop.hbase.master.procedure.TestMasterProcedureWalLease.org.apache.hadoop.hbase.master.procedure.TestMasterProcedureWalLease [ERROR] Run 1: TestMasterProcedureWalLease.tearDown:85->Object.wait:-2 ? TestTimedOut test ti... [ERROR] Run 2: TestMasterProcedureWalLease.org.apache.hadoop.hbase.master.procedure.TestMasterProcedureWalLease ? [INFO] [WARNING] Flakes: [WARNING] org.apache.hadoop.hbase.quotas.TestSnapshotQuotaObserverChore.testSnapshotSize(org.apache.hadoop.hbase.quotas.TestSnapshotQuotaObserverChore) [ERROR] Run 1: TestSnapshotQuotaObserverChore.testSnapshotSize:277 Waiting timed out after [30,000] msec [INFO] Run 2: PASS > Update pom plugins > -- > > Key: HBASE-18264 > URL: https://issues.apache.org/jira/browse/HBASE-18264 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: Peter Somogyi > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18264.master.001.patch, > HBASE-18264.master.002.patch, HBASE-18264.master.003.patch, > HBASE-18264.master.003.patch, HBASE-18264.master.003.patch > > > A bunch are old. Lets update. [~balazs.meszaros] you want to have a go at > this sir? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16415) Replication in different namespace
[
https://issues.apache.org/jira/browse/HBASE-16415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071292#comment-16071292
]
Jan Kunigk commented on HBASE-16415:
Thanks, I also just realised, that with Option 2 we could have a user configure
two redirections with the same source, which is not something that the
redirection code supports in this initial patch.
With Option 1, we can rule out such misconfiguration via the the Map Interfaces
invariant, that it may never contain duplicate keys.
J
> Replication in different namespace
> --
>
> Key: HBASE-16415
> URL: https://issues.apache.org/jira/browse/HBASE-16415
> Project: HBase
> Issue Type: New Feature
> Components: Replication
>Reporter: Christian Guegi
>Assignee: Jan Kunigk
>
> It would be nice to replicate tables from one namespace to another namespace.
> Example:
> Master cluster, namespace=default, table=bar
> Slave cluster, namespace=dr, table=bar
> Replication happens in class ReplicationSink:
> public void replicateEntries(List entries, final CellScanner
> cells, ...){
> ...
> TableName table =
> TableName.valueOf(entry.getKey().getTableName().toByteArray());
> ...
> addToHashMultiMap(rowMap, table, clusterIds, m);
> ...
> for (Entry> entry :
> rowMap.entrySet()) {
> batch(entry.getKey(), entry.getValue().values());
> }
>}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18301) Procedure V2 (AM) - Enable TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster that was disabled by HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-18301: --- Attachment: HBASE-18301.v1-master.patch > Procedure V2 (AM) - Enable > TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster > that was disabled by HBASE-14614 > - > > Key: HBASE-18301 > URL: https://issues.apache.org/jira/browse/HBASE-18301 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Fix For: 2.0.0 > > Attachments: HBASE-18301.v1-master.patch > > > Enable > TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster > that was temporally disabled by HBASE-14614 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18301) Procedure V2 (AM) - Enable TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster that was disabled by HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-18301: --- Attachment: (was: HBASE-18301.v1-master.patch) > Procedure V2 (AM) - Enable > TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster > that was disabled by HBASE-14614 > - > > Key: HBASE-18301 > URL: https://issues.apache.org/jira/browse/HBASE-18301 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Fix For: 2.0.0 > > > Enable > TestSimpleRegionNormalizerOnCluster#testRegionNormalizationMergeOnCluster > that was temporally disabled by HBASE-14614 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18023) Log multi-* requests for more than threshold number of rows
[ https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071219#comment-16071219 ] Hudson commented on HBASE-18023: FAILURE: Integrated in Jenkins build HBase-1.4 #797 (See [https://builds.apache.org/job/HBase-1.4/797/]) HBASE-18023 Log multi-* requests for more than threshold number of rows (apurtell: rev 743f454d25f70a06d6ba212e0bae648616474f8d) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java * (edit) hbase-common/src/main/resources/hbase-default.xml * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestMultiLogThreshold.java > Log multi-* requests for more than threshold number of rows > --- > > Key: HBASE-18023 > URL: https://issues.apache.org/jira/browse/HBASE-18023 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Clay B. >Assignee: David Harju >Priority: Minor > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18023-branch-1.3.patch, > HBASE-18023-branch-1.patch, HBASE-18023.master.001.patch, > HBASE-18023.master.002.patch, HBASE-18023.master.003.patch, > HBASE-18023.master.004.patch > > > Today, if a user happens to do something like a large multi-put, they can get > through request throttling (e.g. it is one request) but still crash a region > server with a garbage storm. We have seen regionservers hit this issue and it > is silent and deadly. The RS will report nothing more than a mysterious > garbage collection and exit out. > Ideally, we could report a large multi-* request before starting it, in case > it happens to be deadly. Knowing the client, user and how many rows are > affected would be a good start to tracking down painful users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18266) Eliminate the warnings from the spotbugs
[ https://issues.apache.org/jira/browse/HBASE-18266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071213#comment-16071213 ] Hudson commented on HBASE-18266: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3292 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3292/]) HBASE-18266 Create static empty byte array to save memory (Ben Epstein) (stack: rev e89baeaf93c36997296f84c600c4065b597365f5) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java > Eliminate the warnings from the spotbugs > > > Key: HBASE-18266 > URL: https://issues.apache.org/jira/browse/HBASE-18266 > Project: HBase > Issue Type: Umbrella >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > > It is hard to get +1 from QA currently because spotbugs is always unhappy... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18264) Update pom plugins
[
https://issues.apache.org/jira/browse/HBASE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071212#comment-16071212
]
Hadoop QA commented on HBASE-18264:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{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:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 10m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 7m
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 7m
49s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
31s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 9m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
14s{color} | {color:green} hbase-common generated 0 new + 26 unchanged - 26
fixed = 26 total (was 52) {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
26s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
10s{color} | {color:green} hbase-metrics-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
11s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
8s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
9s{color} | {color:green} hbase-metrics in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
10s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
14s{color} | {color:green} hbase-protocol in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
16s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
11s{color} | {color:green} hbase-prefix-tree in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
35s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
17s{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
12s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
13s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
15s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
15s{color} | {color:green} hbase-it in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
13s{color} | {color:green} hbase-examples in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
17s{color} | {color:green} hbase-rest in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
11s{color} | {color:green} hbase-external-blockcache in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
47s{color} | {color:green}
[jira] [Commented] (HBASE-18239) Address ruby static analysis for shell module
[ https://issues.apache.org/jira/browse/HBASE-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071210#comment-16071210 ] Hudson commented on HBASE-18239: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3290 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3290/]) HBASE-18239 rubocop autocorrect for shell (stack: rev 2115d4b50ecf7a17028d88c9bccef076e516a3e2) * (edit) hbase-shell/src/main/ruby/shell/commands/alter_async.rb * (edit) hbase-shell/src/main/ruby/hbase/hbase.rb * (edit) hbase-shell/src/main/ruby/shell/commands/list_rsgroups.rb * (edit) hbase-shell/src/main/ruby/shell/commands/balancer_enabled.rb * (edit) hbase-shell/src/main/ruby/shell/commands/drop.rb * (edit) hbase-shell/src/main/ruby/shell/commands/set_auths.rb * (edit) hbase-shell/src/main/ruby/shell/commands/list_quota_snapshots.rb * (edit) hbase-shell/src/main/ruby/shell/commands/move.rb * (edit) hbase-shell/src/main/ruby/shell/commands/incr.rb * (edit) hbase-shell/src/main/ruby/shell/commands/remove_peer.rb * (edit) hbase-shell/src/main/ruby/shell/commands/list_snapshot_sizes.rb * (edit) hbase-shell/src/main/ruby/shell/commands/snapshot.rb * (edit) hbase-shell/src/main/ruby/shell/commands/close_region.rb * (edit) hbase-shell/src/main/ruby/irb/hirb.rb * (edit) hbase-shell/src/main/ruby/shell/commands/describe_namespace.rb * (edit) hbase-shell/src/main/ruby/shell/commands/truncate.rb * (edit) hbase-shell/src/main/ruby/shell/commands/balancer.rb * (edit) hbase-shell/src/main/ruby/shell/commands/deleteall.rb * (edit) hbase-shell/src/main/ruby/hbase/visibility_labels.rb * (edit) hbase-shell/src/main/ruby/shell/commands/disable_table_replication.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get_table.rb * (edit) hbase-shell/src/main/ruby/shell/commands/update_config.rb * (edit) hbase-shell/src/main/ruby/shell/commands/catalogjanitor_switch.rb * (edit) hbase-shell/src/main/ruby/shell/commands/enable_all.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get_peer_config.rb * (edit) hbase-shell/src/main/ruby/shell/commands/show_peer_tableCFs.rb * (edit) hbase-shell/src/main/ruby/shell/commands/delete.rb * (edit) hbase-shell/src/main/ruby/shell/commands/list_security_capabilities.rb * (edit) hbase-shell/src/main/ruby/shell/commands/add_peer.rb * (edit) hbase-shell/src/main/ruby/shell/commands/describe.rb * (edit) hbase-shell/src/main/ruby/shell/commands/truncate_preserve.rb * (edit) hbase-shell/src/main/ruby/shell/commands/alter_namespace.rb * (edit) hbase-shell/src/main/ruby/shell/commands/count.rb * (edit) hbase-shell/src/main/ruby/shell/commands/remove_peer_tableCFs.rb * (edit) hbase-shell/src/main/ruby/shell/commands/version.rb * (edit) hbase-shell/src/main/ruby/shell/commands/balance_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/compact_rs.rb * (edit) hbase-shell/src/main/ruby/shell/commands/catalogjanitor_enabled.rb * (edit) hbase-shell/src/main/ruby/shell/commands/assign.rb * (edit) hbase-shell/src/main/ruby/shell/commands/cleaner_chore_switch.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get.rb * (edit) hbase-shell/src/main/ruby/shell/commands/set_peer_namespaces.rb * (edit) hbase-shell/src/main/ruby/hbase/taskmonitor.rb * (edit) hbase-shell/src/main/ruby/shell/commands/move_servers_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/move_servers_tables_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/add_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/set_peer_tableCFs.rb * (edit) hbase-shell/src/main/ruby/shell/commands/status.rb * (edit) hbase-shell/src/main/ruby/shell/commands/compact.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get_table_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get_server_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/disable_all.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get_auths.rb * (edit) hbase-shell/src/main/ruby/shell/commands/list_snapshots.rb * (edit) hbase-shell/src/main/ruby/shell/commands/normalizer_enabled.rb * (edit) hbase-shell/src/main/ruby/shell/commands/remove_rsgroup.rb * (edit) hbase-shell/src/main/ruby/shell/commands/remove_peer_namespaces.rb * (edit) hbase-shell/src/main/ruby/shell/formatter.rb * (edit) hbase-shell/src/main/ruby/shell/commands/update_all_config.rb * (edit) hbase-shell/src/main/ruby/shell/commands/create_namespace.rb * (edit) hbase-shell/src/main/ruby/shell/commands/get_counter.rb * (edit) hbase-shell/src/main/ruby/shell/commands/enable.rb * (edit) hbase-shell/src/main/ruby/shell/commands/set_visibility.rb * (edit) hbase-shell/src/main/ruby/shell/commands/add_labels.rb * (edit) hbase-shell/src/main/ruby/shell/commands/disable.rb * (edit) hbase-shell/src/main/ruby/hbase/quotas.rb * (edit) hbase-shell/src/main/ruby/shell/commands/clear_auths.rb * (edit) hbase-shell/src/main/ruby/shell/commands/list_locks.rb * (edit)
[jira] [Commented] (HBASE-17995) improve log messages during snapshot related tests
[ https://issues.apache.org/jira/browse/HBASE-17995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071207#comment-16071207 ] Hudson commented on HBASE-17995: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3290 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3290/]) HBASE-17995 improve log messages during snapshot tests. (busbey: rev fc973d0918156ce92e63e67c433c0b59252908c5) * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/SnapshotTestingUtils.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TableSnapshotInputFormatTestBase.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableSnapshotInputFormat.java > improve log messages during snapshot related tests > -- > > Key: HBASE-17995 > URL: https://issues.apache.org/jira/browse/HBASE-17995 > Project: HBase > Issue Type: Improvement > Components: integration tests, mapreduce, snapshots, test >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Trivial > Fix For: 3.0.0, 1.4.0, 2.0.0-alpha-2 > > Attachments: HBASE-17995.0.patch > > > while verifying the changes for HBASE-17964 I had to chase down a failure > related to having the wrong hbase configs. Adding some additional logging > detail let me see what was happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15391) Avoid too large "deleted from META" info log
[
https://issues.apache.org/jira/browse/HBASE-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071206#comment-16071206
]
Hudson commented on HBASE-15391:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3290 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3290/])
HBASE-15391 ADDENDUM Avoid too large "deleted from META" info log. (busbey: rev
3caeba07981de09c440284caa5d3d31d686377d6)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> Avoid too large "deleted from META" info log
>
>
> Key: HBASE-15391
> URL: https://issues.apache.org/jira/browse/HBASE-15391
> Project: HBase
> Issue Type: Improvement
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-15391.addendum.patch, HBASE-15391-trunk-v1.diff,
> HBASE-15391-trunk-v2.diff
>
>
> When deleting a large table in HBase, there will be a large info log in
> HMaster.
> {code}
> 2016-02-29,05:58:45,920 INFO org.apache.hadoop.hbase.catalog.MetaEditor:
> Deleted [{ENCODED => 4b54572150941cd03f5addfdeab0a754, NAME =>
> 'YCSBTest,,1453186492932.4b54572150941cd03f5addfdeab0a754.', STARTKEY => '',
> ENDKEY => 'user01'}, {ENCODED => 715e142bcd6a31d7842abf286ef8a5fe, NAME =>
> 'YCSBTest,user01,1453186492933.715e142bcd6a31d7842abf286ef8a5fe.', STARTKEY
> => 'user01', ENDKEY => 'user02'}, {ENCODED =>
> 5f9cef5714973f13baa63fba29a68d70, NAME =>
> 'YCSBTest,user02,1453186492933.5f9cef5714973f13baa63fba29a68d70.', STARTKEY
> => 'user02', ENDKEY => 'user03'}, {ENCODED =>
> 86cf3fa4c0a6b911275512c1d4b78533, NAME => 'YCSBTest,user0...
> {code}
> The reason is that MetaTableAccessor will log all regions when deleting them
> from meta. See, MetaTableAccessor.java#deleteRegions
> {code}
> public static void deleteRegions(Connection connection,
>List regionsInfo, long ts)
> throws IOException {
> List deletes = new ArrayList(regionsInfo.size());
> for (HRegionInfo hri: regionsInfo) {
> Delete e = new Delete(hri.getRegionName());
> e.addFamily(getCatalogFamily(), ts);
> deletes.add(e);
> }
> deleteFromMetaTable(connection, deletes);
> LOG.info("Deleted " + regionsInfo);
> }
> {code}
> Just change the info log to debug and add a info log about the number of
> deleted regions. Others suggestions are welcomed~
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18302) Protobuf section in the docs needs some clean up
[ https://issues.apache.org/jira/browse/HBASE-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071209#comment-16071209 ] Hudson commented on HBASE-18302: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3290 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3290/]) HBASE-18302 Protobuf section in the docs needs some clean up (Artem (stack: rev 90fee695b49a68b2e183c7b9f8f2791e41a7aaa7) * (edit) src/main/asciidoc/_chapters/preface.adoc * (edit) src/main/asciidoc/_chapters/protobuf.adoc > Protobuf section in the docs needs some clean up > > > Key: HBASE-18302 > URL: https://issues.apache.org/jira/browse/HBASE-18302 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits >Priority: Blocker > Labels: newbie > Fix For: 3.0.0 > > Attachments: HBASE-18302-0.patch > > > there are some grammatical mistakes in the protobuf section -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18293) Only add the spotbugs dependency when jdk8 is active
[
https://issues.apache.org/jira/browse/HBASE-18293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071208#comment-16071208
]
Hudson commented on HBASE-18293:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3290 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3290/])
HBASE-18293 Only add the spotbugs dependency when jdk8 is active (busbey: rev
0d4245c99e5e0a326d384af643ec268cc312513a)
* (edit) pom.xml
> Only add the spotbugs dependency when jdk8 is active
>
>
> Key: HBASE-18293
> URL: https://issues.apache.org/jira/browse/HBASE-18293
> Project: HBase
> Issue Type: Sub-task
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12
>
> Attachments: HBASE-18293.v0.patch, HBASE-18923-branch-1.1.v1.patch
>
>
> The spotbugs requires the java 8 so we should only add the spotbugs
> dependency when jdk8 is active.
> {noformat}
> [INFO] Fork Value is true
> [java] Exception in thread "main"
> java.lang.UnsupportedClassVersionError: edu/umd/cs/findbugs/FindBugs2 :
> Unsupported major.minor version 52.0
> [java] at java.lang.ClassLoader.defineClass1(Native Method)
> [java] at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
> [java] at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> [java] at java.net.URLClassLoader.defineClass(URLClassLoader.java:442)
> [java] at java.net.URLClassLoader.access$100(URLClassLoader.java:64)
> [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:354)
> [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:348)
> [java] at java.security.AccessController.doPrivileged(Native Method)
> [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:347)
> [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:312)
> [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> [java] at
> sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-13866) Add endpoint coprocessor to the section hbase.coprocessor.region.classes in HBase book
[
https://issues.apache.org/jira/browse/HBASE-13866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071211#comment-16071211
]
Hudson commented on HBASE-13866:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3290 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3290/])
HBASE-13866 Clarify description of hbase.coprocessor.region.classes (stack: rev
92f74d6f1ed23c7525742f9c81a44594b8d8b8e6)
* (edit) hbase-common/src/main/resources/hbase-default.xml
> Add endpoint coprocessor to the section hbase.coprocessor.region.classes in
> HBase book
> --
>
> Key: HBASE-13866
> URL: https://issues.apache.org/jira/browse/HBASE-13866
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.0.0
>Reporter: Vladimir Rodionov
>Assignee: Misty Stanley-Jones
>Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: HBASE-13866.patch
>
>
> {quote}
> hbase.coprocessor.region.classes
> Description
> A comma-separated list of Coprocessors that are loaded by default on all
> tables. For any override coprocessor method, these classes will be called in
> order. After implementing your own Coprocessor, just put it in HBase’s
> classpath and add the fully qualified class name here. A coprocessor can also
> be loaded on demand by setting HTableDescriptor.
> {quote}
> This must be more specific: not Coprocessors, but Region observers and
> *endpoint coprocessors*.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18288) Declared dependency on specific javax.ws.rs
[ https://issues.apache.org/jira/browse/HBASE-18288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071205#comment-16071205 ] Hudson commented on HBASE-18288: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3290 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3290/]) HBASE-18288 Declared dependency on specific javax.ws.rs. (busbey: rev 74c574202489824aa7bada7a6d38059e934a3f65) * (edit) pom.xml * (edit) hbase-it/pom.xml * (edit) hbase-rest/pom.xml * (edit) hbase-server/pom.xml > Declared dependency on specific javax.ws.rs > --- > > Key: HBASE-18288 > URL: https://issues.apache.org/jira/browse/HBASE-18288 > Project: HBase > Issue Type: Task > Components: dependencies, REST >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18288.0.patch > > > We make use of the javax.ws.rs API, but we rely on getting a jar for it > transitively. since we use the classes, we should declare an explicit > dependency. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[ https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anastasia Braginsky updated HBASE-18010: Attachment: HBASE-18010-V10.patch > Connect CellChunkMap to be used for flattening in CompactingMemStore > > > Key: HBASE-18010 > URL: https://issues.apache.org/jira/browse/HBASE-18010 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky > Attachments: HBASE-18010-V04.patch, HBASE-18010-V06.patch, > HBASE-18010-V07.patch, HBASE-18010-V08.patch, HBASE-18010-V09.patch, > HBASE-18010-V10.patch > > > The CellChunkMap helps to create a new type of ImmutableSegment, where the > index (CellSet's delegatee) is going to be CellChunkMap. No big cells or > upserted cells are going to be supported here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18228) HBCK improvements
[
https://issues.apache.org/jira/browse/HBASE-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071131#comment-16071131
]
Hadoop QA commented on HBASE-18228:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
39s{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} 3m
45s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
4s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
40s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
27s{color} | {color:green} branch-1.3 passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 4m
9s{color} | {color:red} hbase-server in branch-1.3 has 17 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
14s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
32s{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}
39m 35s{color} | {color:green} The patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 4m
47s{color} | {color:red} hbase-server generated 2 new + 17 unchanged - 0 fixed
= 19 total (was 17) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
10s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}151m 46s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}216m 47s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | new org.apache.hadoop.hbase.util.HBaseFsck(Configuration,
ExecutorService) invokes inefficient new String() constructor At
HBaseFsck.java:new String() constructor At HBaseFsck.java:[line 251] |
| | org.apache.hadoop.hbase.util.HBaseFsck.checkRegionConsistency(String,
HBaseFsck$HbckInfo) concatenates strings using + in a loop At HBaseFsck.java:+
in a loop At HBaseFsck.java:[line 2388] |
| Failed junit tests | hadoop.hbase.util.TestHBaseFsck |
| | hadoop.hbase.client.TestAdmin2 |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:9ba21e3 |
| JIRA Issue | HBASE-18228 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875313/HBASE-18228.branch-1.3.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 1da7b822bbf9 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 | /testptch/patchprocess/precommit/personality/hbase.sh |
| git revision | branch-1.3 / 70386cb |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| findbugs |
[jira] [Updated] (HBASE-18295) The result contains the cells across different rows
[ https://issues.apache.org/jira/browse/HBASE-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18295: --- Summary: The result contains the cells across different rows (was: TestAcidGuarantees fails again) > The result contains the cells across different rows > > > Key: HBASE-18295 > URL: https://issues.apache.org/jira/browse/HBASE-18295 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Blocker > Fix For: 3.0.0, 2.0.0-alpha-2 > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18023) Log multi-* requests for more than threshold number of rows
[ https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071100#comment-16071100 ] Hudson commented on HBASE-18023: SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #190 (See [https://builds.apache.org/job/HBase-1.3-JDK7/190/]) HBASE-18023 Log multi-* requests for more than threshold number of rows (apurtell: rev 70386cbe4cd905b50bec5fa67a751141ea89ed9f) * (edit) hbase-common/src/main/resources/hbase-default.xml * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestMultiLogThreshold.java > Log multi-* requests for more than threshold number of rows > --- > > Key: HBASE-18023 > URL: https://issues.apache.org/jira/browse/HBASE-18023 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Clay B. >Assignee: David Harju >Priority: Minor > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18023-branch-1.3.patch, > HBASE-18023-branch-1.patch, HBASE-18023.master.001.patch, > HBASE-18023.master.002.patch, HBASE-18023.master.003.patch, > HBASE-18023.master.004.patch > > > Today, if a user happens to do something like a large multi-put, they can get > through request throttling (e.g. it is one request) but still crash a region > server with a garbage storm. We have seen regionservers hit this issue and it > is silent and deadly. The RS will report nothing more than a mysterious > garbage collection and exit out. > Ideally, we could report a large multi-* request before starting it, in case > it happens to be deadly. Knowing the client, user and how many rows are > affected would be a good start to tracking down painful users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18023) Log multi-* requests for more than threshold number of rows
[ https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071097#comment-16071097 ] Hudson commented on HBASE-18023: SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #204 (See [https://builds.apache.org/job/HBase-1.3-JDK8/204/]) HBASE-18023 Log multi-* requests for more than threshold number of rows (apurtell: rev 70386cbe4cd905b50bec5fa67a751141ea89ed9f) * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestMultiLogThreshold.java * (edit) hbase-common/src/main/resources/hbase-default.xml * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java > Log multi-* requests for more than threshold number of rows > --- > > Key: HBASE-18023 > URL: https://issues.apache.org/jira/browse/HBASE-18023 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Clay B. >Assignee: David Harju >Priority: Minor > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18023-branch-1.3.patch, > HBASE-18023-branch-1.patch, HBASE-18023.master.001.patch, > HBASE-18023.master.002.patch, HBASE-18023.master.003.patch, > HBASE-18023.master.004.patch > > > Today, if a user happens to do something like a large multi-put, they can get > through request throttling (e.g. it is one request) but still crash a region > server with a garbage storm. We have seen regionservers hit this issue and it > is silent and deadly. The RS will report nothing more than a mysterious > garbage collection and exit out. > Ideally, we could report a large multi-* request before starting it, in case > it happens to be deadly. Knowing the client, user and how many rows are > affected would be a good start to tracking down painful users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-11707) Using Map instead of list in FailedServers of RpcClient
[
https://issues.apache.org/jira/browse/HBASE-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071093#comment-16071093
]
Hadoop QA commented on HBASE-11707:
---
| (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: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} 8m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s{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:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
16s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
21s{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}
69m 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-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
7s{color} | {color:green} hbase-client 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} 93m 52s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-11707 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875302/HBASE-11707.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 78d706502f81 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 / e89baea |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7439/artifact/patchprocess/branch-findbugs-hbase-client-warnings.html
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7439/testReport/ |
| modules | C: hbase-client U: hbase-client |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7439/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Using Map instead of list in FailedServers of RpcClient
> ---
>
> Key: HBASE-11707
> URL:
[jira] [Created] (HBASE-18306) Get rid of TableDescriptor#getConfiguration
Chia-Ping Tsai created HBASE-18306: -- Summary: Get rid of TableDescriptor#getConfiguration Key: HBASE-18306 URL: https://issues.apache.org/jira/browse/HBASE-18306 Project: HBase Issue Type: Bug Reporter: Chia-Ping Tsai Fix For: 3.0.0, 2.0.0-alpha-2 We should substitute TD#Value for the TD#Configuration. The TD#Configuration is rarely used in code base. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18266) Eliminate the warnings from the spotbugs
[ https://issues.apache.org/jira/browse/HBASE-18266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071060#comment-16071060 ] Hudson commented on HBASE-18266: FAILURE: Integrated in Jenkins build HBase-1.4 #796 (See [https://builds.apache.org/job/HBase-1.4/796/]) HBASE-18266 Create static empty byte array to save memory (Ben Epstein) (stack: rev 3b28f66bf3ee7c0c2b02dbc3434a2ae2f4f1946b) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java > Eliminate the warnings from the spotbugs > > > Key: HBASE-18266 > URL: https://issues.apache.org/jira/browse/HBASE-18266 > Project: HBase > Issue Type: Umbrella >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > > It is hard to get +1 from QA currently because spotbugs is always unhappy... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18216) [AMv2] Workaround for HBASE-18152, corrupt procedure WAL
[ https://issues.apache.org/jira/browse/HBASE-18216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071057#comment-16071057 ] Hudson commented on HBASE-18216: FAILURE: Integrated in Jenkins build HBase-1.4 #796 (See [https://builds.apache.org/job/HBase-1.4/796/]) HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL (stack: rev 8ce3f49f8034417734ef1a3e6c624a601a22ace9) * (edit) hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALFormatReader.java > [AMv2] Workaround for HBASE-18152, corrupt procedure WAL > > > Key: HBASE-18216 > URL: https://issues.apache.org/jira/browse/HBASE-18216 > Project: HBase > Issue Type: Bug > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: stack >Assignee: stack > Fix For: 2.0.0 > > Attachments: HBASE-18216.branch-1.001.patch > > > Let me commit workaround for the issue up in HBASE-18152, corruption in the > master wal procedure files. Testing on cluster shows it helps. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18152) [AMv2] Corrupt Procedure WAL file; procedure data stored out of order
[ https://issues.apache.org/jira/browse/HBASE-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071058#comment-16071058 ] Hudson commented on HBASE-18152: FAILURE: Integrated in Jenkins build HBase-1.4 #796 (See [https://builds.apache.org/job/HBase-1.4/796/]) HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL (stack: rev 8ce3f49f8034417734ef1a3e6c624a601a22ace9) * (edit) hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALFormatReader.java > [AMv2] Corrupt Procedure WAL file; procedure data stored out of order > - > > Key: HBASE-18152 > URL: https://issues.apache.org/jira/browse/HBASE-18152 > Project: HBase > Issue Type: Sub-task > Components: Region Assignment >Affects Versions: 2.0.0 >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18152.master.001.patch, > pv2-0036.log, pv2-0047.log, > reading_bad_wal.patch > > > I've seen corruption from time-to-time testing. Its rare enough. Often we > can get over it but sometimes we can't. It took me a while to capture an > instance of corruption. Turns out we are write to the WAL out-of-order which > undoes a basic tenet; that WAL content is ordered in line w/ execution. > Below I'll post a corrupt WAL. > Looking at the write-side, there is a lot going on. I'm not clear on how we > could write out of order. Will try and get more insight. Meantime parking > this issue here to fill data into. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18004) getRegionLocations needs to be called once in ScannerCallableWithReplicas#call()
[ https://issues.apache.org/jira/browse/HBASE-18004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071059#comment-16071059 ] Hudson commented on HBASE-18004: FAILURE: Integrated in Jenkins build HBase-1.4 #796 (See [https://builds.apache.org/job/HBase-1.4/796/]) HBASE-18004 getRegionLocations needs to be called once in (stack: rev 262e6bb3fa20fd138cf13a35b44576d6733f9856) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallableWithReplicas.java > getRegionLocations needs to be called once in > ScannerCallableWithReplicas#call() > - > > Key: HBASE-18004 > URL: https://issues.apache.org/jira/browse/HBASE-18004 > Project: HBase > Issue Type: Improvement > Components: Client >Affects Versions: 2.0.0 >Reporter: huaxiang sun >Assignee: huaxiang sun >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-18004.branch-1.001.patch, > HBASE-18004-master-001.patch, HBASE-18004-master-002.patch > > > Look at this line, > https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallableWithReplicas.java#L145 > It calls getRegionLocations() to get the primary region's locations. It's > usage is to figure out table's region replications. Since table's region > replication wont be changed until the table is disabled. It is safe to cache > this region replication. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18286) Create static empty byte array to save memory
[ https://issues.apache.org/jira/browse/HBASE-18286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071050#comment-16071050 ] Chia-Ping Tsai commented on HBASE-18286: This [commit|https://github.com/apache/hbase/commit/e89baeaf93c36997296f84c600c4065b597365f5] has incorrect jira number. FYI [~stack] > Create static empty byte array to save memory > - > > Key: HBASE-18286 > URL: https://issues.apache.org/jira/browse/HBASE-18286 > Project: HBase > Issue Type: Improvement > Components: community >Reporter: Ben Epstein >Assignee: Ben Epstein >Priority: Trivial > Fix For: 1.4.0, 2.0.0-alpha-2 > > Attachments: JIRA.HBASE-18286.001.patch > > Original Estimate: 5m > Remaining Estimate: 5m > > In Put.java, create a static empty byte array so new ones do not have to be > allocated every time it is passed into a function -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18266) Eliminate the warnings from the spotbugs
[ https://issues.apache.org/jira/browse/HBASE-18266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071049#comment-16071049 ] Chia-Ping Tsai commented on HBASE-18266: Oh..there is a [commit|https://github.com/apache/hbase/commit/e89baeaf93c36997296f84c600c4065b597365f5] with incorrect jira number... > Eliminate the warnings from the spotbugs > > > Key: HBASE-18266 > URL: https://issues.apache.org/jira/browse/HBASE-18266 > Project: HBase > Issue Type: Umbrella >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > > It is hard to get +1 from QA currently because spotbugs is always unhappy... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15631) Backport Regionserver Groups (HBASE-6721) to branch-1
[
https://issues.apache.org/jira/browse/HBASE-15631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071038#comment-16071038
]
Hadoop QA commented on HBASE-15631:
---
| (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 10s{color}
| {color:red} HBASE-15631 does not apply to branch-1. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-15631 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799888/HBASE-15631.02.branch-1.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7440/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Backport Regionserver Groups (HBASE-6721) to branch-1
> --
>
> Key: HBASE-15631
> URL: https://issues.apache.org/jira/browse/HBASE-15631
> Project: HBase
> Issue Type: New Feature
>Affects Versions: 1.4.0
>Reporter: Francis Liu
>Assignee: Francis Liu
> Attachments: HBASE-15631.02.branch-1.patch,
> HBASE-15631_1_branch-1.patch, HBASE-15631.branch-1.1.patch,
> HBASE-15631.branch-1.patch, HBASE-15631.patch
>
>
> Based on dev list discussion backporting region server group should not be an
> issue as it does not: 1. destabilize the code. 2. cause backward
> incompatibility.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-12542) Delete a family of table online will crash regionserver
[
https://issues.apache.org/jira/browse/HBASE-12542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071031#comment-16071031
]
Hadoop QA commented on HBASE-12542:
---
| (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:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
3s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} HBASE-12542 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-12542 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12682839/HBASE-12542-v1.diff |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7436/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Delete a family of table online will crash regionserver
>
>
> Key: HBASE-12542
> URL: https://issues.apache.org/jira/browse/HBASE-12542
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Reporter: Liu Shaohui
>Assignee: Liu Shaohui
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-12542-v1.diff
>
>
> Using alter command to delete a family of table online will make the
> regionsevers that serve the regions of the table crash.
> {code}
> alter 't', NAME => 'f', METHOD => 'delete'
> {code}
> The reason is that TableDeleteFamilyHandler in HMaster delete the family dir
> firstly and then reopen all the regions of table.
> When the regionserver reopen the region, it will crash for the exception in
> flushing memstore to hfile of the deleted family during closing the region,
> because the parent dir of the hfile has been deleted in
> TableDeleteFamilyHandler.
> See: TableDeleteFamilyHandler.java #57
> A simple solution is change the order of operations in
> TableDeleteFamilyHandler.
> - update table descriptor first,
> - reopen all the regions,
> - delete the the family dir at last.
> Suggestions are welcomed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
