[GitHub] [hbase] Apache-HBase commented on issue #251: HBASE-22114 Port HBASE-15560 (TinyLFU-based BlockCache) to branch-1
Apache-HBase commented on issue #251: HBASE-22114 Port HBASE-15560 (TinyLFU-based BlockCache) to branch-1 URL: https://github.com/apache/hbase/pull/251#issuecomment-529804377 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 31m 34s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :broken_heart: | hbaseanti | 0m 0s | The patch appears use Hadoop classification instead of HBase. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :green_heart: | test4tests | 0m 0s | The patch appears to include 2 new or modified test files. | ||| _ branch-1 Compile Tests _ | | :blue_heart: | mvndep | 6m 3s | Maven dependency ordering for branch | | :green_heart: | mvninstall | 3m 11s | branch-1 passed | | :green_heart: | compile | 1m 47s | branch-1 passed | | :green_heart: | checkstyle | 8m 41s | branch-1 passed | | :blue_heart: | refguide | 3m 19s | branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect. | | :broken_heart: | shadedjars | 0m 11s | branch has 10 errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 3m 48s | branch-1 passed | | :blue_heart: | spotbugs | 8m 59s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :blue_heart: | findbugs | 0m 18s | branch/hbase-resource-bundle no findbugs output file (findbugsXml.xml) | ||| _ Patch Compile Tests _ | | :blue_heart: | mvndep | 0m 22s | Maven dependency ordering for patch | | :green_heart: | mvninstall | 1m 56s | the patch passed | | :green_heart: | compile | 1m 55s | the patch passed | | :green_heart: | javac | 1m 54s | the patch passed | | :green_heart: | checkstyle | 0m 9s | The patch passed checkstyle in hbase-resource-bundle | | :green_heart: | checkstyle | 0m 26s | The patch passed checkstyle in hbase-common | | :green_heart: | checkstyle | 1m 48s | hbase-server: The patch generated 0 new + 83 unchanged - 11 fixed = 83 total (was 94) | | :broken_heart: | checkstyle | 0m 10s | hbase-tinylfu-blockcache: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0) | | :broken_heart: | checkstyle | 6m 1s | root: The patch generated 1 new + 92 unchanged - 11 fixed = 93 total (was 103) | | :green_heart: | checkstyle | 0m 26s | The patch passed checkstyle in hbase-it | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | xml | 0m 6s | The patch has no ill-formed XML file. | | :blue_heart: | refguide | 2m 59s | patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect. | | :broken_heart: | shadedjars | 0m 10s | patch has 10 errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 5m 5s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2. | | :green_heart: | javadoc | 3m 44s | the patch passed | | :blue_heart: | findbugs | 0m 9s | hbase-resource-bundle has no data from findbugs | ||| _ Other Tests _ | | :green_heart: | unit | 171m 14s | root in the patch passed. | | :green_heart: | asflicense | 1m 55s | The patch does not generate ASF License warnings. | | | | 287m 4s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-251/19/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/251 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml | | uname | Linux d2a6470c7541 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-251/out/precommit/personality/provided.sh | | git revision | branch-1 / 1c0ee31 | | Default Java | 1.8.0_222 | | refguide | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-251/19/artifact/out/branch-site/book.html | | shadedjars | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-251/19/artifact/out/branch-shadedjars.txt | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-251/19/artifact/out/diff-checkstyle-hbase-tinylfu-blockcache.txt | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-251/19/artifact/out/di
[jira] [Created] (HBASE-23005) Table UI showed exception message when table is disabled
Guanghao Zhang created HBASE-23005: -- Summary: Table UI showed exception message when table is disabled Key: HBASE-23005 URL: https://issues.apache.org/jira/browse/HBASE-23005 Project: HBase Issue Type: Bug Reporter: Guanghao Zhang -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-23005: --- Description: Compaction java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) Unknown > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.Se
[jira] [Commented] (HBASE-22676) Move all the code in hbase-rsgroup to hbase-server and remove hbase-rsgroup module
[
https://issues.apache.org/jira/browse/HBASE-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926390#comment-16926390
]
Hudson commented on HBASE-22676:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Move all the code in hbase-rsgroup to hbase-server and remove hbase-rsgroup
> module
> --
>
> Key: HBASE-22676
> URL: https://issues.apache.org/jira/browse/HBASE-22676
> Project: HBase
> Issue Type: Sub-task
> Components: build, pom, rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
> Let's do this first and then try to refactor it.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22664) Move protobuf stuff in hbase-rsgroup to hbase-protocol-shaded
[
https://issues.apache.org/jira/browse/HBASE-22664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926392#comment-16926392
]
Hudson commented on HBASE-22664:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Move protobuf stuff in hbase-rsgroup to hbase-protocol-shaded
> -
>
> Key: HBASE-22664
> URL: https://issues.apache.org/jira/browse/HBASE-22664
> Project: HBase
> Issue Type: Sub-task
> Components: Protobufs, Region Assignment, rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22809) Allow creating table in group when rs group contains no live servers
[
https://issues.apache.org/jira/browse/HBASE-22809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926388#comment-16926388
]
Hudson commented on HBASE-22809:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Allow creating table in group when rs group contains no live servers
>
>
> Key: HBASE-22809
> URL: https://issues.apache.org/jira/browse/HBASE-22809
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
> This is for API consistency. In general, a rs group could have no live
> servers if all the region servers are dead, and then the regions in side this
> group can not online.
> So it is a bit strange that we do not allow new regions here since they are
> just the same with the old regions...
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[
https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926391#comment-16926391
]
Hudson commented on HBASE-22662:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Move RSGroupInfoManager to hbase-server
> ---
>
> Key: HBASE-22662
> URL: https://issues.apache.org/jira/browse/HBASE-22662
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-22662.v0.patch, HBASE-22662.v1.patch
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[
https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926389#comment-16926389
]
Hudson commented on HBASE-22695:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Store the rsgroup of a table in table configuration
> ---
>
> Key: HBASE-22695
> URL: https://issues.apache.org/jira/browse/HBASE-22695
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22819) Automatically migrate the rs group config for table after HBASE-22695
[
https://issues.apache.org/jira/browse/HBASE-22819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926386#comment-16926386
]
Hudson commented on HBASE-22819:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Automatically migrate the rs group config for table after HBASE-22695
> -
>
> Key: HBASE-22819
> URL: https://issues.apache.org/jira/browse/HBASE-22819
> Project: HBase
> Issue Type: Sub-task
> Components: master, rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
> It used to be stored in the rsgroup table, so we need to migrate it to the
> new place.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22820) Do not need to persist default rs group now
[
https://issues.apache.org/jira/browse/HBASE-22820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926387#comment-16926387
]
Hudson commented on HBASE-22820:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Do not need to persist default rs group now
> ---
>
> Key: HBASE-22820
> URL: https://issues.apache.org/jira/browse/HBASE-22820
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Xiaolin Ha
>Priority: Major
> Fix For: HBASE-22514
>
>
> As now the rs group info for a table is stored in the table metadata, we only
> need to store the servers of a rs group to the rs group table, so we do not
> need to store the default rs group anymore. The servers in default group will
> be refreshed automatically.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22729) Start RSGroupInfoManager as default
[
https://issues.apache.org/jira/browse/HBASE-22729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926385#comment-16926385
]
Hudson commented on HBASE-22729:
Results for branch master
[build #1421 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1421/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1421//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Start RSGroupInfoManager as default
> ---
>
> Key: HBASE-22729
> URL: https://issues.apache.org/jira/browse/HBASE-22729
> Project: HBase
> Issue Type: Sub-task
> Components: master, rsgroup
>Reporter: Guanghao Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
> Start RSGroupInfoManager as default. If no rsgroup information, all
> RegionServers belong to default group.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926395#comment-16926395 ] Duo Zhang commented on HBASE-23005: --- The line separators are missed in the description... > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase] sunhelly opened a new pull request #601: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin
sunhelly opened a new pull request #601: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin URL: https://github.com/apache/hbase/pull/601 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase] sunhelly closed pull request #588: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin
sunhelly closed pull request #588: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin URL: https://github.com/apache/hbase/pull/588 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926399#comment-16926399 ] Guanghao Zhang commented on HBASE-23005: Checked HBASE-17561. So we plan to show stacktrace here if there are exception? Ping [~busbey] > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926403#comment-16926403 ] Guanghao Zhang commented on HBASE-23005: bq. The line separators are missed in the description... Copied from the UI. The stacktrace didn't have line separators. > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase] Apache-HBase commented on issue #581: HBASE-22888 Use separate classe to deal with streaming read and pread
Apache-HBase commented on issue #581: HBASE-22888 Use separate classe to deal with streaming read and pread URL: https://github.com/apache/hbase/pull/581#issuecomment-529823384 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 0m 33s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :green_heart: | test4tests | 0m 0s | The patch appears to include 4 new or modified test files. | ||| _ master Compile Tests _ | | :green_heart: | mvninstall | 5m 22s | master passed | | :green_heart: | compile | 0m 55s | master passed | | :green_heart: | checkstyle | 1m 22s | master passed | | :green_heart: | shadedjars | 4m 30s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 0m 40s | master passed | | :blue_heart: | spotbugs | 4m 0s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :green_heart: | findbugs | 3m 58s | master passed | ||| _ Patch Compile Tests _ | | :green_heart: | mvninstall | 4m 51s | the patch passed | | :green_heart: | compile | 0m 55s | the patch passed | | :green_heart: | javac | 0m 55s | the patch passed | | :green_heart: | checkstyle | 1m 21s | hbase-server: The patch generated 0 new + 139 unchanged - 3 fixed = 139 total (was 142) | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | shadedjars | 4m 29s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 15m 33s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :broken_heart: | javadoc | 0m 35s | hbase-server generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0) | | :green_heart: | findbugs | 4m 13s | the patch passed | ||| _ Other Tests _ | | :green_heart: | unit | 157m 7s | hbase-server in the patch passed. | | :green_heart: | asflicense | 0m 36s | The patch does not generate ASF License warnings. | | | | 213m 31s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-581/3/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/581 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux b8f7484fb10f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-581/out/precommit/personality/provided.sh | | git revision | master / 4ca760fe9d | | Default Java | 1.8.0_181 | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-581/3/artifact/out/diff-javadoc-javadoc-hbase-server.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-581/3/testReport/ | | Max. process+thread count | 4673 (vs. ulimit of 1) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-581/3/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-22796) [HBCK2] Add fix of overlaps to fixMeta hbck Service
[
https://issues.apache.org/jira/browse/HBASE-22796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926408#comment-16926408
]
Sakthi commented on HBASE-22796:
+1 from me Stack.
Just a minor nit - There is a duplicate assertion in testIsOverlap:
{code:java}
@Test
public void testIsOverlap() {
assertTrue(MetaFixer.isOverlap(_BRI, new Pair(ABRI,
ACRI)));
assertFalse(MetaFixer.isOverlap(_ARI, new Pair(C_RI,
D_RI)));
assertTrue(MetaFixer.isOverlap(ADRI, new Pair(CDRI,
C_RI)));
assertFalse(MetaFixer.isOverlap(_BRI, new Pair(CDRI,
C_RI)));
assertFalse(MetaFixer.isOverlap(_BRI, new Pair(CDRI,
C_RI))); // -> Duplicate
} {code}
> [HBCK2] Add fix of overlaps to fixMeta hbck Service
> ---
>
> Key: HBASE-22796
> URL: https://issues.apache.org/jira/browse/HBASE-22796
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: Sakthi
>Priority: Major
> Attachments: HBASE-22796.master.001.patch,
> HBASE-22796.master.002.patch, HBASE-22796.master.003.patch,
> HBASE-22796.master.004.patch, HBASE-22796.master.005.patch
>
>
> fixMeta currently does holes in meta only courtesy of HBASE-22771 which added
> fixMeta to hbck Service; missing was fix of overlaps too. This JIRA is about
> adding fix of overlaps to general fixMeta call.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926410#comment-16926410 ] Duo Zhang commented on HBASE-23005: --- So why there are exceptions? > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926417#comment-16926417 ] Guanghao Zhang commented on HBASE-23005: Because table was disabled, it get CompactionState by admin call. This will failed when table is disabled. > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase] infraio opened a new pull request #602: HBASE-23005 Table UI showed exception message when table is disabled
infraio opened a new pull request #602: HBASE-23005 Table UI showed exception message when table is disabled URL: https://github.com/apache/hbase/pull/602 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926422#comment-16926422 ] Duo Zhang commented on HBASE-23005: --- We should change the code to not getCompactionState when table is disabled? And does this effect other branches? > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926432#comment-16926432 ] Guanghao Zhang commented on HBASE-23005: Yes. All active branchs have this problem. > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926437#comment-16926437 ] Duo Zhang commented on HBASE-23005: --- Then I do not think this is a release blocker? Can fix it in the next release... > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase] Apache-HBase commented on issue #599: HBASE-22987 Calculate the region servers in default group in foreground
Apache-HBase commented on issue #599: HBASE-22987 Calculate the region servers in default group in foreground URL: https://github.com/apache/hbase/pull/599#issuecomment-529840218 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 1m 15s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :yellow_heart: | test4tests | 0m 0s | 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. | ||| _ HBASE-22514 Compile Tests _ | | :green_heart: | mvninstall | 6m 15s | HBASE-22514 passed | | :green_heart: | compile | 0m 59s | HBASE-22514 passed | | :green_heart: | checkstyle | 1m 30s | HBASE-22514 passed | | :green_heart: | shadedjars | 5m 8s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 0m 38s | HBASE-22514 passed | | :blue_heart: | spotbugs | 4m 59s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :green_heart: | findbugs | 4m 57s | HBASE-22514 passed | ||| _ Patch Compile Tests _ | | :green_heart: | mvninstall | 5m 29s | the patch passed | | :green_heart: | compile | 1m 0s | the patch passed | | :green_heart: | javac | 1m 0s | the patch passed | | :green_heart: | checkstyle | 1m 30s | the patch passed | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | shadedjars | 5m 6s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 17m 51s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | javadoc | 0m 34s | the patch passed | | :green_heart: | findbugs | 5m 18s | the patch passed | ||| _ Other Tests _ | | :broken_heart: | unit | 253m 39s | hbase-server in the patch failed. | | :green_heart: | asflicense | 0m 41s | The patch does not generate ASF License warnings. | | | | 318m 53s | | | Reason | Tests | |---:|:--| | Failed junit tests | hadoop.hbase.quotas.TestQuotaAdmin | | | hadoop.hbase.filter.TestFuzzyRowFilterEndToEnd | | | hadoop.hbase.filter.TestFilterWithScanLimits | | | hadoop.hbase.filter.TestMultiRowRangeFilter | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-599/2/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/599 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux 35537d8d4812 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-599/out/precommit/personality/provided.sh | | git revision | HBASE-22514 / 728d9fe198 | | Default Java | 1.8.0_181 | | unit | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-599/2/artifact/out/patch-unit-hbase-server.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-599/2/testReport/ | | Max. process+thread count | 4458 (vs. ulimit of 1) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-599/2/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926444#comment-16926444 ] Guanghao Zhang commented on HBASE-23005: bq. Then I do not think this is a release blocker? Can fix it in the next release... Ok. And I checked HBASE-17561. It updated to show the stacktrace in the UI. > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-14413) Procedure V2 - Snapshot V2
[ https://issues.apache.org/jira/browse/HBASE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926453#comment-16926453 ] Nicholas Jiang commented on HBASE-14413: [~openinx]https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing,I have designed snapshot implementation based on Procedure V2 framework.Can you review this? > Procedure V2 - Snapshot V2 > -- > > Key: HBASE-14413 > URL: https://issues.apache.org/jira/browse/HBASE-14413 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Zheng Hu >Priority: Major > > We need new implementation of snapshot feature that is more robust and > performant. Ideally, it will work with multiple tables as well. The possible > areas of improvements: > # Must be flushless. Coordinated memstore flushes across a cluster are bad. > # Verification phase must be distributed, done in parallel and not on Master. > In theory, the only info we need to record snapshot of a table: list of WAL > files, list of HFiles and max sequence id of an edit which has been flushed > per Region. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (HBASE-14413) Procedure V2 - Snapshot V2
[ https://issues.apache.org/jira/browse/HBASE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Jiang updated HBASE-14413: --- Comment: was deleted (was: [~openinx]https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing,I have designed snapshot implementation based on Procedure V2 framework.Can you review this?) > Procedure V2 - Snapshot V2 > -- > > Key: HBASE-14413 > URL: https://issues.apache.org/jira/browse/HBASE-14413 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Zheng Hu >Priority: Major > > We need new implementation of snapshot feature that is more robust and > performant. Ideally, it will work with multiple tables as well. The possible > areas of improvements: > # Must be flushless. Coordinated memstore flushes across a cluster are bad. > # Verification phase must be distributed, done in parallel and not on Master. > In theory, the only info we need to record snapshot of a table: list of WAL > files, list of HFiles and max sequence id of an edit which has been flushed > per Region. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-14413) Procedure V2 - Snapshot V2
[ https://issues.apache.org/jira/browse/HBASE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926455#comment-16926455 ] Nicholas Jiang commented on HBASE-14413: [#https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing],I have designed snapshot implementation based on Procedure V2 framework.Can you review this? > Procedure V2 - Snapshot V2 > -- > > Key: HBASE-14413 > URL: https://issues.apache.org/jira/browse/HBASE-14413 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Zheng Hu >Priority: Major > > We need new implementation of snapshot feature that is more robust and > performant. Ideally, it will work with multiple tables as well. The possible > areas of improvements: > # Must be flushless. Coordinated memstore flushes across a cluster are bad. > # Verification phase must be distributed, done in parallel and not on Master. > In theory, the only info we need to record snapshot of a table: list of WAL > files, list of HFiles and max sequence id of an edit which has been flushed > per Region. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (HBASE-14413) Procedure V2 - Snapshot V2
[ https://issues.apache.org/jira/browse/HBASE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Jiang updated HBASE-14413: --- Comment: was deleted (was: [#https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing],I have designed snapshot implementation based on Procedure V2 framework.Can you review this?) > Procedure V2 - Snapshot V2 > -- > > Key: HBASE-14413 > URL: https://issues.apache.org/jira/browse/HBASE-14413 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Zheng Hu >Priority: Major > > We need new implementation of snapshot feature that is more robust and > performant. Ideally, it will work with multiple tables as well. The possible > areas of improvements: > # Must be flushless. Coordinated memstore flushes across a cluster are bad. > # Verification phase must be distributed, done in parallel and not on Master. > In theory, the only info we need to record snapshot of a table: list of WAL > files, list of HFiles and max sequence id of an edit which has been flushed > per Region. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (HBASE-14413) Procedure V2 - Snapshot V2
[ https://issues.apache.org/jira/browse/HBASE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Jiang updated HBASE-14413: --- Comment: was deleted (was: [Procedure V2 - Snapshot V2|https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing],I have already designed the snapshot implementation based on Procedure V2.Can you review this?) > Procedure V2 - Snapshot V2 > -- > > Key: HBASE-14413 > URL: https://issues.apache.org/jira/browse/HBASE-14413 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Zheng Hu >Priority: Major > > We need new implementation of snapshot feature that is more robust and > performant. Ideally, it will work with multiple tables as well. The possible > areas of improvements: > # Must be flushless. Coordinated memstore flushes across a cluster are bad. > # Verification phase must be distributed, done in parallel and not on Master. > In theory, the only info we need to record snapshot of a table: list of WAL > files, list of HFiles and max sequence id of an edit which has been flushed > per Region. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-14413) Procedure V2 - Snapshot V2
[ https://issues.apache.org/jira/browse/HBASE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926456#comment-16926456 ] Nicholas Jiang commented on HBASE-14413: [Procedure V2 - Snapshot V2|https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing],I have already designed the snapshot implementation based on Procedure V2.Can you review this? > Procedure V2 - Snapshot V2 > -- > > Key: HBASE-14413 > URL: https://issues.apache.org/jira/browse/HBASE-14413 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Zheng Hu >Priority: Major > > We need new implementation of snapshot feature that is more robust and > performant. Ideally, it will work with multiple tables as well. The possible > areas of improvements: > # Must be flushless. Coordinated memstore flushes across a cluster are bad. > # Verification phase must be distributed, done in parallel and not on Master. > In theory, the only info we need to record snapshot of a table: list of WAL > files, list of HFiles and max sequence id of an edit which has been flushed > per Region. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-14413) Procedure V2 - Snapshot V2
[ https://issues.apache.org/jira/browse/HBASE-14413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926457#comment-16926457 ] Nicholas Jiang commented on HBASE-14413: [~openinx][Procedure V2 - Snapshot V2|https://docs.google.com/document/d/1Gy6fJtf6IA3IB_EtQcGhjwVB3U8mCnVnHB3sYwKI5KU/edit?usp=sharing],I have already designed the snapshot implementation based on Procedure V2.Can you review this? > Procedure V2 - Snapshot V2 > -- > > Key: HBASE-14413 > URL: https://issues.apache.org/jira/browse/HBASE-14413 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Zheng Hu >Priority: Major > > We need new implementation of snapshot feature that is more robust and > performant. Ideally, it will work with multiple tables as well. The possible > areas of improvements: > # Must be flushless. Coordinated memstore flushes across a cluster are bad. > # Verification phase must be distributed, done in parallel and not on Master. > In theory, the only info we need to record snapshot of a table: list of WAL > files, list of HFiles and max sequence id of an edit which has been flushed > per Region. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23002) [HBCK2/hbase-operator-tools] Create an assembly that builds an hbase-operator-tools tgz
[ https://issues.apache.org/jira/browse/HBASE-23002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926472#comment-16926472 ] Peter Somogyi commented on HBASE-23002: --- I started to test you commit on the branch after rebasing to the current master. Few comments: * hbase-assembly/src/main/assembly/bin.xml needs license header otherwise it will fail on RAT check. * might be good to rename hbase-assembly to hbase-operator-assembly not to have naming conflict with the main hbase-assembly. HBase connectors use hbase-connectors-assembly artifactId. * In the generated tar.gz the hbase-hbck2-1.0.0-SNAPSHOT.jar is placed into hbase-hbck2/*lib*/hbase-hbck2-1.0.0-SNAPSHOT.jar. Shouldn't it be under hbase-hbck2/hbase-hbck2-1.0.0-SNAPSHOT.jar? * lib contains slf4j-api-1.7.25.jar which is under MIT license. This is a transitive dependency from log4j-slf4j-impl and I haven't noticed that we need to package it. I will fix this one. > [HBCK2/hbase-operator-tools] Create an assembly that builds an > hbase-operator-tools tgz > --- > > Key: HBASE-23002 > URL: https://issues.apache.org/jira/browse/HBASE-23002 > Project: HBase > Issue Type: Task >Reporter: stack >Priority: Major > > Was going to build a convenience binary tgz as part of the first release of > hbase-operator-tools. Not sure how just yet; best would be if it were a > fatjar with all dependencies but that'd be kinda insane at same time since > the tgz would be massive. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (HBASE-22969) A new binary component comparator(BinaryComponentComparator) to perform comparison of arbitrary length and position
[
https://issues.apache.org/jira/browse/HBASE-22969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reassigned HBASE-22969:
-
Assignee: Udai Bhan Kashyap
> A new binary component comparator(BinaryComponentComparator) to perform
> comparison of arbitrary length and position
> ---
>
> Key: HBASE-22969
> URL: https://issues.apache.org/jira/browse/HBASE-22969
> Project: HBase
> Issue Type: Improvement
> Components: Filters
>Reporter: Udai Bhan Kashyap
>Assignee: Udai Bhan Kashyap
>Priority: Minor
> Attachments: HBASE-22969.0003.patch, HBASE-22969.0004.patch,
> HBASE-22969.0005.patch, HBASE-22969.HBASE-22969.0001.patch,
> HBASE-22969.master.0001.patch
>
>
> Lets say you have composite key: a+b+c+d. And for simplicity assume that
> a,b,c, and d all are 4 byte integers.
> Now, if you want to execute a query which is semantically same to following
> sql:
> {{"SELECT * from table where a=1 and b > 10 and b < 20 and c > 90 and c < 100
> and d=1"}}
> The only choice you have is to do client side filtering. That could be lots
> of unwanted data going through various software components and network.
> Solution:
> We can create a "component" comparator which takes the value of the
> "component" and its relative position in the key to pass the 'Filter'
> subsystem of the server:
> {code}
> FilterList filterList = new FilterList(FilterList.Operator.MUST_PASS_ALL);
> int bOffset = 4;
> byte[] b10 = Bytes.toBytes(10);
> Filter b10Filter = new RowFilter(CompareFilter.CompareOp.GREATER,
> new BinaryComponentComparator(b10,bOffset));
> filterList.addFilter(b10Filter);
> byte[] b20 = Bytes.toBytes(20);
> Filter b20Filter = new RowFilter(CompareFilter.CompareOp.LESS,
> new BinaryComponentComparator(b20,bOffset));
> filterList.addFilter(b20Filter);
> int cOffset = 8;
> byte[] c90 = Bytes.toBytes(90);
> Filter c90Filter = new RowFilter(CompareFilter.CompareOp.GREATER,
> new BinaryComponentComparator(c90,cOffset));
> filterList.addFilter(c90Filter);
> byte[] c100 = Bytes.toBytes(100);
> Filter c100Filter = new RowFilter(CompareFilter.CompareOp.LESS,
> new BinaryComponentComparator(c100,cOffset));
> filterList.addFilter(c100Filter);
> in dOffset = 12;
> byte[] d1 = Bytes.toBytes(1);
> Filter dFilter = new RowFilter(CompareFilter.CompareOp.EQUAL,
> new BinaryComponentComparator(d1,dOffset));
> filterList.addFilter(dFilter);
> //build start and end key for scan
> int aOffset = 0;
> byte[] startKey = new byte[16]; //key size with four ints
> Bytes.putInt(startKey,aOffset,1); //a=1
> Bytes.putInt(startKey,bOffset,11); //b=11, takes care of b > 10
> Bytes.putInt(startKey,cOffset,91); //c=91,
> Bytes.putInt(startKey,dOffset,1); //d=1,
> byte[] endKey = new byte[16];
> Bytes.putInt(endKey,aOffset,1); //a=1
> Bytes.putInt(endKey,bOffset,20); //b=20, takes care of b < 20
> Bytes.putInt(endKey,cOffset,100); //c=100,
> Bytes.putInt(endKey,dOffset,1); //d=1,
> //setup scan
> Scan scan = new Scan(startKey,endKey);
> scan.setFilter(filterList);
> //The scanner below now should give only desired rows.
> //No client side filtering is required.
> ResultScanner scanner = table.getScanner(scan);
> {code}
> The comparator can be used with any filter which makes use of
> ByteArrayComparable. Most notably it can be used with ValueFilter to filter
> out KV based on partial comparison of 'values' :
> {code}
> byte[] partialValue = Bytes.toBytes("partial_value");
> int partialValueOffset =
> Filter partialValueFilter = new
> ValueFilter(CompareFilter.CompareOp.GREATER,
> new BinaryComponentComparator(partialValue,partialValueOffset));
> {code}
> Which in turn can be combined with RowFilter to create a poweful predicate:
> {code}
> RowFilter rowFilter = new RowFilter(GREATER, new
> BinaryComponentComparator(Bytes.toBytes("a"),1);
> FilterLiost fl = new FilterList
> (MUST_PASS_ALL,rowFilter,partialValueFilter);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase] chenxu14 opened a new pull request #603: HBASE-22965 RS Crash due to DBE reference to an reused ByteBuff
chenxu14 opened a new pull request #603: HBASE-22965 RS Crash due to DBE reference to an reused ByteBuff URL: https://github.com/apache/hbase/pull/603 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-22514) Move rsgroup feature into core of HBase
[
https://issues.apache.org/jira/browse/HBASE-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926504#comment-16926504
]
Hudson commented on HBASE-22514:
Results for branch HBASE-22514
[build #101 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/101/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/101//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/101//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/101//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Move rsgroup feature into core of HBase
> ---
>
> Key: HBASE-22514
> URL: https://issues.apache.org/jira/browse/HBASE-22514
> Project: HBase
> Issue Type: Umbrella
> Components: Admin, Client, rsgroup
>Reporter: Yechao Chen
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-22514.master.001.patch,
> image-2019-05-31-18-25-38-217.png
>
>
> The class RSGroupAdminClient is not public
> we need to use java api RSGroupAdminClient to manager RSG
> so RSGroupAdminClient should be public
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (HBASE-23006) RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers
Duo Zhang created HBASE-23006: - Summary: RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers Key: HBASE-23006 URL: https://issues.apache.org/jira/browse/HBASE-23006 Project: HBase Issue Type: Bug Components: Region Assignment, rsgroup Reporter: Duo Zhang Found this when implementing HBASE-22971. TestSCPWithReplicas fails when RSGroupBasedLoadBalancer is enabled. And this can be reproduced by a UT on master branch too. I think the problem is that in RSGroupBasedLoadBalancer.retainAssignment we do not consider region replicas. We should fix this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (HBASE-23006) RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers
[ https://issues.apache.org/jira/browse/HBASE-23006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-23006: -- Assignee: Duo Zhang Status: Patch Available (was: Open) > RSGroupBasedLoadBalancer should also try to place replicas for the same > region to different region servers > -- > > Key: HBASE-23006 > URL: https://issues.apache.org/jira/browse/HBASE-23006 > Project: HBase > Issue Type: Bug > Components: Region Assignment, rsgroup >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Attachments: HBASE-23006-UT.patch > > > Found this when implementing HBASE-22971. TestSCPWithReplicas fails when > RSGroupBasedLoadBalancer is enabled. > And this can be reproduced by a UT on master branch too. I think the problem > is that in RSGroupBasedLoadBalancer.retainAssignment we do not consider > region replicas. > We should fix this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (HBASE-23006) RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers
[ https://issues.apache.org/jira/browse/HBASE-23006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-23006: -- Attachment: HBASE-23006-UT.patch > RSGroupBasedLoadBalancer should also try to place replicas for the same > region to different region servers > -- > > Key: HBASE-23006 > URL: https://issues.apache.org/jira/browse/HBASE-23006 > Project: HBase > Issue Type: Bug > Components: Region Assignment, rsgroup >Reporter: Duo Zhang >Priority: Major > Attachments: HBASE-23006-UT.patch > > > Found this when implementing HBASE-22971. TestSCPWithReplicas fails when > RSGroupBasedLoadBalancer is enabled. > And this can be reproduced by a UT on master branch too. I think the problem > is that in RSGroupBasedLoadBalancer.retainAssignment we do not consider > region replicas. > We should fix this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23006) RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers
[ https://issues.apache.org/jira/browse/HBASE-23006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926505#comment-16926505 ] Duo Zhang commented on HBASE-23006: --- Let's see if the newly introduced UT fails. > RSGroupBasedLoadBalancer should also try to place replicas for the same > region to different region servers > -- > > Key: HBASE-23006 > URL: https://issues.apache.org/jira/browse/HBASE-23006 > Project: HBase > Issue Type: Bug > Components: Region Assignment, rsgroup >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Attachments: HBASE-23006-UT.patch > > > Found this when implementing HBASE-22971. TestSCPWithReplicas fails when > RSGroupBasedLoadBalancer is enabled. > And this can be reproduced by a UT on master branch too. I think the problem > is that in RSGroupBasedLoadBalancer.retainAssignment we do not consider > region replicas. > We should fix this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Reopened] (HBASE-22997) Move to SLF4J
[
https://issues.apache.org/jira/browse/HBASE-22997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi reopened HBASE-22997:
---
log4j-slf4j-impl adds transitive dependency to slf4j-api which has MIT license.
License file needs to contain this MIT license text.
> Move to SLF4J
> -
>
> Key: HBASE-22997
> URL: https://issues.apache.org/jira/browse/HBASE-22997
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools
>Affects Versions: operator-1.0.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
> Fix For: operator-1.0.0
>
>
> Currently hbase-operator-tools uses org.apache.logging.log4j while the rest
> of our projects have SLF4J.
> When building the project with release profile the enforce plugin fails on
> org.apache.logging.log4j:log4j-api:jar:2.11.1 dependency
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4:enforce
> (min-maven-min-java-banned-xerces) @ hbase-hbck2 ---
> [INFO] Restricted to JDK 1.8 yet
> org.apache.logging.log4j:log4j-api:jar:2.11.1:compile contains
> META-INF/versions/9/module-info.class targeted to JDK 1.9
> [WARNING] Rule 3: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion
> failed with message:
> HBase has unsupported dependencies.
> HBase requires that all dependencies be compiled with version 1.8 or earlier
> of the JDK to properly build from source. You appear to be using a newer
> dependency. You can use
> either "mvn -version" or "mvn enforcer:display-info" to verify what version
> is active.
> Non-release builds can temporarily build with a newer JDK version by
> setting the
> 'compileSource' property (eg. mvn -DcompileSource=1.8 clean package).
> Found Banned Dependency: org.apache.logging.log4j:log4j-api:jar:2.11.1
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22514) Move rsgroup feature into core of HBase
[
https://issues.apache.org/jira/browse/HBASE-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926520#comment-16926520
]
Hudson commented on HBASE-22514:
Results for branch HBASE-22514
[build #100 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/100/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/100//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/100//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/100//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Move rsgroup feature into core of HBase
> ---
>
> Key: HBASE-22514
> URL: https://issues.apache.org/jira/browse/HBASE-22514
> Project: HBase
> Issue Type: Umbrella
> Components: Admin, Client, rsgroup
>Reporter: Yechao Chen
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-22514.master.001.patch,
> image-2019-05-31-18-25-38-217.png
>
>
> The class RSGroupAdminClient is not public
> we need to use java api RSGroupAdminClient to manager RSG
> so RSGroupAdminClient should be public
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase-operator-tools] petersomogyi opened a new pull request #28: HBASE-22997 Move to SLF4J; addendum
petersomogyi opened a new pull request #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28 Add MIT to LICENSE.txt This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase-operator-tools] asf-ci commented on issue #28: HBASE-22997 Move to SLF4J; addendum
asf-ci commented on issue #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28#issuecomment-529888198 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/PreCommit-HBASE-OPERATOR-TOOLS-Build/96/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (HBASE-23007) UnsatisfiedLinkError when using hbase-shaded packages under linux
Balazs Meszaros created HBASE-23007:
---
Summary: UnsatisfiedLinkError when using hbase-shaded packages
under linux
Key: HBASE-23007
URL: https://issues.apache.org/jira/browse/HBASE-23007
Project: HBase
Issue Type: Bug
Components: shading
Affects Versions: 3.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros
If we use hbase-shaded-* packages under linux, we get the following exception:
{noformat}
2019-08-26 16:36:10,413 ERROR [Time-limited test] regionserver.HRegionServer
(HRegionServer.java:(662)) - Failed construction RegionServer
java.lang.UnsatisfiedLinkError: failed to load the required native library
at
org.apache.hbase.thirdparty.io.netty.channel.epoll.Epoll.ensureAvailability(Epoll.java:79)
…
Caused by: java.lang.UnsatisfiedLinkError: could not load a native library:
org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64
at
org.apache.hbase.thirdparty.io.netty.util.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:224)
{noformat}
{{liborg_apache_hbase_thirdparty_netty_transport_native_epoll_x86_64.so}} is in
the shaded jar files, but
{{org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64.so}}
is not.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase] shardul-cr7 commented on issue #598: HBASE-22142 Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
shardul-cr7 commented on issue #598: HBASE-22142 Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table. URL: https://github.com/apache/hbase/pull/598#issuecomment-529895114 Hi @joshelser , can you review this one ?.. I was planning to work on HBASE-20821 after this one gets merged. Thanks again. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-22956) [HBCK2/hbase-operator-tools] Make first release, 1.0.0
[
https://issues.apache.org/jira/browse/HBASE-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926539#comment-16926539
]
Peter Somogyi commented on HBASE-22956:
---
{quote}We need a 1.0 branch
{quote}
Why do we need a different branch? I think we can have a tag (rel/1.0.0) for
the release and continue the development on master and release the second
operator-tools release from there. We want to keep backward compatibility with
HBase2 releases so until we don't introduce something that could break
compatibility with earlier HBase 2 releases I don't feel the need to have
multiple branches.
> [HBCK2/hbase-operator-tools] Make first release, 1.0.0
> --
>
> Key: HBASE-22956
> URL: https://issues.apache.org/jira/browse/HBASE-22956
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
>Reporter: stack
>Priority: Major
> Fix For: hbase-operator-tools-1.0.0
>
>
> Make our first release of hbck2/hbase-operator-tools.
> First release should have the coverage hbck1 had at least. When the parent
> for this issue is done, we'll be at hbck1+. Let us release then (week or
> two?).
> A release will help operators who have been struggling having to build hbck2
> against different hbase versions. The release should be a "fat
> jar"/completely contained with all dependency satisfied so operator can just
> fire up hbck2 w/o having to build against an hbase or provide some magic mix
> of jars to satisfy hbck2 tool needs.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Work started] (HBASE-23007) UnsatisfiedLinkError when using hbase-shaded packages under linux
[
https://issues.apache.org/jira/browse/HBASE-23007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-23007 started by Balazs Meszaros.
---
> UnsatisfiedLinkError when using hbase-shaded packages under linux
> -
>
> Key: HBASE-23007
> URL: https://issues.apache.org/jira/browse/HBASE-23007
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 3.0.0
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
>
> If we use hbase-shaded-* packages under linux, we get the following exception:
> {noformat}
> 2019-08-26 16:36:10,413 ERROR [Time-limited test] regionserver.HRegionServer
> (HRegionServer.java:(662)) - Failed construction RegionServer
> java.lang.UnsatisfiedLinkError: failed to load the required native library
> at
> org.apache.hbase.thirdparty.io.netty.channel.epoll.Epoll.ensureAvailability(Epoll.java:79)
> …
> Caused by: java.lang.UnsatisfiedLinkError: could not load a native library:
> org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64
> at
> org.apache.hbase.thirdparty.io.netty.util.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:224)
> {noformat}
> {{liborg_apache_hbase_thirdparty_netty_transport_native_epoll_x86_64.so}} is
> in the shaded jar files, but
> {{org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64.so}}
> is not.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-23006) RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers
[
https://issues.apache.org/jira/browse/HBASE-23006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926548#comment-16926548
]
HBase QA commented on HBASE-23006:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
29s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {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:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
55s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
17s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 0m
45s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
44s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
52s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
16m 52s{color} | {color:green} Patch does not cause any errors with Hadoop
2.8.5 2.9.2 or 3.1.2. {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} findbugs {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 4m 43s{color}
| {color:red} hbase-rsgroup in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 52m 41s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestSCPWithReplicasWithRSGroup |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.1 Server=19.03.1 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/890/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-23006 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12979952/HBASE-23006-UT.patch |
| Optional Tests | dupname asflicense javac javadoc unit shadedjars hadoopcheck
xml compile spotbugs findbugs hbaseanti checkstyle |
| uname | Linux 7ab8e3dfefeb 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22
16:55:30 UTC 2019 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/hbase-personality.sh |
| git revision | master / 4ca
[jira] [Created] (HBASE-23008) ReplicationSourceShipper has no chance to delete hlog znode when the wal entry batch always empty
Zheng Wang created HBASE-23008:
--
Summary: ReplicationSourceShipper has no chance to delete hlog
znode when the wal entry batch always empty
Key: HBASE-23008
URL: https://issues.apache.org/jira/browse/HBASE-23008
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 2.0.0
Reporter: Zheng Wang
My live cluster config master-master replication,and only one is used to put
data,as active cluster.
Recently ,i find there are a great many znode in
/hbase/replication/rs/#host/#peer in backup cluster,at least 1+.
I think the reason is , the wal entry in backup cluster are filtered by
ClusterMarkingEntryFilter totaly, so ReplicationSourceWALReader will not put
any data to entryBatchQueue,and ReplicationSourceShipper always blocked at
entryReader.take(),it has no chance to delete hlog znode.
The thread stack of walReader and walShiper is below:
{code:java}
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition
[0x7f6114c0e000]"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition [0x7f6114c0e000] java.lang.Thread.State: TIMED_WAITING
(sleeping) at java.lang.Thread.sleep(Native Method) at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.handleEmptyWALEntryBatch(ReplicationSourceWALReader.java:192)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.run(ReplicationSourceWALReader.java:142)
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157237 daemon prio=5 os_prio=0 tid=0x7f76350b nid=0x377ee waiting on
condition [0x7f6108173000] java.lang.Thread.State: WAITING (parking) at
sun.misc.Unsafe.park(Native Method) - parking to wait for <0x7f6f99bb6718>
(a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.take(ReplicationSourceWALReader.java:248)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.run(ReplicationSourceShipper.java:108)
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (HBASE-23008) ReplicationSourceShipper has no chance to delete hlog znode when the wal entry batch always empty
[
https://issues.apache.org/jira/browse/HBASE-23008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zheng Wang updated HBASE-23008:
---
Description:
My live cluster config master-master replication,and only one is used to put
data,as active cluster.
Recently ,i find there are a great many znode in
/hbase/replication/rs/#server/#peer in backup cluster,at least 1+.
I think the reason is , the wal entry in backup cluster are filtered by
ClusterMarkingEntryFilter totaly, so ReplicationSourceWALReader will not put
any data to entryBatchQueue,and ReplicationSourceShipper always blocked at
entryReader.take(),it has no chance to delete hlog znode.
The thread stack of walReader and walShiper is below:
{code:java}
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition
[0x7f6114c0e000]"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition [0x7f6114c0e000] java.lang.Thread.State: TIMED_WAITING
(sleeping) at java.lang.Thread.sleep(Native Method) at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.handleEmptyWALEntryBatch(ReplicationSourceWALReader.java:192)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.run(ReplicationSourceWALReader.java:142)
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157237 daemon prio=5 os_prio=0 tid=0x7f76350b nid=0x377ee waiting on
condition [0x7f6108173000] java.lang.Thread.State: WAITING (parking) at
sun.misc.Unsafe.park(Native Method) - parking to wait for <0x7f6f99bb6718>
(a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.take(ReplicationSourceWALReader.java:248)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.run(ReplicationSourceShipper.java:108)
{code}
was:
My live cluster config master-master replication,and only one is used to put
data,as active cluster.
Recently ,i find there are a great many znode in
/hbase/replication/rs/#host/#peer in backup cluster,at least 1+.
I think the reason is , the wal entry in backup cluster are filtered by
ClusterMarkingEntryFilter totaly, so ReplicationSourceWALReader will not put
any data to entryBatchQueue,and ReplicationSourceShipper always blocked at
entryReader.take(),it has no chance to delete hlog znode.
The thread stack of walReader and walShiper is below:
{code:java}
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition
[0x7f6114c0e000]"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition [0x7f6114c0e000] java.lang.Thread.State: TIMED_WAITING
(sleeping) at java.lang.Thread.sleep(Native Method) at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.handleEmptyWALEntryBatch(ReplicationSourceWALReader.java:192)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.run(ReplicationSourceWALReader.java:142)
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157237 daemon prio=5 os_prio=0 tid=0x7f76350b nid=0x377ee waiting on
condition [0x7f6108173000] java.lang.Thread.State: WAITING (parking) at
sun.misc.Unsafe.park(Native Method) -
[jira] [Updated] (HBASE-23008) ReplicationSourceShipper has no chance to delete hlog znode when the wal entry batch always empty
[
https://issues.apache.org/jira/browse/HBASE-23008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zheng Wang updated HBASE-23008:
---
Description:
My live cluster config master-master replication,and only one is used to put
data,as active cluster.
Recently ,i find there are a great many znode in
/hbase/replication/rs/#server/#peer in backup cluster,at least 1+.
I think the reason is , the wal entry in backup cluster are filtered by
ClusterMarkingEntryFilter totaly, so ReplicationSourceWALReader will not put
any data to entryBatchQueue,and ReplicationSourceShipper always blocked at
entryReader.take(),it has no chance to delete hlog znode.
The thread stack of walReader and walShiper is below:
{code:java}
"main-EventThread.replicationSource,2.replicationSource.hostname%2C16020%2C1567586932902.hostname%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.hostname%2C16020%2C1567586932902.hostname%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition
[0x7f6114c0e000]"main-EventThread.replicationSource,2.replicationSource.hostname%2C16020%2C1567586932902.hostname%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.hostname%2C16020%2C1567586932902.hostname%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition [0x7f6114c0e000] java.lang.Thread.State: TIMED_WAITING
(sleeping) at java.lang.Thread.sleep(Native Method) at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.handleEmptyWALEntryBatch(ReplicationSourceWALReader.java:192)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.run(ReplicationSourceWALReader.java:142)
"main-EventThread.replicationSource,2.replicationSource.hostname%2C16020%2C1567586932902.hostname%2C16020%2C1567586932902.regiongroup-0,2"
#157237 daemon prio=5 os_prio=0 tid=0x7f76350b nid=0x377ee waiting on
condition [0x7f6108173000] java.lang.Thread.State: WAITING (parking) at
sun.misc.Unsafe.park(Native Method) - parking to wait for <0x7f6f99bb6718>
(a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.take(ReplicationSourceWALReader.java:248)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.run(ReplicationSourceShipper.java:108)
{code}
was:
My live cluster config master-master replication,and only one is used to put
data,as active cluster.
Recently ,i find there are a great many znode in
/hbase/replication/rs/#server/#peer in backup cluster,at least 1+.
I think the reason is , the wal entry in backup cluster are filtered by
ClusterMarkingEntryFilter totaly, so ReplicationSourceWALReader will not put
any data to entryBatchQueue,and ReplicationSourceShipper always blocked at
entryReader.take(),it has no chance to delete hlog znode.
The thread stack of walReader and walShiper is below:
{code:java}
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition
[0x7f6114c0e000]"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2.replicationSource.wal-reader.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157238 daemon prio=5 os_prio=0 tid=0x7f7634be8800 nid=0x377ef waiting on
condition [0x7f6114c0e000] java.lang.Thread.State: TIMED_WAITING
(sleeping) at java.lang.Thread.sleep(Native Method) at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.handleEmptyWALEntryBatch(ReplicationSourceWALReader.java:192)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceWALReader.run(ReplicationSourceWALReader.java:142)
"main-EventThread.replicationSource,2.replicationSource.bj1-203-centos17%2C16020%2C1567586932902.bj1-203-centos17%2C16020%2C1567586932902.regiongroup-0,2"
#157237 daemon prio=5 os_prio=0 tid=0x7f76350b nid=0x377ee waiting on
condition [0x7f6108173000] java.lang.Thread.State: WAITING (parking) at
sun.misc.Unsafe.park(Native Method) - parking to wait for <0x7f6f99bb6718>
(a java.util.concurrent.locks.Abs
[jira] [Commented] (HBASE-22809) Allow creating table in group when rs group contains no live servers
[
https://issues.apache.org/jira/browse/HBASE-22809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926568#comment-16926568
]
Hudson commented on HBASE-22809:
Results for branch master
[build #1420 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1420/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Allow creating table in group when rs group contains no live servers
>
>
> Key: HBASE-22809
> URL: https://issues.apache.org/jira/browse/HBASE-22809
> Project: HBase
> Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
> This is for API consistency. In general, a rs group could have no live
> servers if all the region servers are dead, and then the regions in side this
> group can not online.
> So it is a bit strange that we do not allow new regions here since they are
> just the same with the old regions...
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22664) Move protobuf stuff in hbase-rsgroup to hbase-protocol-shaded
[
https://issues.apache.org/jira/browse/HBASE-22664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926564#comment-16926564
]
Hudson commented on HBASE-22664:
Results for branch master
[build #1420 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1420/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Move protobuf stuff in hbase-rsgroup to hbase-protocol-shaded
> -
>
> Key: HBASE-22664
> URL: https://issues.apache.org/jira/browse/HBASE-22664
> Project: HBase
> Issue Type: Sub-task
> Components: Protobufs, Region Assignment, rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22695) Store the rsgroup of a table in table configuration
[
https://issues.apache.org/jira/browse/HBASE-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926567#comment-16926567
]
Hudson commented on HBASE-22695:
Results for branch master
[build #1420 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1420/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Store the rsgroup of a table in table configuration
> ---
>
> Key: HBASE-22695
> URL: https://issues.apache.org/jira/browse/HBASE-22695
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[
https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926565#comment-16926565
]
Hudson commented on HBASE-22662:
Results for branch master
[build #1420 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1420/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Move RSGroupInfoManager to hbase-server
> ---
>
> Key: HBASE-22662
> URL: https://issues.apache.org/jira/browse/HBASE-22662
> Project: HBase
> Issue Type: Sub-task
> Components: rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-22662.v0.patch, HBASE-22662.v1.patch
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22676) Move all the code in hbase-rsgroup to hbase-server and remove hbase-rsgroup module
[
https://issues.apache.org/jira/browse/HBASE-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926566#comment-16926566
]
Hudson commented on HBASE-22676:
Results for branch master
[build #1420 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1420/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1420//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Move all the code in hbase-rsgroup to hbase-server and remove hbase-rsgroup
> module
> --
>
> Key: HBASE-22676
> URL: https://issues.apache.org/jira/browse/HBASE-22676
> Project: HBase
> Issue Type: Sub-task
> Components: build, pom, rsgroup
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-22514
>
>
> Let's do this first and then try to refactor it.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase] meszibalu opened a new pull request #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux
meszibalu opened a new pull request #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux URL: https://github.com/apache/hbase/pull/604 * Relocation rule "net" has been changed to "net." because "netty" applies to that rule. * Added jackson dependencies for WebHdfs. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase] Apache-HBase commented on issue #601: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin
Apache-HBase commented on issue #601: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin URL: https://github.com/apache/hbase/pull/601#issuecomment-529906225 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 0m 35s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 1s | No case conflicting files found. | | :blue_heart: | prototool | 0m 0s | prototool was not available. | | :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :green_heart: | test4tests | 0m 0s | The patch appears to include 3 new or modified test files. | ||| _ HBASE-22514 Compile Tests _ | | :blue_heart: | mvndep | 0m 36s | Maven dependency ordering for branch | | :green_heart: | mvninstall | 6m 10s | HBASE-22514 passed | | :green_heart: | compile | 2m 59s | HBASE-22514 passed | | :green_heart: | checkstyle | 3m 0s | HBASE-22514 passed | | :green_heart: | shadedjars | 4m 40s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 1m 46s | HBASE-22514 passed | | :blue_heart: | spotbugs | 1m 30s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :green_heart: | findbugs | 9m 31s | HBASE-22514 passed | ||| _ Patch Compile Tests _ | | :blue_heart: | mvndep | 0m 16s | Maven dependency ordering for patch | | :green_heart: | mvninstall | 5m 16s | the patch passed | | :green_heart: | compile | 2m 37s | the patch passed | | :green_heart: | cc | 2m 37s | the patch passed | | :green_heart: | javac | 2m 37s | the patch passed | | :broken_heart: | checkstyle | 0m 34s | hbase-client: The patch generated 19 new + 162 unchanged - 0 fixed = 181 total (was 162) | | :broken_heart: | checkstyle | 1m 18s | hbase-server: The patch generated 31 new + 111 unchanged - 0 fixed = 142 total (was 111) | | :broken_heart: | whitespace | 0m 0s | The patch has 2 line(s) that end in whitespace. Use git apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply | | :green_heart: | shadedjars | 4m 50s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 16m 1s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | hbaseprotoc | 2m 30s | the patch passed | | :broken_heart: | javadoc | 0m 35s | hbase-server generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0) | | :green_heart: | findbugs | 10m 47s | the patch passed | ||| _ Other Tests _ | | :green_heart: | unit | 0m 41s | hbase-protocol-shaded in the patch passed. | | :green_heart: | unit | 1m 50s | hbase-client in the patch passed. | | :broken_heart: | unit | 155m 22s | hbase-server in the patch failed. | | :green_heart: | unit | 3m 43s | hbase-thrift in the patch passed. | | :green_heart: | asflicense | 2m 8s | The patch does not generate ASF License warnings. | | | | 247m 28s | | | Reason | Tests | |---:|:--| | Failed junit tests | hadoop.hbase.rsgroup.TestMigrateRSGroupInfo | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/1/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/601 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool | | uname | Linux 0be50a693434 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-601/out/precommit/personality/provided.sh | | git revision | HBASE-22514 / 728d9fe198 | | Default Java | 1.8.0_181 | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/1/artifact/out/diff-checkstyle-hbase-client.txt | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/1/artifact/out/diff-checkstyle-hbase-server.txt | | whitespace | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/1/artifact/out/whitespace-eol.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/1/artifact/out/diff-javadoc-javadoc-hbase-server.txt | | unit | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/1/artifact/out/patch-unit-hbase-server.txt | | Test Results | https://builds.apache.
[jira] [Updated] (HBASE-23007) UnsatisfiedLinkError when using hbase-shaded packages under linux
[
https://issues.apache.org/jira/browse/HBASE-23007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balazs Meszaros updated HBASE-23007:
Status: Patch Available (was: In Progress)
> UnsatisfiedLinkError when using hbase-shaded packages under linux
> -
>
> Key: HBASE-23007
> URL: https://issues.apache.org/jira/browse/HBASE-23007
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 3.0.0
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
>
> If we use hbase-shaded-* packages under linux, we get the following exception:
> {noformat}
> 2019-08-26 16:36:10,413 ERROR [Time-limited test] regionserver.HRegionServer
> (HRegionServer.java:(662)) - Failed construction RegionServer
> java.lang.UnsatisfiedLinkError: failed to load the required native library
> at
> org.apache.hbase.thirdparty.io.netty.channel.epoll.Epoll.ensureAvailability(Epoll.java:79)
> …
> Caused by: java.lang.UnsatisfiedLinkError: could not load a native library:
> org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64
> at
> org.apache.hbase.thirdparty.io.netty.util.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:224)
> {noformat}
> {{liborg_apache_hbase_thirdparty_netty_transport_native_epoll_x86_64.so}} is
> in the shaded jar files, but
> {{org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64.so}}
> is not.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22514) Move rsgroup feature into core of HBase
[
https://issues.apache.org/jira/browse/HBASE-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926582#comment-16926582
]
Hudson commented on HBASE-22514:
Results for branch HBASE-22514
[build #102 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/102/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/102//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/102//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/102//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-22514/102//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Move rsgroup feature into core of HBase
> ---
>
> Key: HBASE-22514
> URL: https://issues.apache.org/jira/browse/HBASE-22514
> Project: HBase
> Issue Type: Umbrella
> Components: Admin, Client, rsgroup
>Reporter: Yechao Chen
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-22514.master.001.patch,
> image-2019-05-31-18-25-38-217.png
>
>
> The class RSGroupAdminClient is not public
> we need to use java api RSGroupAdminClient to manager RSG
> so RSGroupAdminClient should be public
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase] Apache9 opened a new pull request #605: HBASE-23006 RSGroupBasedLoadBalancer should also try to place replica…
Apache9 opened a new pull request #605: HBASE-23006 RSGroupBasedLoadBalancer should also try to place replica… URL: https://github.com/apache/hbase/pull/605 …s for the same region to different region servers This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase] Apache-HBase commented on issue #602: HBASE-23005 Table UI showed exception message when table is disabled
Apache-HBase commented on issue #602: HBASE-23005 Table UI showed exception message when table is disabled URL: https://github.com/apache/hbase/pull/602#issuecomment-529926180 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 1m 16s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :yellow_heart: | test4tests | 0m 0s | 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. | ||| _ branch-2.2 Compile Tests _ | | :green_heart: | mvninstall | 5m 34s | branch-2.2 passed | | :green_heart: | javadoc | 0m 38s | branch-2.2 passed | ||| _ Patch Compile Tests _ | | :green_heart: | mvninstall | 6m 22s | the patch passed | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | javadoc | 0m 42s | the patch passed | ||| _ Other Tests _ | | :broken_heart: | unit | 256m 50s | hbase-server in the patch failed. | | :green_heart: | asflicense | 0m 36s | The patch does not generate ASF License warnings. | | | | 273m 15s | | | Reason | Tests | |---:|:--| | Failed junit tests | hadoop.hbase.client.TestReplicaWithCluster | | | hadoop.hbase.TestMetaTableAccessor | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.0 Server=19.03.0 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-602/1/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/602 | | Optional Tests | dupname asflicense javac javadoc unit | | uname | Linux 8e5f0d0deb0e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-602/out/precommit/personality/provided.sh | | git revision | branch-2.2 / b5366c7fdd | | Default Java | 1.8.0_181 | | unit | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-602/1/artifact/out/patch-unit-hbase-server.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-602/1/testReport/ | | Max. process+thread count | 4779 (vs. ulimit of 1) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-602/1/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (HBASE-23009) TestSnapshotScannerHDFSAclController is broken on branch-2
Peter Somogyi created HBASE-23009:
-
Summary: TestSnapshotScannerHDFSAclController is broken on branch-2
Key: HBASE-23009
URL: https://issues.apache.org/jira/browse/HBASE-23009
Project: HBase
Issue Type: Bug
Components: snapshots
Affects Versions: 2.3.0
Reporter: Peter Somogyi
Fix For: 2.3.0
TestSnapshotScannerHDFSAclController.testCleanArchiveTableDir always fails on
branch-2.
{noformat}
java.lang.AssertionError at
org.apache.hadoop.hbase.security.access.TestSnapshotScannerHDFSAclController.testCleanArchiveTableDir(TestSnapshotScannerHDFSAclController.java:745)
{noformat}
Test run:
[https://builds.apache.org/job/HBase-Flaky-Tests/job/branch-2/4148/testReport/junit/org.apache.hadoop.hbase.security.access/TestSnapshotScannerHDFSAclController/testCleanArchiveTableDir/]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase] Apache-HBase commented on issue #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux
Apache-HBase commented on issue #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux URL: https://github.com/apache/hbase/pull/604#issuecomment-529933984 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 2m 36s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :yellow_heart: | test4tests | 0m 0s | 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. | ||| _ master Compile Tests _ | | :blue_heart: | mvndep | 0m 47s | Maven dependency ordering for branch | | :green_heart: | mvninstall | 7m 18s | master passed | | :green_heart: | compile | 1m 14s | master passed | | :green_heart: | shadedjars | 5m 56s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 0m 35s | master passed | ||| _ Patch Compile Tests _ | | :blue_heart: | mvndep | 0m 17s | Maven dependency ordering for patch | | :green_heart: | mvninstall | 6m 34s | the patch passed | | :green_heart: | compile | 1m 11s | the patch passed | | :green_heart: | javac | 1m 11s | the patch passed | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | xml | 0m 4s | The patch has no ill-formed XML file. | | :green_heart: | shadedjars | 6m 9s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 21m 47s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | javadoc | 0m 33s | the patch passed | ||| _ Other Tests _ | | :green_heart: | unit | 1m 23s | hbase-shaded in the patch passed. | | :green_heart: | unit | 0m 26s | hbase-shaded-testing-util in the patch passed. | | :green_heart: | asflicense | 0m 29s | The patch does not generate ASF License warnings. | | | | 65m 59s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-604/1/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/604 | | Optional Tests | dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile | | uname | Linux d15655f0fe21 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-604/out/precommit/personality/provided.sh | | git revision | master / 4ca760fe9d | | Default Java | 1.8.0_181 | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-604/1/testReport/ | | Max. process+thread count | 413 (vs. ulimit of 1) | | modules | C: hbase-shaded hbase-shaded/hbase-shaded-testing-util U: hbase-shaded | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-604/1/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase] busbey commented on a change in pull request #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux
busbey commented on a change in pull request #604: HBASE-23007
UnsatisfiedLinkError when using hbase-shaded packages under linux
URL: https://github.com/apache/hbase/pull/604#discussion_r322741442
##
File path: hbase-shaded/pom.xml
##
@@ -441,8 +441,8 @@
-net
-
${shaded.prefix}.net
+net.
Review comment:
I think this should be "net/" instead of "net." and then the shade plugin
will look for both because it takes the slash to mean like a package delimiter.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [hbase] Apache-HBase commented on issue #595: HBASE-22971 Deprecated RSGroupAdminEndpoint and make RSGroup feature …
Apache-HBase commented on issue #595: HBASE-22971 Deprecated RSGroupAdminEndpoint and make RSGroup feature … URL: https://github.com/apache/hbase/pull/595#issuecomment-529939284 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 0m 35s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :green_heart: | test4tests | 0m 0s | The patch appears to include 8 new or modified test files. | ||| _ HBASE-22514 Compile Tests _ | | :green_heart: | mvninstall | 5m 42s | HBASE-22514 passed | | :green_heart: | compile | 0m 57s | HBASE-22514 passed | | :green_heart: | checkstyle | 1m 26s | HBASE-22514 passed | | :green_heart: | shadedjars | 4m 44s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 0m 39s | HBASE-22514 passed | | :blue_heart: | spotbugs | 4m 24s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :green_heart: | findbugs | 4m 22s | HBASE-22514 passed | ||| _ Patch Compile Tests _ | | :green_heart: | mvninstall | 5m 7s | the patch passed | | :green_heart: | compile | 0m 59s | the patch passed | | :green_heart: | javac | 0m 59s | the patch passed | | :green_heart: | checkstyle | 1m 24s | hbase-server: The patch generated 0 new + 174 unchanged - 2 fixed = 174 total (was 176) | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | shadedjars | 5m 38s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 19m 56s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | javadoc | 0m 43s | the patch passed | | :green_heart: | findbugs | 5m 9s | the patch passed | ||| _ Other Tests _ | | :broken_heart: | unit | 167m 47s | hbase-server in the patch failed. | | :green_heart: | asflicense | 0m 34s | The patch does not generate ASF License warnings. | | | | 233m 34s | | | Reason | Tests | |---:|:--| | Failed junit tests | hadoop.hbase.master.TestMasterFailoverBalancerPersistence | | | hadoop.hbase.regionserver.TestRegionServerReportForDuty | | | hadoop.hbase.master.procedure.TestSCPWithoutMetaWithReplicasWithoutZKCoordinated | | | hadoop.hbase.master.procedure.TestSCPWithMetaWithReplicas | | | hadoop.hbase.regionserver.TestRegionOpen | | | hadoop.hbase.master.TestMasterRestartAfterDisablingTable | | | hadoop.hbase.master.procedure.TestSCPWithReplicas | | | hadoop.hbase.master.procedure.TestSCPWithMetaWithReplicasWithoutZKCoordinated | | | hadoop.hbase.master.procedure.TestSCPWithReplicasWithoutZKCoordinated | | | hadoop.hbase.master.procedure.TestSCPWithoutMetaWithReplicas | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-595/3/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/595 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux 7525a95727b7 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-595/out/precommit/personality/provided.sh | | git revision | HBASE-22514 / 728d9fe198 | | Default Java | 1.8.0_181 | | unit | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-595/3/artifact/out/patch-unit-hbase-server.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-595/3/testReport/ | | Max. process+thread count | 4092 (vs. ulimit of 1) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-595/3/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With
[GitHub] [hbase] Apache-HBase commented on issue #605: HBASE-23006 RSGroupBasedLoadBalancer should also try to place replica…
Apache-HBase commented on issue #605: HBASE-23006 RSGroupBasedLoadBalancer should also try to place replica… URL: https://github.com/apache/hbase/pull/605#issuecomment-529942677 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 1m 8s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :green_heart: | test4tests | 0m 0s | The patch appears to include 2 new or modified test files. | ||| _ master Compile Tests _ | | :green_heart: | mvninstall | 5m 33s | master passed | | :green_heart: | compile | 0m 26s | master passed | | :green_heart: | checkstyle | 0m 16s | master passed | | :green_heart: | shadedjars | 4m 32s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 0m 24s | master passed | | :blue_heart: | spotbugs | 0m 47s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :green_heart: | findbugs | 0m 46s | master passed | ||| _ Patch Compile Tests _ | | :green_heart: | mvninstall | 5m 1s | the patch passed | | :green_heart: | compile | 0m 26s | the patch passed | | :green_heart: | javac | 0m 26s | the patch passed | | :green_heart: | checkstyle | 0m 15s | the patch passed | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | xml | 0m 1s | The patch has no ill-formed XML file. | | :green_heart: | shadedjars | 4m 33s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 15m 28s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | javadoc | 0m 22s | the patch passed | | :green_heart: | findbugs | 0m 53s | the patch passed | ||| _ Other Tests _ | | :green_heart: | unit | 9m 20s | hbase-rsgroup in the patch passed. | | :green_heart: | asflicense | 0m 13s | The patch does not generate ASF License warnings. | | | | 55m 58s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-605/1/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/605 | | Optional Tests | dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile spotbugs findbugs hbaseanti checkstyle | | uname | Linux 4077ea2cad8f 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-605/out/precommit/personality/provided.sh | | git revision | master / 4ca760fe9d | | Default Java | 1.8.0_181 | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-605/1/testReport/ | | Max. process+thread count | 4667 (vs. ulimit of 1) | | modules | C: hbase-rsgroup U: hbase-rsgroup | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-605/1/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-23006) RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers
[ https://issues.apache.org/jira/browse/HBASE-23006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926672#comment-16926672 ] Duo Zhang commented on HBASE-23006: --- The fix is simple, just removed lots of code in RSGroupBasedLoadBalancer... Not sure why we introduce lots of code to deal with misplaced regions specially in retainAssignment, just give the internal load balancer the correct candidate list, if the region is misplaced, it will be place to new places... > RSGroupBasedLoadBalancer should also try to place replicas for the same > region to different region servers > -- > > Key: HBASE-23006 > URL: https://issues.apache.org/jira/browse/HBASE-23006 > Project: HBase > Issue Type: Bug > Components: Region Assignment, rsgroup >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Attachments: HBASE-23006-UT.patch > > > Found this when implementing HBASE-22971. TestSCPWithReplicas fails when > RSGroupBasedLoadBalancer is enabled. > And this can be reproduced by a UT on master branch too. I think the problem > is that in RSGroupBasedLoadBalancer.retainAssignment we do not consider > region replicas. > We should fix this. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase-operator-tools] petersomogyi commented on issue #28: HBASE-22997 Move to SLF4J; addendum
petersomogyi commented on issue #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28#issuecomment-529952807 > this should be in the LICENSE file for artifacts we generate that include a copy of slf4j. We don't have it in our source repository, so it should not be in this top level LICENSE. Does it mean we need to add the MIT license when generating the tarball? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase] Apache-HBase commented on issue #603: HBASE-22965 RS Crash due to DBE reference to an reused ByteBuff
Apache-HBase commented on issue #603: HBASE-22965 RS Crash due to DBE reference to an reused ByteBuff URL: https://github.com/apache/hbase/pull/603#issuecomment-529953096 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 0m 40s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :green_heart: | test4tests | 0m 0s | The patch appears to include 1 new or modified test files. | ||| _ master Compile Tests _ | | :blue_heart: | mvndep | 0m 35s | Maven dependency ordering for branch | | :green_heart: | mvninstall | 5m 11s | master passed | | :green_heart: | compile | 1m 19s | master passed | | :green_heart: | checkstyle | 1m 45s | master passed | | :green_heart: | shadedjars | 4m 35s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 0m 58s | master passed | | :blue_heart: | spotbugs | 4m 0s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :green_heart: | findbugs | 4m 48s | master passed | ||| _ Patch Compile Tests _ | | :blue_heart: | mvndep | 0m 15s | Maven dependency ordering for patch | | :green_heart: | mvninstall | 4m 53s | the patch passed | | :green_heart: | compile | 1m 20s | the patch passed | | :green_heart: | javac | 1m 20s | the patch passed | | :broken_heart: | checkstyle | 0m 26s | hbase-common: The patch generated 2 new + 1 unchanged - 0 fixed = 3 total (was 1) | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | shadedjars | 4m 32s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 15m 31s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | javadoc | 0m 55s | the patch passed | | :green_heart: | findbugs | 4m 59s | the patch passed | ||| _ Other Tests _ | | :green_heart: | unit | 3m 5s | hbase-common in the patch passed. | | :broken_heart: | unit | 159m 50s | hbase-server in the patch failed. | | :green_heart: | asflicense | 0m 56s | The patch does not generate ASF License warnings. | | | | 224m 25s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-603/1/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/603 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux c0134af57db9 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-603/out/precommit/personality/provided.sh | | git revision | master / 4ca760fe9d | | Default Java | 1.8.0_181 | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-603/1/artifact/out/diff-checkstyle-hbase-common.txt | | unit | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-603/1/artifact/out/patch-unit-hbase-server.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-603/1/testReport/ | | Max. process+thread count | 4860 (vs. ulimit of 1) | | modules | C: hbase-common hbase-server U: . | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-603/1/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase-operator-tools] busbey commented on issue #28: HBASE-22997 Move to SLF4J; addendum
busbey commented on issue #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28#issuecomment-529955209 Yes, when we make a binary tarball that includes our dependencies we'll need to include it in that LICENSE. Do we need to bundle slf4j though? won't it always be available from the hbase instance we're running against? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-21879) Read HFile's block to ByteBuffer directly instead of to byte for reducing young gc purpose
[
https://issues.apache.org/jira/browse/HBASE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926704#comment-16926704
]
Hudson commented on HBASE-21879:
Results for branch HBASE-21879
[build #236 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-21879/236/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-21879/236//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-21879/236//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-21879/236//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Read HFile's block to ByteBuffer directly instead of to byte for reducing
> young gc purpose
> --
>
> Key: HBASE-21879
> URL: https://issues.apache.org/jira/browse/HBASE-21879
> Project: HBase
> Issue Type: Improvement
>Reporter: Zheng Hu
>Assignee: Zheng Hu
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HBASE-21879.v1.patch, HBASE-21879.v1.patch,
> QPS-latencies-before-HBASE-21879.png, gc-data-before-HBASE-21879.png
>
>
> In HFileBlock#readBlockDataInternal, we have the following:
> {code}
> @VisibleForTesting
> protected HFileBlock readBlockDataInternal(FSDataInputStream is, long offset,
> long onDiskSizeWithHeaderL, boolean pread, boolean verifyChecksum,
> boolean updateMetrics)
> throws IOException {
> // .
> // TODO: Make this ByteBuffer-based. Will make it easier to go to HDFS with
> BBPool (offheap).
> byte [] onDiskBlock = new byte[onDiskSizeWithHeader + hdrSize];
> int nextBlockOnDiskSize = readAtOffset(is, onDiskBlock, preReadHeaderSize,
> onDiskSizeWithHeader - preReadHeaderSize, true, offset +
> preReadHeaderSize, pread);
> if (headerBuf != null) {
> // ...
> }
> // ...
> }
> {code}
> In the read path, we still read the block from hfile to on-heap byte[], then
> copy the on-heap byte[] to offheap bucket cache asynchronously, and in my
> 100% get performance test, I also observed some frequent young gc, The
> largest memory footprint in the young gen should be the on-heap block byte[].
> In fact, we can read HFile's block to ByteBuffer directly instead of to
> byte[] for reducing young gc purpose. we did not implement this before,
> because no ByteBuffer reading interface in the older HDFS client, but 2.7+
> has supported this now, so we can fix this now. I think.
> Will provide an patch and some perf-comparison for this.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22956) [HBCK2/hbase-operator-tools] Make first release, 1.0.0
[ https://issues.apache.org/jira/browse/HBASE-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926710#comment-16926710 ] stack commented on HBASE-22956: --- bq. I think we can have a tag (rel/1.0.0) for the release and continue the development on master and release the second operator-tools release from there. Was concerned we'd need to do a 1.1 or 1.0.1 but we'd polluted master branch w/ some new feature not fully-baked But lets try your suggestion. It would be easier all around if we could work that way. > [HBCK2/hbase-operator-tools] Make first release, 1.0.0 > -- > > Key: HBASE-22956 > URL: https://issues.apache.org/jira/browse/HBASE-22956 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Reporter: stack >Priority: Major > Fix For: hbase-operator-tools-1.0.0 > > > Make our first release of hbck2/hbase-operator-tools. > First release should have the coverage hbck1 had at least. When the parent > for this issue is done, we'll be at hbck1+. Let us release then (week or > two?). > A release will help operators who have been struggling having to build hbck2 > against different hbase versions. The release should be a "fat > jar"/completely contained with all dependency satisfied so operator can just > fire up hbck2 w/o having to build against an hbase or provide some magic mix > of jars to satisfy hbck2 tool needs. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase-operator-tools] wchevreuil merged pull request #27: HBASE-22999 Fix non-varargs compile warnings
wchevreuil merged pull request #27: HBASE-22999 Fix non-varargs compile warnings URL: https://github.com/apache/hbase-operator-tools/pull/27 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-23005) Table UI showed exception message when table is disabled
[ https://issues.apache.org/jira/browse/HBASE-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926713#comment-16926713 ] Sean Busbey commented on HBASE-23005: - > Checked HBASE-17561. So we plan to show stacktrace here if there are > exception? Ping Sean Busbey AFAIK HBASE-17561 just maintained the existing behavior but changed it to safely print the stacktrace instead of allowing it to inject arbitrary html. > Table UI showed exception message when table is disabled > > > Key: HBASE-23005 > URL: https://issues.apache.org/jira/browse/HBASE-23005 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Priority: Minor > > Compaction > java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:299)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) > Unknown -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase-operator-tools] petersomogyi commented on issue #28: HBASE-22997 Move to SLF4J; addendum
petersomogyi commented on issue #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28#issuecomment-529976416 > Do we need to bundle slf4j though? won't it always be available from the hbase instance we're running against? slf4j-api-1.7.25.jar (the one that we currently include in the hbck2 tarball) is available in the hbase releases. I just checked 2.2.1RC and these files are there: ``` $ find . -name *slf4j* ./lib/client-facing-thirdparty/slf4j-api-1.7.25.jar ./lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar ``` Based on this I think we can just exclude the slf4j-api when generating the tar.gz file. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (HBASE-22999) Fix non-varargs compile warnings
[
https://issues.apache.org/jira/browse/HBASE-22999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-22999.
--
Resolution: Fixed
> Fix non-varargs compile warnings
>
>
> Key: HBASE-22999
> URL: https://issues.apache.org/jira/browse/HBASE-22999
> Project: HBase
> Issue Type: Improvement
> Components: hbase-operator-tools
>Affects Versions: operator-1.0.0
>Reporter: Peter Somogyi
>Assignee: Wellington Chevreuil
>Priority: Minor
> Labels: beginner
> Fix For: operator-1.0.0
>
>
> In hbase-hbck2 submodule there are a few compile warnings with "non-varargs
> call of varargs method with inexact argument type for last parameter".
> Warnings can be removed by casting null value.
> {noformat}
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestHBCK2.java:[206,46]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to java.lang.String for a varargs call
> cast to java.lang.String[] for a non-varargs call and to suppress this
> warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestHBCK2.java:[313,43]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to java.lang.String for a varargs call
> cast to java.lang.String[] for a non-varargs call and to suppress this
> warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestFsRegionsMetaRecoverer.java:[117,53]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to org.apache.hadoop.hbase.client.Result for a varargs call
> cast to org.apache.hadoop.hbase.client.Result[] for a non-varargs call and
> to suppress this warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestFsRegionsMetaRecoverer.java:[132,53]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to org.apache.hadoop.hbase.client.Result for a varargs call
> cast to org.apache.hadoop.hbase.client.Result[] for a non-varargs call and
> to suppress this warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestFsRegionsMetaRecoverer.java:[162,53]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to org.apache.hadoop.hbase.client.Result for a varargs call
> cast to org.apache.hadoop.hbase.client.Result[] for a non-varargs call and
> to suppress this warning
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (HBASE-22999) Fix non-varargs compile warnings
[
https://issues.apache.org/jira/browse/HBASE-22999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil updated HBASE-22999:
-
Fix Version/s: operator-1.0.0
> Fix non-varargs compile warnings
>
>
> Key: HBASE-22999
> URL: https://issues.apache.org/jira/browse/HBASE-22999
> Project: HBase
> Issue Type: Improvement
> Components: hbase-operator-tools
>Affects Versions: operator-1.0.0
>Reporter: Peter Somogyi
>Assignee: Wellington Chevreuil
>Priority: Minor
> Labels: beginner
> Fix For: operator-1.0.0
>
>
> In hbase-hbck2 submodule there are a few compile warnings with "non-varargs
> call of varargs method with inexact argument type for last parameter".
> Warnings can be removed by casting null value.
> {noformat}
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestHBCK2.java:[206,46]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to java.lang.String for a varargs call
> cast to java.lang.String[] for a non-varargs call and to suppress this
> warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestHBCK2.java:[313,43]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to java.lang.String for a varargs call
> cast to java.lang.String[] for a non-varargs call and to suppress this
> warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestFsRegionsMetaRecoverer.java:[117,53]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to org.apache.hadoop.hbase.client.Result for a varargs call
> cast to org.apache.hadoop.hbase.client.Result[] for a non-varargs call and
> to suppress this warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestFsRegionsMetaRecoverer.java:[132,53]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to org.apache.hadoop.hbase.client.Result for a varargs call
> cast to org.apache.hadoop.hbase.client.Result[] for a non-varargs call and
> to suppress this warning
> [WARNING]
> /Users/peter.somogyi/Cloudera/repos/hbase-operator-tools/hbase-hbck2/src/test/java/org/apache/hbase/TestFsRegionsMetaRecoverer.java:[162,53]
> non-varargs call of varargs method with inexact argument type for last
> parameter;
> cast to org.apache.hadoop.hbase.client.Result for a varargs call
> cast to org.apache.hadoop.hbase.client.Result[] for a non-varargs call and
> to suppress this warning
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22956) [HBCK2/hbase-operator-tools] Make first release, 1.0.0
[ https://issues.apache.org/jira/browse/HBASE-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926714#comment-16926714 ] Peter Somogyi commented on HBASE-22956: --- We can always create a branch from the release tag when we actually need it. > [HBCK2/hbase-operator-tools] Make first release, 1.0.0 > -- > > Key: HBASE-22956 > URL: https://issues.apache.org/jira/browse/HBASE-22956 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Reporter: stack >Priority: Major > Fix For: hbase-operator-tools-1.0.0 > > > Make our first release of hbck2/hbase-operator-tools. > First release should have the coverage hbck1 had at least. When the parent > for this issue is done, we'll be at hbck1+. Let us release then (week or > two?). > A release will help operators who have been struggling having to build hbck2 > against different hbase versions. The release should be a "fat > jar"/completely contained with all dependency satisfied so operator can just > fire up hbck2 w/o having to build against an hbase or provide some magic mix > of jars to satisfy hbck2 tool needs. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase-operator-tools] busbey commented on issue #28: HBASE-22997 Move to SLF4J; addendum
busbey commented on issue #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28#issuecomment-529985743 👍 I love shipping fewer bits 😸 I assume it'll be there for whatever HBase versions we want to use operator-tools with. The location might change, but since we're always run via the `hbase` command we should get a classpath that includes it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase-operator-tools] petersomogyi closed pull request #28: HBASE-22997 Move to SLF4J; addendum
petersomogyi closed pull request #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [hbase-operator-tools] petersomogyi commented on issue #28: HBASE-22997 Move to SLF4J; addendum
petersomogyi commented on issue #28: HBASE-22997 Move to SLF4J; addendum URL: https://github.com/apache/hbase-operator-tools/pull/28#issuecomment-529989717 Based on the above I'm closing this pull request. The exclusion should happen when we introduce the assembly module. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (HBASE-22997) Move to SLF4J
[
https://issues.apache.org/jira/browse/HBASE-22997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi resolved HBASE-22997.
---
Resolution: Fixed
We should just exclude slf4j-api jar from the binary tarball so we don't need
to include the MIT license.
> Move to SLF4J
> -
>
> Key: HBASE-22997
> URL: https://issues.apache.org/jira/browse/HBASE-22997
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools
>Affects Versions: operator-1.0.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
> Fix For: operator-1.0.0
>
>
> Currently hbase-operator-tools uses org.apache.logging.log4j while the rest
> of our projects have SLF4J.
> When building the project with release profile the enforce plugin fails on
> org.apache.logging.log4j:log4j-api:jar:2.11.1 dependency
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4:enforce
> (min-maven-min-java-banned-xerces) @ hbase-hbck2 ---
> [INFO] Restricted to JDK 1.8 yet
> org.apache.logging.log4j:log4j-api:jar:2.11.1:compile contains
> META-INF/versions/9/module-info.class targeted to JDK 1.9
> [WARNING] Rule 3: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion
> failed with message:
> HBase has unsupported dependencies.
> HBase requires that all dependencies be compiled with version 1.8 or earlier
> of the JDK to properly build from source. You appear to be using a newer
> dependency. You can use
> either "mvn -version" or "mvn enforcer:display-info" to verify what version
> is active.
> Non-release builds can temporarily build with a newer JDK version by
> setting the
> 'compileSource' property (eg. mvn -DcompileSource=1.8 clean package).
> Found Banned Dependency: org.apache.logging.log4j:log4j-api:jar:2.11.1
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (HBASE-22804) Provide an API to get list of successful regions and total expected regions in Canary
[ https://issues.apache.org/jira/browse/HBASE-22804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caroline updated HBASE-22804: - Attachment: HBASE-22804.branch-1.009.patch > Provide an API to get list of successful regions and total expected regions > in Canary > - > > Key: HBASE-22804 > URL: https://issues.apache.org/jira/browse/HBASE-22804 > Project: HBase > Issue Type: Improvement > Components: canary >Affects Versions: 3.0.0, 1.3.0, 1.4.0, 1.5.0, 2.0.0, 2.1.5, 2.2.1 >Reporter: Caroline >Assignee: Caroline >Priority: Minor > Labels: Canary > Attachments: HBASE-22804.branch-1.001.patch, > HBASE-22804.branch-1.002.patch, HBASE-22804.branch-1.003.patch, > HBASE-22804.branch-1.004.patch, HBASE-22804.branch-1.005.patch, > HBASE-22804.branch-1.006.patch, HBASE-22804.branch-1.007.patch, > HBASE-22804.branch-1.008.patch, HBASE-22804.branch-1.009.patch, > HBASE-22804.branch-1.009.patch, HBASE-22804.branch-2.001.patch, > HBASE-22804.branch-2.002.patch, HBASE-22804.branch-2.003.patch, > HBASE-22804.branch-2.004.patch, HBASE-22804.branch-2.005.patch, > HBASE-22804.branch-2.006.patch, HBASE-22804.master.001.patch, > HBASE-22804.master.002.patch, HBASE-22804.master.003.patch, > HBASE-22804.master.004.patch, HBASE-22804.master.005.patch, > HBASE-22804.master.006.patch > > > At present HBase Canary tool only prints the successes as part of logs. > Providing an API to get the list of successes, as well as total number of > expected regions, will make it easier to get a more accurate availability > estimate. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23002) [HBCK2/hbase-operator-tools] Create an assembly that builds an hbase-operator-tools tgz
[ https://issues.apache.org/jira/browse/HBASE-23002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926735#comment-16926735 ] Peter Somogyi commented on HBASE-23002: --- Based on [~busbey]'s comment on [PR#28|https://github.com/apache/hbase-operator-tools/pull/28] we can exclude slf4j-api from the generated tarball since that's already on hbase's classpath. > [HBCK2/hbase-operator-tools] Create an assembly that builds an > hbase-operator-tools tgz > --- > > Key: HBASE-23002 > URL: https://issues.apache.org/jira/browse/HBASE-23002 > Project: HBase > Issue Type: Task >Reporter: stack >Priority: Major > > Was going to build a convenience binary tgz as part of the first release of > hbase-operator-tools. Not sure how just yet; best would be if it were a > fatjar with all dependencies but that'd be kinda insane at same time since > the tgz would be massive. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23002) [HBCK2/hbase-operator-tools] Create an assembly that builds an hbase-operator-tools tgz
[ https://issues.apache.org/jira/browse/HBASE-23002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926738#comment-16926738 ] stack commented on HBASE-23002: --- Thanks for feedback. Addressing in next push. Keep the feedback coming. > [HBCK2/hbase-operator-tools] Create an assembly that builds an > hbase-operator-tools tgz > --- > > Key: HBASE-23002 > URL: https://issues.apache.org/jira/browse/HBASE-23002 > Project: HBase > Issue Type: Task >Reporter: stack >Priority: Major > > Was going to build a convenience binary tgz as part of the first release of > hbase-operator-tools. Not sure how just yet; best would be if it were a > fatjar with all dependencies but that'd be kinda insane at same time since > the tgz would be massive. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [hbase] Apache-HBase commented on issue #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux
Apache-HBase commented on issue #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux URL: https://github.com/apache/hbase/pull/604#issuecomment-530005751 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 1m 13s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 0s | No case conflicting files found. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :yellow_heart: | test4tests | 0m 0s | 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. | ||| _ master Compile Tests _ | | :blue_heart: | mvndep | 0m 34s | Maven dependency ordering for branch | | :green_heart: | mvninstall | 5m 47s | master passed | | :green_heart: | compile | 1m 0s | master passed | | :green_heart: | shadedjars | 4m 57s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 0m 27s | master passed | ||| _ Patch Compile Tests _ | | :blue_heart: | mvndep | 0m 14s | Maven dependency ordering for patch | | :green_heart: | mvninstall | 5m 26s | the patch passed | | :green_heart: | compile | 1m 0s | the patch passed | | :green_heart: | javac | 1m 0s | the patch passed | | :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | :green_heart: | xml | 0m 3s | The patch has no ill-formed XML file. | | :green_heart: | shadedjars | 4m 54s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 17m 6s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | javadoc | 0m 26s | the patch passed | ||| _ Other Tests _ | | :green_heart: | unit | 1m 1s | hbase-shaded in the patch passed. | | :green_heart: | unit | 0m 22s | hbase-shaded-testing-util in the patch passed. | | :green_heart: | asflicense | 0m 21s | The patch does not generate ASF License warnings. | | | | 51m 35s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-604/2/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/604 | | Optional Tests | dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile | | uname | Linux 7ab3ecf919f9 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-604/out/precommit/personality/provided.sh | | git revision | master / 4ca760fe9d | | Default Java | 1.8.0_181 | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-604/2/testReport/ | | Max. process+thread count | 403 (vs. ulimit of 1) | | modules | C: hbase-shaded hbase-shaded/hbase-shaded-testing-util U: hbase-shaded | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-604/2/console | | versions | git=2.11.0 maven=2018-06-17T18:33:14Z) | | Powered by | Apache Yetus 0.11.0 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-23002) [HBCK2/hbase-operator-tools] Create an assembly that builds an hbase-operator-tools tgz
[ https://issues.apache.org/jira/browse/HBASE-23002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926743#comment-16926743 ] stack commented on HBASE-23002: --- Pushes to address above (except for bit about adding MIT license) > [HBCK2/hbase-operator-tools] Create an assembly that builds an > hbase-operator-tools tgz > --- > > Key: HBASE-23002 > URL: https://issues.apache.org/jira/browse/HBASE-23002 > Project: HBase > Issue Type: Task >Reporter: stack >Priority: Major > > Was going to build a convenience binary tgz as part of the first release of > hbase-operator-tools. Not sure how just yet; best would be if it were a > fatjar with all dependencies but that'd be kinda insane at same time since > the tgz would be massive. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-22804) Provide an API to get list of successful regions and total expected regions in Canary
[
https://issues.apache.org/jira/browse/HBASE-22804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926741#comment-16926741
]
HBase QA commented on HBASE-22804:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 29m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} yetus {color} | {color:red} 0m 14s{color}
| {color:red} Unprocessed flag(s): --skip-errorprone {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.1 Server=19.03.1 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/891/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-22804 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12979979/HBASE-22804.branch-1.009.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/891/console |
| versions | git=1.9.1 |
| Powered by | Apache Yetus 0.11.0 https://yetus.apache.org |
This message was automatically generated.
> Provide an API to get list of successful regions and total expected regions
> in Canary
> -
>
> Key: HBASE-22804
> URL: https://issues.apache.org/jira/browse/HBASE-22804
> Project: HBase
> Issue Type: Improvement
> Components: canary
>Affects Versions: 3.0.0, 1.3.0, 1.4.0, 1.5.0, 2.0.0, 2.1.5, 2.2.1
>Reporter: Caroline
>Assignee: Caroline
>Priority: Minor
> Labels: Canary
> Attachments: HBASE-22804.branch-1.001.patch,
> HBASE-22804.branch-1.002.patch, HBASE-22804.branch-1.003.patch,
> HBASE-22804.branch-1.004.patch, HBASE-22804.branch-1.005.patch,
> HBASE-22804.branch-1.006.patch, HBASE-22804.branch-1.007.patch,
> HBASE-22804.branch-1.008.patch, HBASE-22804.branch-1.009.patch,
> HBASE-22804.branch-1.009.patch, HBASE-22804.branch-2.001.patch,
> HBASE-22804.branch-2.002.patch, HBASE-22804.branch-2.003.patch,
> HBASE-22804.branch-2.004.patch, HBASE-22804.branch-2.005.patch,
> HBASE-22804.branch-2.006.patch, HBASE-22804.master.001.patch,
> HBASE-22804.master.002.patch, HBASE-22804.master.003.patch,
> HBASE-22804.master.004.patch, HBASE-22804.master.005.patch,
> HBASE-22804.master.006.patch
>
>
> At present HBase Canary tool only prints the successes as part of logs.
> Providing an API to get the list of successes, as well as total number of
> expected regions, will make it easier to get a more accurate availability
> estimate.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase] Apache-HBase commented on issue #601: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin
Apache-HBase commented on issue #601: HBASE-22932 Add rs group management methods in Admin and AsyncAdmin URL: https://github.com/apache/hbase/pull/601#issuecomment-530013759 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | :blue_heart: | reexec | 0m 42s | Docker mode activated. | ||| _ Prechecks _ | | :green_heart: | dupname | 0m 1s | No case conflicting files found. | | :blue_heart: | prototool | 0m 0s | prototool was not available. | | :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | :green_heart: | test4tests | 0m 0s | The patch appears to include 9 new or modified test files. | ||| _ HBASE-22514 Compile Tests _ | | :blue_heart: | mvndep | 0m 37s | Maven dependency ordering for branch | | :green_heart: | mvninstall | 5m 42s | HBASE-22514 passed | | :green_heart: | compile | 2m 46s | HBASE-22514 passed | | :green_heart: | checkstyle | 2m 50s | HBASE-22514 passed | | :green_heart: | shadedjars | 4m 35s | branch has no errors when building our shaded downstream artifacts. | | :green_heart: | javadoc | 1m 45s | HBASE-22514 passed | | :blue_heart: | spotbugs | 1m 30s | Used deprecated FindBugs config; considering switching to SpotBugs. | | :green_heart: | findbugs | 9m 17s | HBASE-22514 passed | ||| _ Patch Compile Tests _ | | :blue_heart: | mvndep | 0m 14s | Maven dependency ordering for patch | | :green_heart: | mvninstall | 4m 52s | the patch passed | | :green_heart: | compile | 2m 35s | the patch passed | | :green_heart: | cc | 2m 35s | the patch passed | | :green_heart: | javac | 2m 35s | the patch passed | | :broken_heart: | checkstyle | 0m 36s | hbase-client: The patch generated 19 new + 162 unchanged - 0 fixed = 181 total (was 162) | | :broken_heart: | checkstyle | 1m 28s | hbase-server: The patch generated 35 new + 111 unchanged - 0 fixed = 146 total (was 111) | | :broken_heart: | whitespace | 0m 0s | The patch has 2 line(s) that end in whitespace. Use git apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply | | :green_heart: | shadedjars | 5m 11s | patch has no errors when building our shaded downstream artifacts. | | :green_heart: | hadoopcheck | 17m 8s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2. | | :green_heart: | hbaseprotoc | 2m 29s | the patch passed | | :broken_heart: | javadoc | 0m 36s | hbase-server generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0) | | :green_heart: | findbugs | 10m 14s | the patch passed | ||| _ Other Tests _ | | :green_heart: | unit | 0m 42s | hbase-protocol-shaded in the patch passed. | | :broken_heart: | unit | 1m 35s | hbase-client in the patch failed. | | :broken_heart: | unit | 156m 20s | hbase-server in the patch failed. | | :green_heart: | unit | 3m 50s | hbase-thrift in the patch passed. | | :green_heart: | asflicense | 2m 8s | The patch does not generate ASF License warnings. | | | | 247m 41s | | | Reason | Tests | |---:|:--| | Failed junit tests | hadoop.hbase.client.TestInterfaceAlign | | | hadoop.hbase.rsgroup.TestMigrateRSGroupInfo | | | hadoop.hbase.rsgroup.TestRSGroupsAdmin1 | | | hadoop.hbase.rsgroup.TestRSGroupsKillRS | | | hadoop.hbase.rsgroup.TestRSGroupsBasics | | | hadoop.hbase.rsgroup.TestRSGroupsBalance | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/2/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/601 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool | | uname | Linux 599313bda677 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-601/out/precommit/personality/provided.sh | | git revision | HBASE-22514 / 728d9fe198 | | Default Java | 1.8.0_181 | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/2/artifact/out/diff-checkstyle-hbase-client.txt | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/2/artifact/out/diff-checkstyle-hbase-server.txt | | whitespace | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-601/2/artifact/out/whitespace-eol.txt | | javadoc | https://builds.apache.org/job/HBase-
[GitHub] [hbase] busbey commented on a change in pull request #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux
busbey commented on a change in pull request #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux URL: https://github.com/apache/hbase/pull/604#discussion_r322842506 ## File path: hbase-shaded/hbase-shaded-testing-util/pom.xml ## @@ -133,9 +133,9 @@ org.codehaus.jackson -jackson-mapper-asl +jackson-jaxrs 1.9.13 -test +compile Review comment: the jackson-mapper-asl dependency in the `hbase-shaded-testing-util-tester` module should be removed now I think? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (HBASE-22338) LICENSE file only contains Apache 2.0
[
https://issues.apache.org/jira/browse/HBASE-22338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926780#comment-16926780
]
Rabi Kumar K C commented on HBASE-22338:
Regarding the progress of license and notice aggregation, I added
{{src/main/appended-resources/META-INF/}} in hbase-kafka-proxy and
hbase-kafka-model and added the aggregated non-ALv2 licenses and notices. Yes,
there are some GPL, LGPL but they are in combination with other licenses. I
will finish the license aggregation for sub-modules of hbase-spark by tomorrow
and will create the pull request for review. And I am putting together the
licenses and notice files manually. If I find any dependency with public domain
or unknown license then will update here
Please do let me know [~busbey] if what I am doing is correct.
> LICENSE file only contains Apache 2.0
> -
>
> Key: HBASE-22338
> URL: https://issues.apache.org/jira/browse/HBASE-22338
> Project: HBase
> Issue Type: Bug
> Components: hbase-connectors
>Affects Versions: connector-1.0.0
>Reporter: Peter Somogyi
>Assignee: Rabi Kumar K C
>Priority: Critical
> Fix For: connector-1.0.1
>
> Attachments: hbase-connectors-dependency.html
>
>
> LICENSE.md file has only Apache 2.0 licenses but we package dependencies that
> use different ones. For example jcodings uses MIT.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [hbase] busbey merged pull request #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux
busbey merged pull request #604: HBASE-23007 UnsatisfiedLinkError when using hbase-shaded packages under linux URL: https://github.com/apache/hbase/pull/604 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (HBASE-23007) UnsatisfiedLinkError when using hbase-shaded packages under linux
[
https://issues.apache.org/jira/browse/HBASE-23007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-23007:
Priority: Critical (was: Major)
> UnsatisfiedLinkError when using hbase-shaded packages under linux
> -
>
> Key: HBASE-23007
> URL: https://issues.apache.org/jira/browse/HBASE-23007
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 3.0.0
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Critical
>
> If we use hbase-shaded-* packages under linux, we get the following exception:
> {noformat}
> 2019-08-26 16:36:10,413 ERROR [Time-limited test] regionserver.HRegionServer
> (HRegionServer.java:(662)) - Failed construction RegionServer
> java.lang.UnsatisfiedLinkError: failed to load the required native library
> at
> org.apache.hbase.thirdparty.io.netty.channel.epoll.Epoll.ensureAvailability(Epoll.java:79)
> …
> Caused by: java.lang.UnsatisfiedLinkError: could not load a native library:
> org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64
> at
> org.apache.hbase.thirdparty.io.netty.util.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:224)
> {noformat}
> {{liborg_apache_hbase_thirdparty_netty_transport_native_epoll_x86_64.so}} is
> in the shaded jar files, but
> {{org_apache_hbase_thirdparty_org.apache.hadoop.hbase.shaded.netty_transport_native_epoll_x86_64.so}}
> is not.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-23000) Fix all consistently failing tests in branch-1.3
[
https://issues.apache.org/jira/browse/HBASE-23000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926798#comment-16926798
]
Rushabh S Shah commented on HBASE-23000:
I did some analysis yesterday. Found the commit that caused these tests to fail.
This is the jira: https://issues.apache.org/jira/browse/HBASE-22627
I reverted just 1 commit from branch-1.3 head and ran all the failing tests
and it succeeded. See the results below.
{noformat}
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @ hbase-server ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoad
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 112.481
s - in org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoad
[INFO] Running org.apache.hadoop.hbase.regionserver.wal.TestLogRollAbort
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.036 s
- in org.apache.hadoop.hbase.regionserver.wal.TestLogRollAbort
[INFO] Running org.apache.hadoop.hbase.master.TestMasterFileSystemWithWALDir
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.381 s
- in org.apache.hadoop.hbase.master.TestMasterFileSystemWithWALDir
[INFO] Running org.apache.hadoop.hbase.fs.TestBlockReorder
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.484 s
- in org.apache.hadoop.hbase.fs.TestBlockReorder
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] --- maven-surefire-plugin:2.22.2:test (secondPartTestsExecution) @
hbase-server ---
[INFO] Tests are skipped.
[INFO]
{noformat}
git log output:
{noformat}
commit e55a9054dacfacdef1dcb2d8d18e41dfd107f78e (HEAD -> HBASE-23000)
Author: Rushabh
Date: Tue Sep 10 09:42:26 2019 -0700
Revert "HBASE-22627 Port HBASE-22617 (Recovered WAL directories not getting
cleaned up) to branch-1 (#339)"
This reverts commit 13d1c231ba010854e3a3d2d5b9e028b40c28e3e0.
commit 64c0ac5dd4e2dac664c58cbe309a9d8b4a69c4c9 (origin/branch-1.3, branch-1.3)
Author: ravowlga123
Date: Thu Aug 29 17:29:24 2019 +0200
HBASE-22900 Multiple httpcore and httpclient versions included in binary
package (branch-1.3 and branch-1.4)
closes #563
Signed-off-by: Jan Hentschel
Signed-off-by: Sean Busbey
{noformat}
I will post how the test fails in next post.
> Fix all consistently failing tests in branch-1.3
>
>
> Key: HBASE-23000
> URL: https://issues.apache.org/jira/browse/HBASE-23000
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 1.3.6
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Major
>
> Flaky test report:
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.3/Flaky_20Test_20Report/dashboard.html#job_2
> In last 30 builds this test failed all 30 times.
> Here is the stack trace:
> {noformat}
> Stacktrace
> java.io.IOException: Shutting down
> at
> org.apache.hadoop.hbase.fs.TestBlockReorder.testBlockLocation(TestBlockReorder.java:428)
> Caused by: java.lang.RuntimeException: Master not initialized after 20ms
> seconds
> at
> org.apache.hadoop.hbase.fs.TestBlockReorder.testBlockLocation(TestBlockReorder.java:428)
> {noformat}
> Link to latest jenkins build:
> https://builds.apache.org/job/HBase-Flaky-Tests/job/branch-1.3/9351/testReport/org.apache.hadoop.hbase.fs/TestBlockReorder/testBlockLocation/
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (HBASE-22997) Move to SLF4J
[
https://issues.apache.org/jira/browse/HBASE-22997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926803#comment-16926803
]
stack commented on HBASE-22997:
---
I still get the below w/ this patch in place:
{code}
+ mvn -B --settings
//Users/stack/checkouts/hbase-operator-tools/dev-support/create-release/hbase-repo-uZxSi/tmp-settings.xml
install assembly:single -DskipTests -Dcheckstyle.skip=true -Papache-release
-Prelease -
Dmaven.repo.local=/Users/stack/checkouts/hbase-operator-tools/dev-support/create-release/hbase-repo-uZxSi
.
09:31:28 [INFO] --- maven-enforcer-plugin:1.4:enforce
(min-maven-min-java-banned-xerces) @ hbase-hbck2 ---
09:31:31 [INFO] Restricted to JDK 1.8 yet
org.apache.logging.log4j:log4j-api:jar:2.11.1:compile contains
META-INF/versions/9/module-info.class targeted to JDK 1.9
09:31:32 [WARNING] Rule 3:
org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message:
HBase has unsupported dependencies.
HBase requires that all dependencies be compiled with version 1.8 or earlier
of the JDK to properly build from source. You appear to be using a newer
dependency. You can use
either "mvn -version" or "mvn enforcer:display-info" to verify what version
is active.
Non-release builds can temporarily build with a newer JDK version by setting
the
'compileSource' property (eg. mvn -DcompileSource=1.8 clean package).
Found Banned Dependency: org.apache.logging.log4j:log4j-api:jar:2.11.1
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{code}
Trying to figure why...
> Move to SLF4J
> -
>
> Key: HBASE-22997
> URL: https://issues.apache.org/jira/browse/HBASE-22997
> Project: HBase
> Issue Type: Sub-task
> Components: hbase-operator-tools
>Affects Versions: operator-1.0.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
> Fix For: operator-1.0.0
>
>
> Currently hbase-operator-tools uses org.apache.logging.log4j while the rest
> of our projects have SLF4J.
> When building the project with release profile the enforce plugin fails on
> org.apache.logging.log4j:log4j-api:jar:2.11.1 dependency
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4:enforce
> (min-maven-min-java-banned-xerces) @ hbase-hbck2 ---
> [INFO] Restricted to JDK 1.8 yet
> org.apache.logging.log4j:log4j-api:jar:2.11.1:compile contains
> META-INF/versions/9/module-info.class targeted to JDK 1.9
> [WARNING] Rule 3: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion
> failed with message:
> HBase has unsupported dependencies.
> HBase requires that all dependencies be compiled with version 1.8 or earlier
> of the JDK to properly build from source. You appear to be using a newer
> dependency. You can use
> either "mvn -version" or "mvn enforcer:display-info" to verify what version
> is active.
> Non-release builds can temporarily build with a newer JDK version by
> setting the
> 'compileSource' property (eg. mvn -DcompileSource=1.8 clean package).
> Found Banned Dependency: org.apache.logging.log4j:log4j-api:jar:2.11.1
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (HBASE-22627) Port HBASE-22617 (Recovered WAL directories not getting cleaned up) to branch-1
[ https://issues.apache.org/jira/browse/HBASE-22627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-22627: --- Priority: Blocker (was: Major) > Port HBASE-22617 (Recovered WAL directories not getting cleaned up) to > branch-1 > --- > > Key: HBASE-22627 > URL: https://issues.apache.org/jira/browse/HBASE-22627 > Project: HBase > Issue Type: Sub-task >Affects Versions: 1.5.0, 1.4.10, 1.3.5 >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Blocker > Fix For: 1.5.0, 1.3.6, 1.4.11 > > Attachments: HBASE-22627-branch-1.patch, HBASE-22627-branch-1.patch, > HBASE-22627-branch-1.patch > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (HBASE-23000) Fix all consistently failing tests in branch-1.3
[
https://issues.apache.org/jira/browse/HBASE-23000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926808#comment-16926808
]
Andrew Purtell commented on HBASE-23000:
Ok, well HBASE-22627 is a critical bug fix and cannot be reverted, so we shall
need to fix what it broke. I had different test results when porting
HBASE-22627. Not doubting the results here, but wondering if more is going on.
> Fix all consistently failing tests in branch-1.3
>
>
> Key: HBASE-23000
> URL: https://issues.apache.org/jira/browse/HBASE-23000
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 1.3.6
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Major
>
> Flaky test report:
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.3/Flaky_20Test_20Report/dashboard.html#job_2
> In last 30 builds this test failed all 30 times.
> Here is the stack trace:
> {noformat}
> Stacktrace
> java.io.IOException: Shutting down
> at
> org.apache.hadoop.hbase.fs.TestBlockReorder.testBlockLocation(TestBlockReorder.java:428)
> Caused by: java.lang.RuntimeException: Master not initialized after 20ms
> seconds
> at
> org.apache.hadoop.hbase.fs.TestBlockReorder.testBlockLocation(TestBlockReorder.java:428)
> {noformat}
> Link to latest jenkins build:
> https://builds.apache.org/job/HBase-Flaky-Tests/job/branch-1.3/9351/testReport/org.apache.hadoop.hbase.fs/TestBlockReorder/testBlockLocation/
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
