[jira] [Commented] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073148#comment-16073148 ] Chia-Ping Tsai commented on HBASE-18268: We don't commit the HBASE-18293 to branch-1.3. Will fix it. > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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 > > Attachments: HBASE-18268.branch-1.3.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.branch-1.v0.patch, > HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16073145#comment-16073145
]
Anoop Sam John commented on HBASE-18295:
Thanks for digging in these kind of very difficult to solve bugs.
{code}
// If the top cell won't be flushed into disk,
700 // the new top cell may be changed after #reopenAfterFlush.
701 // Because the older top cell only exist in the memstore
scanner but the memstore
702 // scanner is replaced by hfile scanner after
#reopenAfterFlush.
703 // If the row of top cell is changed, we should return the
current cells.
704 // Otherwise, we may return the cells across different rows.
705 if (!outResult.isEmpty() && topChanged) {
706 return scannerContext.setScannerState(heap.peek() == null ?
707 NextState.NO_MORE_VALUES :
NextState.MORE_VALUES).hasMoreValues();
708 }
{code}
This means we will split that current row into more than one result. In normal
case that would have been going as single result correct. Any way that is
expected at any time as we may do it if that scanner reaches some max result
size or so. But we will mark it correctly? Sorry I did not see in detail the
code part. Just asking after reading ur comments
> 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, 1.4.0, 1.3.2, 2.0.0-alpha-2
>
> Attachments: HBASE-18295.branch-1.3.v0.patch,
> HBASE-18295.branch-1.v0.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch
>
>
> From the [flaky
> dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html]
> If we use the cell which won't be flushed into disk as the top cell to reopen
> the scanners, the new top cell will change. If the new top cell is in
> different row, the matcher will reset, and then matcher will accept the new
> top cell...
> The TestStore# testFlushBeforeCompletingScan reproduces the bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-15042) refactor so that site materials are in the Standard Maven Place
[
https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073130#comment-16073130
]
Jan Hentschel commented on HBASE-15042:
---
I think the first time Git didn't get that it was primarily a renaming instead
of a delete and add.
> refactor so that site materials are in the Standard Maven Place
> ---
>
> Key: HBASE-15042
> URL: https://issues.apache.org/jira/browse/HBASE-15042
> Project: HBase
> Issue Type: Task
> Components: build, website
>Reporter: Sean Busbey
>Assignee: Jan Hentschel
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-15042.master.001.patch,
> HBASE-15042.master.002.patch, HBASE-15042.master.002.patch,
> HBASE-15042.master.003.patch
>
>
> for some reason we currently have our site materials in {{src/main/site}}
> rather than the maven prescribed {{src/site}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18298) RegionServerServices Interface cleanup for CP expose
[ https://issues.apache.org/jira/browse/HBASE-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-18298: --- Attachment: HBASE-18298_V2.patch > RegionServerServices Interface cleanup for CP expose > > > Key: HBASE-18298 > URL: https://issues.apache.org/jira/browse/HBASE-18298 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0 > > Attachments: HBASE-18298.patch, HBASE-18298_V2.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[
https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073111#comment-16073111
]
Hadoop QA commented on HBASE-18268:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
26s{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} 7m
40s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
20s{color} | {color:green} branch-1.3 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
18s{color} | {color:green} branch-1.3 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
37s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
23s{color} | {color:green} branch-1.3 passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
12s{color} | {color:red} hbase-client in branch-1.3 failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} branch-1.3 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
20s{color} | {color:green} branch-1.3 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
15s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
17s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
16m 59s{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} 0m
12s{color} | {color:red} hbase-client in the patch failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
16s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
19s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m
38s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
10s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 32m 0s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:9ba21e3 |
| JIRA Issue | HBASE-18268 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875569/HBASE-18268.branch-1.3.v0.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 34b1bbcb0733 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-18297) Provide a AsyncAdminBuilder to create new AsyncAdmin instance
[
https://issues.apache.org/jira/browse/HBASE-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073104#comment-16073104
]
Hadoop QA commented on HBASE-18297:
---
| (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: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} 4m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
56s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
11s{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}
30m 33s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
47s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 43m 14s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18297 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875566/HBASE-18297.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux e91ee6d11146 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 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 / 99221bd |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7484/artifact/patchprocess/branch-findbugs-hbase-client-warnings.html
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7484/testReport/ |
| modules | C: hbase-client U: hbase-client |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7484/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Provide a AsyncAdminBuilder to create new AsyncAdmin instance
> -
>
> Key: HBASE-18297
>
[jira] [Commented] (HBASE-18294) Flush is based on data size instead of heap size
[ https://issues.apache.org/jira/browse/HBASE-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073103#comment-16073103 ] Anoop Sam John commented on HBASE-18294: We should change the 128 MB flush size default value then? When to be flushed, flushing the one with max data size in it make sense no? Any way after the compacting memstore, we are reducing the heap overhead in btw by in memory flushes. > Flush is based on data size instead of heap size > > > Key: HBASE-18294 > URL: https://issues.apache.org/jira/browse/HBASE-18294 > Project: HBase > Issue Type: Bug >Reporter: Eshcar Hillel >Assignee: Eshcar Hillel > > A region is flushed if its memory component exceed a threshold (default size > is 128MB). > A flush policy decides whether to flush a store by comparing the size of the > store to another threshold (that can be configured with > hbase.hregion.percolumnfamilyflush.size.lower.bound). > Currently the implementation (in both cases) compares the data size > (key-value only) to the threshold where it should compare the heap size > (which includes index size, and metadata). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18312) Ineffective handling of FileNotFoundException in FileLink$FileLinkInputStream.tryOpen()
[
https://issues.apache.org/jira/browse/HBASE-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-18312:
---
Attachment: 18312.v2.txt
> Ineffective handling of FileNotFoundException in
> FileLink$FileLinkInputStream.tryOpen()
> ---
>
> Key: HBASE-18312
> URL: https://issues.apache.org/jira/browse/HBASE-18312
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
> Attachments: 18312.v1.txt, 18312.v2.txt
>
>
> Found the following in region server log:
> {code}
> 2017-07-03 11:22:04,669 WARN
> [regionserver/a.b.c.d:16020-shortCompactions-1499094046361]
> retry.RetryInvocationHandler: Exception while invoking
> ClientNamenodeProtocolTranslatorPB.getBlockLocations over e.f.g.h:8020. Not
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(java.io.FileNotFoundException): File
> does not exist: /hbase/data/default/X/4d61af9d1cbcc5fe2a5cbddbfc92fe7e/
> K/47222a9cbd294f499f49de92ecf330ee
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:71)
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:61)
> ...
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.tryOpen(FileLink.java:291)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:122)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:113)
> at org.apache.hadoop.hbase.io.FileLink.open(FileLink.java:404)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:98)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:83)
> {code}
> Here is related code:
> {code}
> private FSDataInputStream tryOpen() throws IOException {
> for (Path path: fileLink.getLocations()) {
> ...
> } catch (FileNotFoundException e) {
> // Try another file location
> }
> {code}
> The intention is to try possible locations for the linked file.
> However, RemoteException was the exception encountered. This makes the above
> catch clause ineffective.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-15943) Add page displaying JVM process metrics
[ https://issues.apache.org/jira/browse/HBASE-15943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15943: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Release Note: Adds new "Process Metrics' tab along the top which leads to new page that dumps mbean -- mostly jvm -- metrics Status: Resolved (was: Patch Available) Pushed to master and branch-2. Tried it. Looks good. Thanks for the patch [~asamir] > Add page displaying JVM process metrics > --- > > Key: HBASE-15943 > URL: https://issues.apache.org/jira/browse/HBASE-15943 > Project: HBase > Issue Type: New Feature > Components: Operability, UI >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Fix For: 2.0.0 > > Attachments: HBASE-15943-master-03.patch, HBASE-15943_v0.patch, > HBASE-15943_v1.patch, processInfo.png > > > It would be useful to have page displaying some JVM metrics like PID, process > owner. threads info, GC info, etc. This ticked will create two jsp pages (for > master and rs) displaying stats listed above. > - -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18268: --- Attachment: HBASE-18268.branch-1.3.v0.patch > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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 > > Attachments: HBASE-18268.branch-1.3.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.branch-1.v0.patch, > HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18268: --- Status: Patch Available (was: Open) > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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 > > Attachments: HBASE-18268.branch-1.3.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.branch-1.v0.patch, > HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18268: --- Status: Open (was: Patch Available) > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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 > > Attachments: HBASE-18268.branch-1.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15943) Add page displaying JVM process metrics
[ https://issues.apache.org/jira/browse/HBASE-15943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073096#comment-16073096 ] stack commented on HBASE-15943: --- Patch looks good to me. Its just query of mbeans on page draw; innocuous. Looks good. The test failure is a known flakey. I need to fix > Add page displaying JVM process metrics > --- > > Key: HBASE-15943 > URL: https://issues.apache.org/jira/browse/HBASE-15943 > Project: HBase > Issue Type: New Feature > Components: Operability, UI >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Attachments: HBASE-15943-master-03.patch, HBASE-15943_v0.patch, > HBASE-15943_v1.patch, processInfo.png > > > It would be useful to have page displaying some JVM metrics like PID, process > owner. threads info, GC info, etc. This ticked will create two jsp pages (for > master and rs) displaying stats listed above. > - -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18312) Ineffective handling of FileNotFoundException in FileLink$FileLinkInputStream.tryOpen()
[
https://issues.apache.org/jira/browse/HBASE-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073094#comment-16073094
]
Hadoop QA commented on HBASE-18312:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
30s{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: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
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
35s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 6m
32s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
58s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
46s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
48s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 48s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
27s{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:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 2m
38s{color} | {color:red} The patch causes 20 errors with Hadoop v2.6.1. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 5m
17s{color} | {color:red} The patch causes 20 errors with Hadoop v2.6.2. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 8m
3s{color} | {color:red} The patch causes 20 errors with Hadoop v2.6.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 10m
49s{color} | {color:red} The patch causes 20 errors with Hadoop v2.6.4. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 13m
14s{color} | {color:red} The patch causes 20 errors with Hadoop v2.6.5. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 15m
38s{color} | {color:red} The patch causes 20 errors with Hadoop v2.7.1. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 18m
13s{color} | {color:red} The patch causes 20 errors with Hadoop v2.7.2. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 20m
56s{color} | {color:red} The patch causes 20 errors with Hadoop v2.7.3. {color}
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 23m
20s{color} | {color:red} The patch causes 20 errors with Hadoop v3.0.0-alpha3.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
47s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
54s{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 0m 48s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
[jira] [Updated] (HBASE-18241) Change client.Table, client.Admin, Region, and Store to not use HTableDescriptor or HColumnDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18241:
---
Attachment: HBASE-18241.v4.patch
v4.patch
--
# fix the javadoc
# all failed tests pass on my machine.
> Change client.Table, client.Admin, Region, and Store to not use
> HTableDescriptor or HColumnDescriptor
> -
>
> Key: HBASE-18241
> URL: https://issues.apache.org/jira/browse/HBASE-18241
> Project: HBase
> Issue Type: Task
> Components: Client
>Reporter: Biju Nair
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18241.v0.patch, HBASE-18241.v1.patch,
> HBASE-18241.v2.patch, HBASE-18241.v2.patch, HBASE-18241.v3.patch,
> HBASE-18241.v3.patch, HBASE-18241.v4.patch
>
>
> {{HTableDescriptor}} is deprecated and scheduled to be removed in 3.0. But
> [client.Table|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java#L69]
> and
> [client.Admin|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java#L198]
> method {{getTableDescriptor}} returns {{HTableDescriptor}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18241) Change client.Table, client.Admin, Region, and Store to not use HTableDescriptor or HColumnDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18241:
---
Status: Patch Available (was: Open)
> Change client.Table, client.Admin, Region, and Store to not use
> HTableDescriptor or HColumnDescriptor
> -
>
> Key: HBASE-18241
> URL: https://issues.apache.org/jira/browse/HBASE-18241
> Project: HBase
> Issue Type: Task
> Components: Client
>Reporter: Biju Nair
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18241.v0.patch, HBASE-18241.v1.patch,
> HBASE-18241.v2.patch, HBASE-18241.v2.patch, HBASE-18241.v3.patch,
> HBASE-18241.v3.patch, HBASE-18241.v4.patch
>
>
> {{HTableDescriptor}} is deprecated and scheduled to be removed in 3.0. But
> [client.Table|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java#L69]
> and
> [client.Admin|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java#L198]
> method {{getTableDescriptor}} returns {{HTableDescriptor}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18241) Change client.Table, client.Admin, Region, and Store to not use HTableDescriptor or HColumnDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18241:
---
Status: Open (was: Patch Available)
> Change client.Table, client.Admin, Region, and Store to not use
> HTableDescriptor or HColumnDescriptor
> -
>
> Key: HBASE-18241
> URL: https://issues.apache.org/jira/browse/HBASE-18241
> Project: HBase
> Issue Type: Task
> Components: Client
>Reporter: Biju Nair
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18241.v0.patch, HBASE-18241.v1.patch,
> HBASE-18241.v2.patch, HBASE-18241.v2.patch, HBASE-18241.v3.patch,
> HBASE-18241.v3.patch
>
>
> {{HTableDescriptor}} is deprecated and scheduled to be removed in 3.0. But
> [client.Table|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java#L69]
> and
> [client.Admin|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java#L198]
> method {{getTableDescriptor}} returns {{HTableDescriptor}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18297) Provide a AsyncAdminBuilder to create new AsyncAdmin instance
[ https://issues.apache.org/jira/browse/HBASE-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18297: --- Fix Version/s: (was: 2.0.0) 2.0.0-alpha-2 3.0.0 > Provide a AsyncAdminBuilder to create new AsyncAdmin instance > - > > Key: HBASE-18297 > URL: https://issues.apache.org/jira/browse/HBASE-18297 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18297.master.001.patch > > > Similar with AsyncTableBuilder, user can only set the configs they care about > when create a new AsyncAdmin instance. It is easy to update the rpc timeout > or operation timeout config when they take some time-consuming admin > operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18297) Provide a AsyncAdminBuilder to create new AsyncAdmin instance
[ https://issues.apache.org/jira/browse/HBASE-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18297: --- Attachment: HBASE-18297.master.001.patch > Provide a AsyncAdminBuilder to create new AsyncAdmin instance > - > > Key: HBASE-18297 > URL: https://issues.apache.org/jira/browse/HBASE-18297 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-18297.master.001.patch > > > Similar with AsyncTableBuilder, user can only set the configs they care about > when create a new AsyncAdmin instance. It is easy to update the rpc timeout > or operation timeout config when they take some time-consuming admin > operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18297) Provide a AsyncAdminBuilder to create new AsyncAdmin instance
[ https://issues.apache.org/jira/browse/HBASE-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18297: --- Status: Patch Available (was: Open) > Provide a AsyncAdminBuilder to create new AsyncAdmin instance > - > > Key: HBASE-18297 > URL: https://issues.apache.org/jira/browse/HBASE-18297 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-18297.master.001.patch > > > Similar with AsyncTableBuilder, user can only set the configs they care about > when create a new AsyncAdmin instance. It is easy to update the rpc timeout > or operation timeout config when they take some time-consuming admin > operations. -- 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=16073079#comment-16073079 ] stack commented on HBASE-7386: -- Thank you [~asamir] > 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-18312) Ineffective handling of FileNotFoundException in FileLink$FileLinkInputStream.tryOpen()
[
https://issues.apache.org/jira/browse/HBASE-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-18312:
---
Attachment: 18312.v1.txt
> Ineffective handling of FileNotFoundException in
> FileLink$FileLinkInputStream.tryOpen()
> ---
>
> Key: HBASE-18312
> URL: https://issues.apache.org/jira/browse/HBASE-18312
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
> Attachments: 18312.v1.txt
>
>
> Found the following in region server log:
> {code}
> 2017-07-03 11:22:04,669 WARN
> [regionserver/a.b.c.d:16020-shortCompactions-1499094046361]
> retry.RetryInvocationHandler: Exception while invoking
> ClientNamenodeProtocolTranslatorPB.getBlockLocations over e.f.g.h:8020. Not
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(java.io.FileNotFoundException): File
> does not exist: /hbase/data/default/X/4d61af9d1cbcc5fe2a5cbddbfc92fe7e/
> K/47222a9cbd294f499f49de92ecf330ee
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:71)
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:61)
> ...
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.tryOpen(FileLink.java:291)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:122)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:113)
> at org.apache.hadoop.hbase.io.FileLink.open(FileLink.java:404)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:98)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:83)
> {code}
> Here is related code:
> {code}
> private FSDataInputStream tryOpen() throws IOException {
> for (Path path: fileLink.getLocations()) {
> ...
> } catch (FileNotFoundException e) {
> // Try another file location
> }
> {code}
> The intention is to try possible locations for the linked file.
> However, RemoteException was the exception encountered. This makes the above
> catch clause ineffective.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18312) Ineffective handling of FileNotFoundException in FileLink$FileLinkInputStream.tryOpen()
[
https://issues.apache.org/jira/browse/HBASE-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-18312:
---
Status: Patch Available (was: Open)
> Ineffective handling of FileNotFoundException in
> FileLink$FileLinkInputStream.tryOpen()
> ---
>
> Key: HBASE-18312
> URL: https://issues.apache.org/jira/browse/HBASE-18312
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
> Attachments: 18312.v1.txt
>
>
> Found the following in region server log:
> {code}
> 2017-07-03 11:22:04,669 WARN
> [regionserver/a.b.c.d:16020-shortCompactions-1499094046361]
> retry.RetryInvocationHandler: Exception while invoking
> ClientNamenodeProtocolTranslatorPB.getBlockLocations over e.f.g.h:8020. Not
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(java.io.FileNotFoundException): File
> does not exist: /hbase/data/default/X/4d61af9d1cbcc5fe2a5cbddbfc92fe7e/
> K/47222a9cbd294f499f49de92ecf330ee
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:71)
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:61)
> ...
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.tryOpen(FileLink.java:291)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:122)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:113)
> at org.apache.hadoop.hbase.io.FileLink.open(FileLink.java:404)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:98)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:83)
> {code}
> Here is related code:
> {code}
> private FSDataInputStream tryOpen() throws IOException {
> for (Path path: fileLink.getLocations()) {
> ...
> } catch (FileNotFoundException e) {
> // Try another file location
> }
> {code}
> The intention is to try possible locations for the linked file.
> However, RemoteException was the exception encountered. This makes the above
> catch clause ineffective.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18312) Ineffective handling of FileNotFoundException in FileLink$FileLinkInputStream.tryOpen()
[
https://issues.apache.org/jira/browse/HBASE-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073065#comment-16073065
]
Ted Yu commented on HBASE-18312:
RemoteExceptionHandler.checkIOException(ex) should be used to decode
RemoteException.
> Ineffective handling of FileNotFoundException in
> FileLink$FileLinkInputStream.tryOpen()
> ---
>
> Key: HBASE-18312
> URL: https://issues.apache.org/jira/browse/HBASE-18312
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>
> Found the following in region server log:
> {code}
> 2017-07-03 11:22:04,669 WARN
> [regionserver/a.b.c.d:16020-shortCompactions-1499094046361]
> retry.RetryInvocationHandler: Exception while invoking
> ClientNamenodeProtocolTranslatorPB.getBlockLocations over e.f.g.h:8020. Not
> retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(java.io.FileNotFoundException): File
> does not exist: /hbase/data/default/X/4d61af9d1cbcc5fe2a5cbddbfc92fe7e/
> K/47222a9cbd294f499f49de92ecf330ee
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:71)
> at
> org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:61)
> ...
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.tryOpen(FileLink.java:291)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:122)
> at
> org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:113)
> at org.apache.hadoop.hbase.io.FileLink.open(FileLink.java:404)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:98)
> at
> org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:83)
> {code}
> Here is related code:
> {code}
> private FSDataInputStream tryOpen() throws IOException {
> for (Path path: fileLink.getLocations()) {
> ...
> } catch (FileNotFoundException e) {
> // Try another file location
> }
> {code}
> The intention is to try possible locations for the linked file.
> However, RemoteException was the exception encountered. This makes the above
> catch clause ineffective.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18313) [hbase-thirdparty] Produce src jars/tgz
stack created HBASE-18313: - Summary: [hbase-thirdparty] Produce src jars/tgz Key: HBASE-18313 URL: https://issues.apache.org/jira/browse/HBASE-18313 Project: HBase Issue Type: Bug Components: hbase-thirdparty Reporter: stack In IDEs when want to dig in on protobuf or guava, need src jars. Currently we don't generate them. Generate them in next release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18312) Ineffective handling of FileNotFoundException in FileLink$FileLinkInputStream.tryOpen()
Ted Yu created HBASE-18312:
--
Summary: Ineffective handling of FileNotFoundException in
FileLink$FileLinkInputStream.tryOpen()
Key: HBASE-18312
URL: https://issues.apache.org/jira/browse/HBASE-18312
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Found the following in region server log:
{code}
2017-07-03 11:22:04,669 WARN
[regionserver/a.b.c.d:16020-shortCompactions-1499094046361]
retry.RetryInvocationHandler: Exception while invoking
ClientNamenodeProtocolTranslatorPB.getBlockLocations over e.f.g.h:8020. Not
retrying because try once and fail.
org.apache.hadoop.ipc.RemoteException(java.io.FileNotFoundException): File does
not exist: /hbase/data/default/X/4d61af9d1cbcc5fe2a5cbddbfc92fe7e/
K/47222a9cbd294f499f49de92ecf330ee
at org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:71)
at org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:61)
...
at
org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.tryOpen(FileLink.java:291)
at
org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:122)
at
org.apache.hadoop.hbase.io.FileLink$FileLinkInputStream.(FileLink.java:113)
at org.apache.hadoop.hbase.io.FileLink.open(FileLink.java:404)
at
org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:98)
at
org.apache.hadoop.hbase.io.FSDataInputStreamWrapper.(FSDataInputStreamWrapper.java:83)
{code}
Here is related code:
{code}
private FSDataInputStream tryOpen() throws IOException {
for (Path path: fileLink.getLocations()) {
...
} catch (FileNotFoundException e) {
// Try another file location
}
{code}
The intention is to try possible locations for the linked file.
However, RemoteException was the exception encountered. This makes the above
catch clause ineffective.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-15042) refactor so that site materials are in the Standard Maven Place
[
https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073058#comment-16073058
]
stack commented on HBASE-15042:
---
What the old patches 6.7MB and new is 31kb? Thanks [~Jan Hentschel]
> refactor so that site materials are in the Standard Maven Place
> ---
>
> Key: HBASE-15042
> URL: https://issues.apache.org/jira/browse/HBASE-15042
> Project: HBase
> Issue Type: Task
> Components: build, website
>Reporter: Sean Busbey
>Assignee: Jan Hentschel
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-15042.master.001.patch,
> HBASE-15042.master.002.patch, HBASE-15042.master.002.patch,
> HBASE-15042.master.003.patch
>
>
> for some reason we currently have our site materials in {{src/main/site}}
> rather than the maven prescribed {{src/site}}.
--
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=16073049#comment-16073049 ] stack commented on HBASE-18266: --- [~chia7712] Thanks for noticing. Fixed. > 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 > > > 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] [Assigned] (HBASE-18297) Provide a AsyncAdminBuilder to create new AsyncAdmin instance
[ https://issues.apache.org/jira/browse/HBASE-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-18297: -- Assignee: Guanghao Zhang > Provide a AsyncAdminBuilder to create new AsyncAdmin instance > - > > Key: HBASE-18297 > URL: https://issues.apache.org/jira/browse/HBASE-18297 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > > Similar with AsyncTableBuilder, user can only set the configs they care about > when create a new AsyncAdmin instance. It is easy to update the rpc timeout > or operation timeout config when they take some time-consuming admin > operations. -- 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: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: (was: 3.0.0) Status: Resolved (was: Patch Available) Pushed to master and branch-2 (sick of retry... will deal w/ any replications as new issue) > 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 > > 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, 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-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16073042#comment-16073042 ] Guanghao Zhang commented on HBASE-18229: [~easyliangjob] As I am developing the async hbase admin, so the code base maybe changed. Please rebase the latest code when you prepare a new patch :-). Thanks. > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (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:all-tabpanel ] Guanghao Zhang updated HBASE-18283: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: (was: 2.0.0) 2.0.0-alpha-2 Status: Resolved (was: Patch Available) Pushed to branch-2 and master. Thanks [~stack] and [~Apache9] for reviewing. > 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: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18283.master.001.patch, > HBASE-18283.master.002.patch, HBASE-18283.master.003.patch, > HBASE-18283.master.003.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-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=16073012#comment-16073012 ] Duo Zhang commented on HBASE-18283: --- +1. Nice work. > 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, HBASE-18283.master.003.patch, > HBASE-18283.master.003.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-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=16073008#comment-16073008 ] Guanghao Zhang commented on HBASE-18283: I will fix the whitespace when commit. Thanks. > 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, HBASE-18283.master.003.patch, > HBASE-18283.master.003.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] [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) 'Submit patch' again > 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: 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] [Commented] (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:comment-tabpanel=16072984#comment-16072984 ] Andrew Purtell commented on HBASE-18248: Any concerns about the updated patches? Let me kick precommit again. > 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] [Commented] (HBASE-18311) clean up the quickstart guide
[ https://issues.apache.org/jira/browse/HBASE-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072979#comment-16072979 ] Hudson commented on HBASE-18311: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3307 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3307/]) HBASE-18311 fix formatting in quickstart (tedyu: rev 8318a092acb12a7d078b382f45db50dcb59263b2) * (edit) src/main/asciidoc/_chapters/getting_started.adoc > clean up the quickstart guide > - > > Key: HBASE-18311 > URL: https://issues.apache.org/jira/browse/HBASE-18311 > 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 > Fix For: 3.0.0 > > Attachments: HBASE-18311.patch > > > extra commas, period, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072913#comment-16072913 ] Peter Somogyi commented on HBASE-18291: --- I'm glad I could contribute! Looks like build stuck for this patch. Could you abort it? https://builds.apache.org/job/PreCommit-HBASE-Build/7481 > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18291.master.001.patch > > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-18311) clean up the quickstart guide
[ https://issues.apache.org/jira/browse/HBASE-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved HBASE-18311. Resolution: Fixed Hadoop Flags: Reviewed Thanks for the patch, Artem. > clean up the quickstart guide > - > > Key: HBASE-18311 > URL: https://issues.apache.org/jira/browse/HBASE-18311 > 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 > Fix For: 3.0.0 > > Attachments: HBASE-18311.patch > > > extra commas, period, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18311) clean up the quickstart guide
[ https://issues.apache.org/jira/browse/HBASE-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18311: --- Priority: Major (was: Blocker) > clean up the quickstart guide > - > > Key: HBASE-18311 > URL: https://issues.apache.org/jira/browse/HBASE-18311 > 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 > Fix For: 3.0.0 > > Attachments: HBASE-18311.patch > > > extra commas, period, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18291: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the patch, Peter. > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18291.master.001.patch > > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072856#comment-16072856 ] Hudson commented on HBASE-18291: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3306 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3306/]) HBASE-18291 Regenerate thrift2 python examples (tedyu: rev 61534931cc0c1c4f51c71ff5447cbecff73cc3ab) * (edit) hbase-examples/src/main/python/thrift2/gen-py/hbase/THBaseService.py * (edit) hbase-examples/src/main/python/thrift2/gen-py/hbase/constants.py * (edit) hbase-examples/src/main/python/thrift2/gen-py/hbase/THBaseService-remote * (edit) hbase-examples/src/main/python/thrift2/DemoClient.py * (edit) hbase-examples/src/main/python/thrift2/gen-py/hbase/ttypes.py > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18291.master.001.patch > > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18311) clean up the quickstart guide
[ https://issues.apache.org/jira/browse/HBASE-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Ervits updated HBASE-18311: - Attachment: HBASE-18311.patch > clean up the quickstart guide > - > > Key: HBASE-18311 > URL: https://issues.apache.org/jira/browse/HBASE-18311 > 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 > Fix For: 3.0.0 > > Attachments: HBASE-18311.patch > > > extra commas, period, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18311) clean up the quickstart guide
Artem Ervits created HBASE-18311: Summary: clean up the quickstart guide Key: HBASE-18311 URL: https://issues.apache.org/jira/browse/HBASE-18311 Project: HBase Issue Type: Bug Components: documentation Affects Versions: 2.0.0-alpha-1, 1.1.11, 1.2.6, 1.3.1 Reporter: Artem Ervits Assignee: Artem Ervits Priority: Blocker Fix For: 3.0.0 extra commas, period, etc. -- 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=16072789#comment-16072789 ] Samir Ahmic commented on HBASE-7386: [~stack] anything improving MTTR and cluster operability deserves decent retry :), i will take look at work done here and check if same or similar concept can be applied at current hbase clusters. > 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] [Commented] (HBASE-17738) BucketCache startup is slow
[ https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072772#comment-16072772 ] ramkrishna.s.vasudevan commented on HBASE-17738: Ping for reviews [~anoop.hbase]. > BucketCache startup is slow > --- > > Key: HBASE-17738 > URL: https://issues.apache.org/jira/browse/HBASE-17738 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Affects Versions: 2.0.0 >Reporter: stack >Assignee: ramkrishna.s.vasudevan > Fix For: 2.0.0 > > Attachments: HBASE-17738_2.patch, HBASE-17738_2.patch, > HBASE-17738_3.patch, HBASE-17738_4.patch, HBASE-17738_5_withoutUnsafe.patch, > HBASE-17738_6_withoutUnsafe.patch, HBASE-17738.patch > > > If you set bucketcache size at 64G say and then start hbase, it takes a long > time. Can we do the allocations in parallel and not inline with the server > startup? > Related, prefetching on a bucketcache is slow. Speed it up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15943) Add page displaying JVM process metrics
[ https://issues.apache.org/jira/browse/HBASE-15943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072769#comment-16072769 ] Samir Ahmic commented on HBASE-15943: - Failures look unrelated to patch. [~stack] i have also tested this patch against branch-2 and applies correctly, ping me if any additional work is required. > Add page displaying JVM process metrics > --- > > Key: HBASE-15943 > URL: https://issues.apache.org/jira/browse/HBASE-15943 > Project: HBase > Issue Type: New Feature > Components: Operability, UI >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Attachments: HBASE-15943-master-03.patch, HBASE-15943_v0.patch, > HBASE-15943_v1.patch, processInfo.png > > > It would be useful to have page displaying some JVM metrics like PID, process > owner. threads info, GC info, etc. This ticked will create two jsp pages (for > master and rs) displaying stats listed above. > - -- 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=16072751#comment-16072751
]
Hadoop QA commented on HBASE-18283:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
11s{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 9 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
27s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
57s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 3m
1s{color} | {color:red} hbase-server in master has 10 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
56s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
33m 33s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
40s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}120m
58s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
33s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}179m 10s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18283 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875516/HBASE-18283.master.003.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 455ac161c777 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 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 / ba54af3 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| findbugs |
[jira] [Commented] (HBASE-15042) refactor so that site materials are in the Standard Maven Place
[
https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072661#comment-16072661
]
Hadoop QA commented on HBASE-15042:
---
| (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:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
5s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color: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
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 23m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 22m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
7s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 46 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
1s{color} | {color:red} The patch 95 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
35s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
29m 24s{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} 2m
8s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 94m 25s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
20s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}189m 34s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestMasterProcedureWalLease |
| Timed out junit tests | org.apache.hadoop.hbase.backup.TestRemoteRestore |
| | org.apache.hadoop.hbase.backup.master.TestBackupLogCleaner |
| | org.apache.hadoop.hbase.TestAcidGuarantees |
| | org.apache.hadoop.hbase.backup.TestIncrementalBackup |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-15042 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875494/HBASE-15042.master.003.patch
|
| Optional Tests | asflicense shellcheck shelldocs javac javadoc unit
xml compile mvnsite |
| uname | Linux 750b6b9ff4b8 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 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 / ba54af3 |
| Default Java | 1.8.0_131 |
| shellcheck | v0.4.6 |
| whitespace |
[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=16072581#comment-16072581 ] Hudson commented on HBASE-18023: SUCCESS: Integrated in Jenkins build HBase-1.3-IT #130 (See [https://builds.apache.org/job/HBase-1.3-IT/130/]) 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-18041) Add pylintrc file to HBase
[ https://issues.apache.org/jira/browse/HBASE-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072580#comment-16072580 ] Hudson commented on HBASE-18041: SUCCESS: Integrated in Jenkins build HBase-1.3-IT #130 (See [https://builds.apache.org/job/HBase-1.3-IT/130/]) HBASE-18041 Add .pylintrc to HBase (busbey: rev 8d40b2d98ffc6b2b522f6b1efdfca46e3ace977e) * (add) .pylintrc > Add pylintrc file to HBase > -- > > Key: HBASE-18041 > URL: https://issues.apache.org/jira/browse/HBASE-18041 > Project: HBase > Issue Type: Improvement > Components: community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: diff-patch-pylint-noRC.txt, diff-patch-pylint.txt, > HBASE-18041.branch-1.2.001.patch > > > Yetus runs all commits with python files through a linter. I think that the > HBase community should add a pylintrc file to actively choose the project's > python style instead of just relying on yetus defaults. > As an argument for this, the yetus project itself doesn't even use the > default python linter for its own commits. -- 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=16072537#comment-16072537
]
Hadoop QA commented on HBASE-18283:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
34s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 9 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
36s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
10s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
36s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 7m
59s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
11s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
39s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
72m 59s{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} 9m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
17s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}202m 44s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
1s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}331m 31s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestPerColumnFamilyFlush |
| | hadoop.hbase.security.access.TestCoprocessorWhitelistMasterObserver |
| Timed out junit tests | org.apache.hadoop.hbase.client.TestFromClientSide |
| | org.apache.hadoop.hbase.replication.regionserver.TestWALEntryStream |
| | org.apache.hadoop.hbase.util.TestMiniClusterLoadEncoded |
| | org.apache.hadoop.hbase.quotas.TestSpaceQuotas |
| | org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe |
| | org.apache.hadoop.hbase.filter.TestFuzzyRowFilterEndToEnd |
| | org.apache.hadoop.hbase.util.TestFSUtils |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18283 |
| JIRA Patch URL |
[jira] [Commented] (HBASE-15943) Add page displaying JVM process metrics
[
https://issues.apache.org/jira/browse/HBASE-15943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072519#comment-16072519
]
Hadoop QA commented on HBASE-15943:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
11s{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} 4m
4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 3m
7s{color} | {color:red} hbase-server in master has 10 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
51s{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
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
33m 41s{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} 3m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
40s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}126m 24s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}177m 33s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestMasterProcedureWalLease |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-15943 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875483/HBASE-15943-master-03.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux c3ff08edb805 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 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 / ba54af3 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7478/artifact/patchprocess/branch-findbugs-hbase-server-warnings.html
|
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/7478/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7478/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7478/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Add page displaying JVM process metrics
>
[jira] [Updated] (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:all-tabpanel ] Guanghao Zhang updated HBASE-18283: --- Attachment: HBASE-18283.master.003.patch > 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, HBASE-18283.master.003.patch, > HBASE-18283.master.003.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-18264) Update pom plugins
[
https://issues.apache.org/jira/browse/HBASE-18264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072507#comment-16072507
]
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
15s{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
23s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 11m
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 7m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 9m
31s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 10m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 10m
45s{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
31s{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
10s{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
20s{color} | {color:green} hbase-protocol in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
17s{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
44s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
22s{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
17s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
14s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
19s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
18s{color} | {color:green} hbase-it in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
16s{color} | {color:green} hbase-examples in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
19s{color} | {color:green} hbase-rest in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
12s{color} | {color:green} hbase-external-blockcache in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
59s{color} | {color:green}
[jira] [Commented] (HBASE-17738) BucketCache startup is slow
[
https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072499#comment-16072499
]
Hadoop QA commented on HBASE-17738:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
49s{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
30s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
49s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
21s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
34s{color} | {color:red} hbase-common in master has 2 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
49s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
49s{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
28s{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}
77m 39s{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
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
32s{color} | {color:green} hbase-common in the patch passed. {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}103m 3s{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-17738 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875492/HBASE-17738_6_withoutUnsafe.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 2fed48ea2677 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 / ba54af3 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7479/artifact/patchprocess/branch-findbugs-hbase-common-warnings.html
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7479/testReport/ |
| modules | C: hbase-common U: hbase-common |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7479/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> BucketCache startup is slow
> ---
>
> Key: HBASE-17738
> URL: https://issues.apache.org/jira/browse/HBASE-17738
>
[jira] [Commented] (HBASE-18294) Flush is based on data size instead of heap size
[ https://issues.apache.org/jira/browse/HBASE-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072467#comment-16072467 ] Eshcar Hillel commented on HBASE-18294: --- The per-cell metadata overhead with basic compaction is about 60B. This means that with small values metadata can easily double the heap occupancy of the memstore. bq. When the data size of the memstore is high (choosing one to flush), the heap occupancy of it also will be on higher side no? Not necessarily. It depends on the size of the values. one memstore can have 50MB data and 100MB total heap size while another memstore has 70MB data and only 80MB total heap size. bq. considering data size only for the per region flush decision is more inline with a normal user thinking. Not necessarily. Here are 2 blogs which consider 128MB to be the total memstore occupancy: https://www.quora.com/HBase-Region-Server-guidelines-give-a-size-range-of-about-1TB-whereas-data-nodes-are-configured-20-times-bigger-Why by [~larsgeorge] _"we can address 4GB of heap for writes, allowing us up to have 32 regions that are written to while flushing at 128MB"_ http://hadoop-hbase.blogspot.co.uk/2013/01/hbase-region-server-memory-sizing.html by [~lhofhansl] _"... you'd need ~338 regions. @128MB that's about 43GB"_ Users who came to understand HBase through this kind of blogs expect a region (memstore) not to exceed the 128MB threshold. With the current implementation all places including regular and blocking thresholds at the region level and both selection policies at the RS-region and region-store level consider data size and not heap size. > Flush is based on data size instead of heap size > > > Key: HBASE-18294 > URL: https://issues.apache.org/jira/browse/HBASE-18294 > Project: HBase > Issue Type: Bug >Reporter: Eshcar Hillel >Assignee: Eshcar Hillel > > A region is flushed if its memory component exceed a threshold (default size > is 128MB). > A flush policy decides whether to flush a store by comparing the size of the > store to another threshold (that can be configured with > hbase.hregion.percolumnfamilyflush.size.lower.bound). > Currently the implementation (in both cases) compares the data size > (key-value only) to the threshold where it should compare the heap size > (which includes index size, and metadata). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi updated HBASE-18291: -- Fix Version/s: 2.0.0-alpha-2 3.0.0 Status: Patch Available (was: In Progress) > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18291.master.001.patch > > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072430#comment-16072430 ] Peter Somogyi commented on HBASE-18291: --- Patch also available on review board: https://reviews.apache.org/r/60599/ > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > Attachments: HBASE-18291.master.001.patch > > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-18291 started by Peter Somogyi. - > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi updated HBASE-18291: -- Attachment: HBASE-18291.master.001.patch > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > Attachments: HBASE-18291.master.001.patch > > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16072403#comment-16072403 ] Chia-Ping Tsai commented on HBASE-18295: bq. You mean with INCLUDE_NEXT_COL case Yes, I meant it (INCLUDE_AND_SEEK_NEXT_COL). Sorry for my mess-up. > 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, 1.4.0, 1.3.2, 2.0.0-alpha-2 > > Attachments: HBASE-18295.branch-1.3.v0.patch, > HBASE-18295.branch-1.v0.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] > If we use the cell which won't be flushed into disk as the top cell to reopen > the scanners, the new top cell will change. If the new top cell is in > different row, the matcher will reset, and then matcher will accept the new > top cell... > The TestStore# testFlushBeforeCompletingScan reproduces the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18310) LoadTestTool unable to write data
Samir Ahmic created HBASE-18310:
---
Summary: LoadTestTool unable to write data
Key: HBASE-18310
URL: https://issues.apache.org/jira/browse/HBASE-18310
Project: HBase
Issue Type: Bug
Components: util
Affects Versions: 2.0.0-alpha-1, 3.0.0
Reporter: Samir Ahmic
Assignee: Samir Ahmic
I was trying to write some data to cluster with hbase ltt but i have this one:
{code}
$ hbase ltt -write 3:30:10 -num_keys 100
2017-07-03 14:40:47,372 ERROR [main] util.AbstractHBaseTool: Error running
command-line tool
java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
at
org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
at
org.apache.hadoop.hbase.HColumnDescriptor.setBloomFilterType(HColumnDescriptor.java:475)
at
org.apache.hadoop.hbase.util.LoadTestTool.applyColumnFamilyOptions(LoadTestTool.java:288)
at
org.apache.hadoop.hbase.util.LoadTestTool.initTestTable(LoadTestTool.java:557)
at
org.apache.hadoop.hbase.util.LoadTestTool.loadTable(LoadTestTool.java:584)
at
org.apache.hadoop.hbase.util.LoadTestTool.doWork(LoadTestTool.java:565)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.doStaticMain(AbstractHBaseTool.java:262)
at org.apache.hadoop.hbase.util.LoadTestTool.main(LoadTestTool.java:831)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-15042) refactor so that site materials are in the Standard Maven Place
[
https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072359#comment-16072359
]
Hadoop QA commented on HBASE-15042:
---
(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at
https://builds.apache.org/job/PreCommit-HBASE-Build/7480/console in case of
problems.
> refactor so that site materials are in the Standard Maven Place
> ---
>
> Key: HBASE-15042
> URL: https://issues.apache.org/jira/browse/HBASE-15042
> Project: HBase
> Issue Type: Task
> Components: build, website
>Reporter: Sean Busbey
>Assignee: Jan Hentschel
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-15042.master.001.patch,
> HBASE-15042.master.002.patch, HBASE-15042.master.002.patch,
> HBASE-15042.master.003.patch
>
>
> for some reason we currently have our site materials in {{src/main/site}}
> rather than the maven prescribed {{src/site}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16072360#comment-16072360 ] ramkrishna.s.vasudevan commented on HBASE-18295: bq.If the cell is INCLUDED, it will be flushed into the disk. Am not sure I get the context here. You mean with INCLUDE_NEXT_COL case this won't happen at all? Let me read the code once 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, 1.4.0, 1.3.2, 2.0.0-alpha-2 > > Attachments: HBASE-18295.branch-1.3.v0.patch, > HBASE-18295.branch-1.v0.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] > If we use the cell which won't be flushed into disk as the top cell to reopen > the scanners, the new top cell will change. If the new top cell is in > different row, the matcher will reset, and then matcher will accept the new > top cell... > The TestStore# testFlushBeforeCompletingScan reproduces the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-15042) refactor so that site materials are in the Standard Maven Place
[
https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-15042:
--
Attachment: HBASE-15042.master.003.patch
> refactor so that site materials are in the Standard Maven Place
> ---
>
> Key: HBASE-15042
> URL: https://issues.apache.org/jira/browse/HBASE-15042
> Project: HBase
> Issue Type: Task
> Components: build, website
>Reporter: Sean Busbey
>Assignee: Jan Hentschel
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-15042.master.001.patch,
> HBASE-15042.master.002.patch, HBASE-15042.master.002.patch,
> HBASE-15042.master.003.patch
>
>
> for some reason we currently have our site materials in {{src/main/site}}
> rather than the maven prescribed {{src/site}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-17738) BucketCache startup is slow
[ https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-17738: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open) > BucketCache startup is slow > --- > > Key: HBASE-17738 > URL: https://issues.apache.org/jira/browse/HBASE-17738 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Affects Versions: 2.0.0 >Reporter: stack >Assignee: ramkrishna.s.vasudevan > Fix For: 2.0.0 > > Attachments: HBASE-17738_2.patch, HBASE-17738_2.patch, > HBASE-17738_3.patch, HBASE-17738_4.patch, HBASE-17738_5_withoutUnsafe.patch, > HBASE-17738_6_withoutUnsafe.patch, HBASE-17738.patch > > > If you set bucketcache size at 64G say and then start hbase, it takes a long > time. Can we do the allocations in parallel and not inline with the server > startup? > Related, prefetching on a bucketcache is slow. Speed it up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17738) BucketCache startup is slow
[ https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-17738: --- Attachment: HBASE-17738_6_withoutUnsafe.patch Patch that splits the buffer creation based on the number of threads and creates only those many callables as the number of threads. This one and the previous patch both takes 11 secs only. How ever before the patch it was taking 34secs. The previous patch was easy to read and this has certain index manipulation to be done. > BucketCache startup is slow > --- > > Key: HBASE-17738 > URL: https://issues.apache.org/jira/browse/HBASE-17738 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Affects Versions: 2.0.0 >Reporter: stack >Assignee: ramkrishna.s.vasudevan > Fix For: 2.0.0 > > Attachments: HBASE-17738_2.patch, HBASE-17738_2.patch, > HBASE-17738_3.patch, HBASE-17738_4.patch, HBASE-17738_5_withoutUnsafe.patch, > HBASE-17738_6_withoutUnsafe.patch, HBASE-17738.patch > > > If you set bucketcache size at 64G say and then start hbase, it takes a long > time. Can we do the allocations in parallel and not inline with the server > startup? > Related, prefetching on a bucketcache is slow. Speed it up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17738) BucketCache startup is slow
[ https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-17738: --- Status: Open (was: Patch Available) > BucketCache startup is slow > --- > > Key: HBASE-17738 > URL: https://issues.apache.org/jira/browse/HBASE-17738 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Affects Versions: 2.0.0 >Reporter: stack >Assignee: ramkrishna.s.vasudevan > Fix For: 2.0.0 > > Attachments: HBASE-17738_2.patch, HBASE-17738_2.patch, > HBASE-17738_3.patch, HBASE-17738_4.patch, HBASE-17738_5_withoutUnsafe.patch, > HBASE-17738.patch > > > If you set bucketcache size at 64G say and then start hbase, it takes a long > time. Can we do the allocations in parallel and not inline with the server > startup? > Related, prefetching on a bucketcache is slow. Speed it up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18298) RegionServerServices Interface cleanup for CP expose
[
https://issues.apache.org/jira/browse/HBASE-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072318#comment-16072318
]
Hadoop QA commented on HBASE-18298:
---
| (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 21 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
32s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
30s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
57s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
38s{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
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
27s{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}
30m 39s{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:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
56s{color} | {color:red} hbase-server generated 1 new + 10 unchanged - 0 fixed
= 11 total (was 10) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 45m 40s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 7m 34s{color}
| {color:red} hbase-endpoint in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}105m 8s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | instanceof will always return true for all non-null values in new
org.apache.hadoop.hbase.regionserver.HRegion(HRegionFileSystem, WAL,
Configuration, HTableDescriptor, InternalRegionServerServices), since all
org.apache.hadoop.hbase.regionserver.InternalRegionServerServices are instances
of org.apache.hadoop.hbase.regionserver.InternalRegionServerServices At
HRegion.java:for all non-null values in new
org.apache.hadoop.hbase.regionserver.HRegion(HRegionFileSystem, WAL,
Configuration, HTableDescriptor, InternalRegionServerServices), since all
org.apache.hadoop.hbase.regionserver.InternalRegionServerServices are instances
of org.apache.hadoop.hbase.regionserver.InternalRegionServerServices At
HRegion.java:[line 791] |
| Failed junit tests | hadoop.hbase.regionserver.TestBlocksScanned |
| | hadoop.hbase.coprocessor.TestCoprocessorInterface |
| | hadoop.hbase.master.locking.TestLockManager |
| |
[jira] [Commented] (HBASE-10147) Canary additions
[ https://issues.apache.org/jira/browse/HBASE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072299#comment-16072299 ] Gustavo Anatoly commented on HBASE-10147: - Hi, [~stack] Thanks for comment :) I'm going to rebase and prepare a new patch. > 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] [Assigned] (HBASE-18291) Regenerate thrift2 python examples
[ https://issues.apache.org/jira/browse/HBASE-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi reassigned HBASE-18291: - Assignee: Peter Somogyi > Regenerate thrift2 python examples > -- > > Key: HBASE-18291 > URL: https://issues.apache.org/jira/browse/HBASE-18291 > Project: HBase > Issue Type: Task >Reporter: Ted Yu >Assignee: Peter Somogyi >Priority: Minor > > Looking at the files under > hbase-examples/src/main/python/thrift2/gen-py/hbase, they were last updated > in 2013. > Now that we use thrift 0.9.3, we should regenerate these examples based on > the latest thrift definition. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-15943) Add page displaying JVM process metrics
[ https://issues.apache.org/jira/browse/HBASE-15943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samir Ahmic updated HBASE-15943: Attachment: HBASE-15943-master-03.patch New patch for master branch. > Add page displaying JVM process metrics > --- > > Key: HBASE-15943 > URL: https://issues.apache.org/jira/browse/HBASE-15943 > Project: HBase > Issue Type: New Feature > Components: Operability, UI >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Attachments: HBASE-15943-master-03.patch, HBASE-15943_v0.patch, > HBASE-15943_v1.patch, processInfo.png > > > It would be useful to have page displaying some JVM metrics like PID, process > owner. threads info, GC info, etc. This ticked will create two jsp pages (for > master and rs) displaying stats listed above. > - -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18241) Change client.Table, client.Admin, Region, and Store to not use HTableDescriptor or HColumnDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072247#comment-16072247
]
Hadoop QA commented on HBASE-18241:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
25s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 34 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
26s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
3s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 4m
8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
17s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
24s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 7m
38s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
12s{color} | {color:red} hbase-examples in master has 2 extant Findbugs
warnings. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
31s{color} | {color:red} hbase-rest in master has 3 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
45s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
38s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 4m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 4m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
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}
76m 26s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 14m
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} hbase-client generated 0 new + 0 unchanged - 1 fixed
= 0 total (was 1) {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 1m
12s{color} | {color:red} hbase-server generated 2 new + 0 unchanged - 0 fixed =
2 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} hbase-examples in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
39s{color} | {color:green} hbase-rest in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
35s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}143m 23s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
15s{color} | {color:green} hbase-examples in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m
35s{color} | {color:green} hbase-rest in the patch passed. {color} |
|
[jira] [Updated] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18268: --- Fix Version/s: (was: 1.1.12) > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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 > > Attachments: HBASE-18268.branch-1.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18266) Eliminate the warnings from the spotbugs
[ https://issues.apache.org/jira/browse/HBASE-18266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18266: --- Fix Version/s: (was: 1.1.12) > 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 > > > 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-18268) Eliminate the findbugs warnings for hbase-client
[
https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072236#comment-16072236
]
Hadoop QA commented on HBASE-18268:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 15m
7s{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} 2m
59s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
23s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
24s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
38s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
11s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
19s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
30s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
16s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
24s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
20m 52s{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:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
18s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
23s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
19s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
10s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 49m 57s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.10.1 Server=1.10.1 Image:yetus/hbase:395d9a0 |
| JIRA Issue | HBASE-18268 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875469/HBASE-18268.branch-1.v0.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux f284e87a4a29 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul
24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-18083) Make large/small file clean thread number configurable in HFileCleaner
[
https://issues.apache.org/jira/browse/HBASE-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072227#comment-16072227
]
Hadoop QA commented on HBASE-18083:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
12s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
25s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
28m 9s{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
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
26s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}110m 56s{color}
| {color:red} hbase-server in the patch failed. {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}152m 41s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestMasterProcedureWalLease |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18083 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875464/HBASE-18083.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 7133aa63336b 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 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 / ba54af3 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7474/artifact/patchprocess/branch-findbugs-hbase-server-warnings.html
|
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/7474/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7474/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7474/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Make large/small file clean thread number configurable in HFileCleaner
>
[jira] [Updated] (HBASE-18298) RegionServerServices Interface cleanup for CP expose
[ https://issues.apache.org/jira/browse/HBASE-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-18298: --- Attachment: HBASE-18298.patch > RegionServerServices Interface cleanup for CP expose > > > Key: HBASE-18298 > URL: https://issues.apache.org/jira/browse/HBASE-18298 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0 > > Attachments: HBASE-18298.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18298) RegionServerServices Interface cleanup for CP expose
[ https://issues.apache.org/jira/browse/HBASE-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-18298: --- Status: Patch Available (was: Open) See what QA says. > RegionServerServices Interface cleanup for CP expose > > > Key: HBASE-18298 > URL: https://issues.apache.org/jira/browse/HBASE-18298 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0 > > Attachments: HBASE-18298.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18083) Make large/small file clean thread number configurable in HFileCleaner
[
https://issues.apache.org/jira/browse/HBASE-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072213#comment-16072213
]
Chia-Ping Tsai commented on HBASE-18083:
{code}
private boolean running;
private long deletedLargeFiles = 0L;
private long deletedSmallFiles = 0L;
{code}
Do we need to declare them as volatile or Atomic object? They may be used
concurrently.
{code}
List leftOverTasks = new ArrayList<>();
for (HFileDeleteTask task : largeFileQueue) {
leftOverTasks.add(task);
}
for (HFileDeleteTask task : smallFileQueue) {
leftOverTasks.add(task);
}
{code}
Would you please set the initial capacity for leftOverTasks? Is the addAll good
to go in?
If all configs used by HFileCleaner aren't changed, is HFileCleaner still reset
when onConfigurationChange is called?
> Make large/small file clean thread number configurable in HFileCleaner
> --
>
> Key: HBASE-18083
> URL: https://issues.apache.org/jira/browse/HBASE-18083
> Project: HBase
> Issue Type: Bug
>Reporter: Yu Li
>Assignee: Yu Li
> Fix For: 3.0.0
>
> Attachments: HBASE-18083.patch
>
>
> Currently we have only one thread for both large and small file cleaning, but
> when write pressure is huge we might need more cleaner threads, so we need to
> make the thread number configurable.
> We observed more than 1.8PB data in archive directory online due to business
> access rate change, and this proposal is one of the necessary changes
> required.
> Default value of the configurations would still be left to 1 to keep low
> pressure to NN for normal case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072176#comment-16072176 ] Chia-Ping Tsai commented on HBASE-18268: Oh...The default jdk for branch-1.2+ may be different sometimes in running QA. Let me fix all warnings in this jira. > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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-18268.branch-1.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18268: --- Attachment: HBASE-18268.branch-1.v0.patch > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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-18268.branch-1.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18268: --- Status: Patch Available (was: Open) > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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-18268.branch-1.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18268) Eliminate the findbugs warnings for hbase-client
[ https://issues.apache.org/jira/browse/HBASE-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18268: --- Status: Open (was: Patch Available) > Eliminate the findbugs warnings for hbase-client > > > Key: HBASE-18268 > URL: https://issues.apache.org/jira/browse/HBASE-18268 > Project: HBase > Issue Type: Sub-task > Components: Client >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-18268.branch-1.v0.patch, > HBASE-18268.branch-1.v0.patch, HBASE-18268.v0.patch, HBASE-18268.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16072157#comment-16072157 ] Chia-Ping Tsai commented on HBASE-18295: bq. we need the change because we are seeking to nextcol and if there is a chance we move to next row we will have similar issues. If the cell is INCLUDED, it will be flushed into the disk. The flusher doesn't skip the cell "visible" to the current scanners. > 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, 1.4.0, 1.3.2, 2.0.0-alpha-2 > > Attachments: HBASE-18295.branch-1.3.v0.patch, > HBASE-18295.branch-1.v0.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] > If we use the cell which won't be flushed into disk as the top cell to reopen > the scanners, the new top cell will change. If the new top cell is in > different row, the matcher will reset, and then matcher will accept the new > top cell... > The TestStore# testFlushBeforeCompletingScan reproduces the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16072143#comment-16072143
]
ramkrishna.s.vasudevan commented on HBASE-18295:
bq.It is hard to say that the we need the change to apply in all places.
I do feel atleast below
{code}
} else if (qcode == ScanQueryMatcher.MatchCode.INCLUDE_AND_SEEK_NEXT_COL) {
seekOrSkipToNextColumn(cell);
} else {
this.heap.next();
}
{code}
we need the change because we are seeking to nextcol and if there is a chance
we move to next row we will have similar issues. Else patch looks good to me.
> 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, 1.4.0, 1.3.2, 2.0.0-alpha-2
>
> Attachments: HBASE-18295.branch-1.3.v0.patch,
> HBASE-18295.branch-1.v0.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch
>
>
> From the [flaky
> dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html]
> If we use the cell which won't be flushed into disk as the top cell to reopen
> the scanners, the new top cell will change. If the new top cell is in
> different row, the matcher will reset, and then matcher will accept the new
> top cell...
> The TestStore# testFlushBeforeCompletingScan reproduces the bug.
--
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=16072140#comment-16072140 ] Guanghao Zhang commented on HBASE-18283: Attach a 003 patch. Rewrite the TestAynscTableAdminApi and TestAsyncRegionAdminApi with AsyncTable, AsyncAdmin and AsyncMetaTableAccessor. TestAsync*Admin* passed locally. Let's wait the hadoop QA result. > 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, HBASE-18283.master.003.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-18309) Support multi threads to clean oldWALs
[ https://issues.apache.org/jira/browse/HBASE-18309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072141#comment-16072141 ] Yu Li commented on HBASE-18309: --- Personally I think supplying a way to accelerate oldWAL clean speed is nice to have, even with HBASE-14247 implemented. Let's make it support online configuration change and set the default thread number to 1. > Support multi threads to clean oldWALs > -- > > Key: HBASE-18309 > URL: https://issues.apache.org/jira/browse/HBASE-18309 > Project: HBase > Issue Type: Improvement >Reporter: binlijin > > There is only one thread in LogCleaner to clean oldWALs and in our big > cluster we find this is not enough. The number of files under oldWALs reach > the max-directory-items limit of HDFS and cause region server crash, so we > use multi threads for LogCleaner and the crash not happened any more. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (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:all-tabpanel ] Guanghao Zhang updated HBASE-18283: --- Attachment: HBASE-18283.master.003.patch > 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, HBASE-18283.master.003.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] [Updated] (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:all-tabpanel ] Guanghao Zhang updated HBASE-18283: --- Attachment: (was: HBASE-18283.master.003.patch) > 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, HBASE-18283.master.003.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-18309) Support multi threads to clean oldWALs
[ https://issues.apache.org/jira/browse/HBASE-18309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072126#comment-16072126 ] binlijin commented on HBASE-18309: -- I find this is the same problem with HBASE-14247, but use different method to solve it, suggestions are welcomed > Support multi threads to clean oldWALs > -- > > Key: HBASE-18309 > URL: https://issues.apache.org/jira/browse/HBASE-18309 > Project: HBase > Issue Type: Improvement >Reporter: binlijin > > There is only one thread in LogCleaner to clean oldWALs and in our big > cluster we find this is not enough. The number of files under oldWALs reach > the max-directory-items limit of HDFS and cause region server crash, so we > use multi threads for LogCleaner and the crash not happened any more. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18309) Support multi threads to clean oldWALs
binlijin created HBASE-18309: Summary: Support multi threads to clean oldWALs Key: HBASE-18309 URL: https://issues.apache.org/jira/browse/HBASE-18309 Project: HBase Issue Type: Improvement Reporter: binlijin There is only one thread in LogCleaner to clean oldWALs and in our big cluster we find this is not enough. The number of files under oldWALs reach the max-directory-items limit of HDFS and cause region server crash, so we use multi threads for LogCleaner and the crash not happened any more. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16072118#comment-16072118
]
Hadoop QA commented on HBASE-18295:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
36s{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} 10m
45s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
37s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
59s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
41s{color} | {color:green} branch-1.3 passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 4m
15s{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
18s{color} | {color:green} branch-1.3 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
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
30s{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 7s{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:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}204m 2s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
31s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}270m 26s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestRegionReplicaFailover |
| | hadoop.hbase.regionserver.TestPerColumnFamilyFlush |
| | hadoop.hbase.client.TestAdmin2 |
| | hadoop.hbase.TestPartialResultsFromClientSide |
| | hadoop.hbase.regionserver.TestCorruptedRegionStoreFile |
| Timed out junit tests | org.apache.hadoop.hbase.util.TestHBaseFsck |
| | org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot |
| | org.apache.hadoop.hbase.snapshot.TestExportSnapshot |
| |
org.apache.hadoop.hbase.replication.regionserver.TestReplicationWALReaderManager
|
| | org.apache.hadoop.hbase.filter.TestFuzzyRowFilterEndToEnd |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:9ba21e3 |
| JIRA Issue | HBASE-18295 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875439/HBASE-18295.branch-1.3.v0.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux e27b5a718654 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 |
https://builds.apache.org/job/PreCommit-HBASE-Build/7466/artifact/patchprocess/branch-findbugs-hbase-server-warnings.html
|
|
[jira] [Updated] (HBASE-18241) Change client.Table, client.Admin, Region, and Store to not use HTableDescriptor or HColumnDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18241:
---
Component/s: Client
> Change client.Table, client.Admin, Region, and Store to not use
> HTableDescriptor or HColumnDescriptor
> -
>
> Key: HBASE-18241
> URL: https://issues.apache.org/jira/browse/HBASE-18241
> Project: HBase
> Issue Type: Task
> Components: Client
>Reporter: Biju Nair
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18241.v0.patch, HBASE-18241.v1.patch,
> HBASE-18241.v2.patch, HBASE-18241.v2.patch, HBASE-18241.v3.patch,
> HBASE-18241.v3.patch
>
>
> {{HTableDescriptor}} is deprecated and scheduled to be removed in 3.0. But
> [client.Table|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java#L69]
> and
> [client.Admin|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java#L198]
> method {{getTableDescriptor}} returns {{HTableDescriptor}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18241) Change client.Table, client.Admin, Region, and Store to not use HTableDescriptor or HColumnDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18241:
---
Release Note:
- : removed API
+ : new API
* : deprecated API
---
Region class
- HTableDescriptor getTableDesc()
+TableDescriptor getTableDescriptor()
Store class
- HColumnDescriptor getFamily()
+ ColumnFamilyDescriptor getColumnFamilyDescriptor()
Table class
* HTableDescriptor getTableDescriptor()
+ TableDescriptor getDescriptor()|
*Admin class*
* HTableDescriptor getTableDescriptor(TableName)
+ List listTableDescriptor(TableName)|
* HTableDescriptor[] getTableDescriptors(List)
* HTableDescriptor[] getTableDescriptorsByTableName(List)
+ List listTableDescriptors(List)
* HTableDescriptor[] listTables()
+ List listTableDescriptors()
* HTableDescriptor[] listTables(Pattern)
+ List listTableDescriptors(Pattern)
* HTableDescriptor[] listTables(String)
+ List listTableDescriptors(String)
* HTableDescriptor[] listTables(Pattern, boolean)
+ List listTableDescriptors(Pattern, boolean)
* HTableDescriptor[] listTables(String, boolean)
+ List listTableDescriptors(String, boolean)
* HTableDescriptor[] deleteTables(String)
* HTableDescriptor[] deleteTables(Pattern)
* HTableDescriptor[] enableTables(String)
* HTableDescriptor[] enableTables(Pattern)
* HTableDescriptor[] disableTables(String)
* HTableDescriptor[] disableTables(Pattern)
* void modifyTable(TableName, HTableDescriptor)
+ void modifyTable(TableDescriptor)
* void modifyTableAsync(TableName, HTableDescriptor)
+ void modifyTableAsync(TableDescriptor)
* HTableDescriptor[] listTableDescriptorsByNamespace(String)
+ List listTableDescriptorsByNamespace(byte[])
- void createTable(HTableDescriptor)
+ void createTable(TableDescriptor)
- void createTable(HTableDescriptor, byte[], byte[], int)
+ void createTable({color:red}TableDescriptor, byte[], byte[], int)
- void createTable(HTableDescriptor, byte[][])
+ void createTable(TableDescriptor, byte[][])
- Future createTableAsync(HTableDescriptor, byte[][])
+ Future createTableAsync(TableDescriptor, byte[][])
was:
*Region class*
||*Removed API*||*New API*||
|HTableDescriptor getTableDesc()|TableDescriptor getTableDescriptor()|
*Store class*
||*Removed API*||*New API*||
|HColumnDescriptor getFamily()|ColumnFamilyDescriptor
getColumnFamilyDescriptor()|
*Table class*
||*Deprecated API*||*New API*||
|HTableDescriptor getTableDescriptor()|TableDescriptor getDescriptor()|
*Admin class*
||*Deprecated API*||*New API*||
|HTableDescriptor getTableDescriptor(TableName)|List
listTableDescriptor(TableName)|
|HTableDescriptor[] getTableDescriptors(List)|N/A|
|HTableDescriptor[]
getTableDescriptorsByTableName(List)|List
listTableDescriptors(List)|
|HTableDescriptor[] listTables()|List listTableDescriptors()|
|HTableDescriptor[] listTables(Pattern)|List
listTableDescriptors(Pattern)|
|HTableDescriptor[] listTables(String)|List
listTableDescriptors(String)|
|HTableDescriptor[] listTables(Pattern, boolean)|List
listTableDescriptors(Pattern, boolean)|
|HTableDescriptor[] listTables(String, boolean)|List
listTableDescriptors(String, boolean)|
|HTableDescriptor[] deleteTables(String)|N/A|
|HTableDescriptor[] deleteTables(Pattern)|N/A|
|HTableDescriptor[] enableTables(String)|N/A|
|HTableDescriptor[] enableTables(Pattern)|N/A|
|HTableDescriptor[] disableTables(String)|N/A|
|HTableDescriptor[] disableTables(Pattern)|N/A|
|void modifyTable(TableName, HTableDescriptor)|void
modifyTable(TableDescriptor)|
|void modifyTableAsync(TableName, HTableDescriptor)|void
modifyTableAsync(TableDescriptor)|
|HTableDescriptor[]
listTableDescriptorsByNamespace(String)|List
listTableDescriptorsByNamespace(byte[])|
||*Removed API*||*New API*||
|void createTable({color:red}HTableDescriptor{color})|void
createTable({color:red}TableDescriptor{color})|
|void createTable({color:red}HTableDescriptor{color}, byte[], byte[], int)|void
createTable({color:red}TableDescriptor{color}, byte[], byte[], int)|
|void createTable({color:red}HTableDescriptor{color}, byte[][])|void
createTable({color:red}TableDescriptor{color}, byte[][])|
|Future createTableAsync({color:red}HTableDescriptor{color},
byte[][])|Future createTableAsync({color:red}TableDescriptor{color},
byte[][])|
> Change client.Table, client.Admin, Region, and Store to not use
> HTableDescriptor or HColumnDescriptor
> -
>
> Key: HBASE-18241
> URL: https://issues.apache.org/jira/browse/HBASE-18241
> Project: HBase
> Issue Type: Task
>Reporter: Biju Nair
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18241.v0.patch, HBASE-18241.v1.patch,
> HBASE-18241.v2.patch, HBASE-18241.v2.patch, HBASE-18241.v3.patch,
[jira] [Commented] (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:comment-tabpanel=16072102#comment-16072102
]
Hadoop QA commented on HBASE-16730:
---
| (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
27s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
42s{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} 4m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 4m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
53s{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
3s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
34m 31s{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} 2m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
45s{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}158m
42s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
40s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}226m 57s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-16730 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12875441/HBASE-16730.master.002%20%281%29.patch
|
| Optional Tests | asflicense javac javadoc unit xml compile |
| uname | Linux 62c33c19384a 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 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 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7467/testReport/ |
| modules | C: hbase-spark . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7467/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> 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:
[jira] [Commented] (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:comment-tabpanel=16072098#comment-16072098 ] Chia-Ping Tsai commented on HBASE-18295: bq. So should you make a similar change in all places where seekAsDireciton() is called? I feel the same way but I can't reproduce the bug for other places. It is hard to say that the we need the change to apply in all places. > 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, 1.4.0, 1.3.2, 2.0.0-alpha-2 > > Attachments: HBASE-18295.branch-1.3.v0.patch, > HBASE-18295.branch-1.v0.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] > If we use the cell which won't be flushed into disk as the top cell to reopen > the scanners, the new top cell will change. If the new top cell is in > different row, the matcher will reset, and then matcher will accept the new > top cell... > The TestStore# testFlushBeforeCompletingScan reproduces the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15062) IntegrationTestMTTR conditionally run some tests
[ https://issues.apache.org/jira/browse/HBASE-15062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072096#comment-16072096 ] Hudson commented on HBASE-15062: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3303 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3303/]) HBASE-15062 IntegrationTestMTTR conditionally run some tests. (stack: rev ba54af3318a3584cdf685e6be8b5f668aff8a492) * (edit) hbase-it/src/test/java/org/apache/hadoop/hbase/mttr/IntegrationTestMTTR.java > IntegrationTestMTTR conditionally run some tests > - > > Key: HBASE-15062 > URL: https://issues.apache.org/jira/browse/HBASE-15062 > Project: HBase > Issue Type: Improvement > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Samir Ahmic >Assignee: Samir Ahmic >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-15062-v0.patch, HBASE-15062-v1.patch, > HBASE-15062-v1.patch, HBASE-15062-v1.patch > > > On master branch master-rs collocation is on by default which cause that > following test in IntegrationTestMTTR is same test as restartMaster > - testKillRsHoldingMeta > I will add condition so that if we have system tables on master test above > will be skipped else we will run it -- This message was sent by Atlassian JIRA (v6.4.14#64029)
