[jira] [Commented] (HBASE-27395) Adding description to Prometheus metrics
[
https://issues.apache.org/jira/browse/HBASE-27395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614363#comment-17614363
]
Hudson commented on HBASE-27395:
Results for branch branch-2
[build #659 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/659/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/659/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/659/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/659/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/659/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Adding description to Prometheus metrics
>
>
> Key: HBASE-27395
> URL: https://issues.apache.org/jira/browse/HBASE-27395
> Project: HBase
> Issue Type: Improvement
> Components: metrics
>Affects Versions: 2.6.0, 3.0.0-alpha-3
>Reporter: Luca Kovacs
>Assignee: Luca Kovacs
>Priority: Minor
> Fix For: 2.6.0, 3.0.0-alpha-4
>
>
> As /jmx endpoint provides enabling description for metrics by using
> 'description=true' URL parameter I would like to implement this feature for
> the /prometheus endpoint as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [hbase] Apache-HBase commented on pull request #4811: HBASE-27405 Fix the replication hfile/log cleaner report that the replication table does not exist
Apache-HBase commented on PR #4811: URL: https://github.com/apache/hbase/pull/4811#issuecomment-1272220777 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 27s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +1 :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ HBASE-27109/table_based_rqs Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 11s | HBASE-27109/table_based_rqs passed | | +1 :green_heart: | compile | 2m 16s | HBASE-27109/table_based_rqs passed | | +1 :green_heart: | checkstyle | 0m 33s | HBASE-27109/table_based_rqs passed | | +1 :green_heart: | spotless | 0m 37s | branch has no errors when running spotless:check. | | +1 :green_heart: | spotbugs | 1m 17s | HBASE-27109/table_based_rqs passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 8s | the patch passed | | +1 :green_heart: | compile | 2m 16s | the patch passed | | +1 :green_heart: | javac | 2m 16s | the patch passed | | +1 :green_heart: | checkstyle | 0m 31s | the patch passed | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | hadoopcheck | 7m 47s | Patch does not cause any errors with Hadoop 3.2.4 3.3.4. | | +1 :green_heart: | spotless | 0m 40s | patch has no errors when running spotless:check. | | +1 :green_heart: | spotbugs | 1m 24s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 9s | The patch does not generate ASF License warnings. | | | | 27m 17s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4811/3/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4811 | | Optional Tests | dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile | | uname | Linux 37b0f061fc7c 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | HBASE-27109/table_based_rqs / de2d20aac2 | | Default Java | Temurin-1.8.0_345-b01 | | Max. process+thread count | 64 (vs. ulimit of 3) | | modules | C: hbase-server U: hbase-server | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4811/3/console | | versions | git=2.17.1 maven=3.6.3 spotbugs=4.7.2 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #4819: HBASE-27420 Allow non-loopback for zk standalone server in minizkcluster
Apache-HBase commented on PR #4819: URL: https://github.com/apache/hbase/pull/4819#issuecomment-1272194953 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 57s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +1 :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 14s | master passed | | +1 :green_heart: | compile | 0m 19s | master passed | | +1 :green_heart: | checkstyle | 0m 9s | master passed | | +1 :green_heart: | spotless | 0m 39s | branch has no errors when running spotless:check. | | +1 :green_heart: | spotbugs | 0m 21s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 10s | the patch passed | | +1 :green_heart: | compile | 0m 19s | the patch passed | | +1 :green_heart: | javac | 0m 19s | the patch passed | | +1 :green_heart: | checkstyle | 0m 8s | the patch passed | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | hadoopcheck | 7m 53s | Patch does not cause any errors with Hadoop 3.2.4 3.3.4. | | +1 :green_heart: | spotless | 0m 40s | patch has no errors when running spotless:check. | | +1 :green_heart: | spotbugs | 0m 25s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 9s | The patch does not generate ASF License warnings. | | | | 21m 32s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4819 | | Optional Tests | dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile | | uname | Linux 483c6c71339d 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Temurin-1.8.0_345-b01 | | Max. process+thread count | 60 (vs. ulimit of 3) | | modules | C: hbase-zookeeper U: hbase-zookeeper | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/console | | versions | git=2.17.1 maven=3.6.3 spotbugs=4.7.2 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #4819: HBASE-27420 Allow non-loopback for zk standalone server in minizkcluster
Apache-HBase commented on PR #4819: URL: https://github.com/apache/hbase/pull/4819#issuecomment-1272194273 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 49s | Docker mode activated. | | -0 :warning: | yetus | 0m 3s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 41s | master passed | | +1 :green_heart: | compile | 0m 10s | master passed | | +1 :green_heart: | shadedjars | 3m 59s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 9s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 4s | the patch passed | | +1 :green_heart: | compile | 0m 10s | the patch passed | | +1 :green_heart: | javac | 0m 10s | the patch passed | | +1 :green_heart: | shadedjars | 3m 58s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 9s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 0m 34s | hbase-zookeeper in the patch passed. | | | | 15m 54s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4819 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux bd5b4ab8eb90 5.4.0-1085-aws #92~18.04.1-Ubuntu SMP Wed Aug 31 17:21:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Temurin-1.8.0_345-b01 | | Test Results | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/testReport/ | | Max. process+thread count | 160 (vs. ulimit of 3) | | modules | C: hbase-zookeeper U: hbase-zookeeper | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/console | | versions | git=2.17.1 maven=3.6.3 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #4819: HBASE-27420 Allow non-loopback for zk standalone server in minizkcluster
Apache-HBase commented on PR #4819: URL: https://github.com/apache/hbase/pull/4819#issuecomment-1272194143 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 1m 2s | Docker mode activated. | | -0 :warning: | yetus | 0m 4s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 46s | master passed | | +1 :green_heart: | compile | 0m 15s | master passed | | +1 :green_heart: | shadedjars | 3m 47s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 14s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 32s | the patch passed | | +1 :green_heart: | compile | 0m 14s | the patch passed | | +1 :green_heart: | javac | 0m 14s | the patch passed | | +1 :green_heart: | shadedjars | 3m 49s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 12s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 0m 41s | hbase-zookeeper in the patch passed. | | | | 16m 39s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4819 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux 96dbbcdb4b34 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Eclipse Adoptium-11.0.16.1+1 | | Test Results | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/testReport/ | | Max. process+thread count | 221 (vs. ulimit of 3) | | modules | C: hbase-zookeeper U: hbase-zookeeper | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/2/console | | versions | git=2.17.1 maven=3.6.3 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #4819: HBASE-27420 Allow non-loopback for zk standalone server in minizkcluster
Apache-HBase commented on PR #4819: URL: https://github.com/apache/hbase/pull/4819#issuecomment-1272176518 :broken_heart: **-1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 59s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +1 :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 25s | master passed | | +1 :green_heart: | compile | 0m 21s | master passed | | +1 :green_heart: | checkstyle | 0m 10s | master passed | | +1 :green_heart: | spotless | 0m 41s | branch has no errors when running spotless:check. | | +1 :green_heart: | spotbugs | 0m 23s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 10s | the patch passed | | +1 :green_heart: | compile | 0m 19s | the patch passed | | +1 :green_heart: | javac | 0m 19s | the patch passed | | -0 :warning: | checkstyle | 0m 9s | hbase-zookeeper: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0) | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | hadoopcheck | 7m 56s | Patch does not cause any errors with Hadoop 3.2.4 3.3.4. | | -1 :x: | spotless | 0m 18s | patch has 23 errors when running spotless:check, run spotless:apply to fix. | | +1 :green_heart: | spotbugs | 0m 25s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 11s | The patch does not generate ASF License warnings. | | | | 21m 47s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4819 | | Optional Tests | dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile | | uname | Linux a2b017fd04fd 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Temurin-1.8.0_345-b01 | | checkstyle | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-zookeeper.txt | | spotless | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/artifact/yetus-general-check/output/patch-spotless.txt | | Max. process+thread count | 64 (vs. ulimit of 3) | | modules | C: hbase-zookeeper U: hbase-zookeeper | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/console | | versions | git=2.17.1 maven=3.6.3 spotbugs=4.7.2 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #4819: HBASE-27420 Allow non-loopback for zk standalone server in minizkcluster
Apache-HBase commented on PR #4819: URL: https://github.com/apache/hbase/pull/4819#issuecomment-1272175020 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 59s | Docker mode activated. | | -0 :warning: | yetus | 0m 4s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 38s | master passed | | +1 :green_heart: | compile | 0m 15s | master passed | | +1 :green_heart: | shadedjars | 3m 49s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 14s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 34s | the patch passed | | +1 :green_heart: | compile | 0m 13s | the patch passed | | +1 :green_heart: | javac | 0m 13s | the patch passed | | +1 :green_heart: | shadedjars | 3m 46s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 12s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 0m 41s | hbase-zookeeper in the patch passed. | | | | 16m 25s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4819 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux a203c029c16c 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Eclipse Adoptium-11.0.16.1+1 | | Test Results | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/testReport/ | | Max. process+thread count | 279 (vs. ulimit of 3) | | modules | C: hbase-zookeeper U: hbase-zookeeper | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/console | | versions | git=2.17.1 maven=3.6.3 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #4819: HBASE-27420 Allow non-loopback for zk standalone server in minizkcluster
Apache-HBase commented on PR #4819: URL: https://github.com/apache/hbase/pull/4819#issuecomment-1272174882 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 40s | Docker mode activated. | | -0 :warning: | yetus | 0m 3s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 30s | master passed | | +1 :green_heart: | compile | 0m 10s | master passed | | +1 :green_heart: | shadedjars | 4m 3s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 11s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 2m 3s | the patch passed | | +1 :green_heart: | compile | 0m 10s | the patch passed | | +1 :green_heart: | javac | 0m 10s | the patch passed | | +1 :green_heart: | shadedjars | 4m 2s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 9s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 0m 35s | hbase-zookeeper in the patch passed. | | | | 15m 41s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4819 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux c210aab837af 5.4.0-1071-aws #76~18.04.1-Ubuntu SMP Mon Mar 28 17:49:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Temurin-1.8.0_345-b01 | | Test Results | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/testReport/ | | Max. process+thread count | 211 (vs. ulimit of 3) | | modules | C: hbase-zookeeper U: hbase-zookeeper | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4819/1/console | | versions | git=2.17.1 maven=3.6.3 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
[ https://issues.apache.org/jira/browse/HBASE-27420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeet Malhotra updated HBASE-27420: - Status: Patch Available (was: In Progress) > Failure while connecting to zk if HBase is running in standalone mode in a > container > > > Key: HBASE-27420 > URL: https://issues.apache.org/jira/browse/HBASE-27420 > Project: HBase > Issue Type: Bug > Components: Zookeeper >Reporter: Sanjeet Malhotra >Assignee: Sanjeet Malhotra >Priority: Major > Fix For: 3.0.0-alpha-4 > > > With [this change|https://issues.apache.org/jira/browse/HBASE-23993] > zookeeper will only listen for client connections on 127.0.0.1 in standalone > mode. If HBase is running in standalone mode inside a docker container and > docker port forwarding is being used to connect to HBase inside container > then, any client trying to connect to zk will have destination IP as > container's private IP rather than loopback IP. This will cause zk to reject > all client connections being initiated from outside the container. > Thus, we need a way to make zk listen for client connections on IP other than > loopback. zk already provides a property named `clientPortAddress` to specify > the address to listen for client connections. And, we can specify zk > properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to > allow user to specify the IP address that zk will listen on using > `hbase.zookeeper.property.clientPortAddress` and if its not specified then > default to loopback as per current behaviour. > This way, the tests will still remain unimpacted and HBase can also be used > in standalone mode in a container. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
[ https://issues.apache.org/jira/browse/HBASE-27420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27420 started by Sanjeet Malhotra. > Failure while connecting to zk if HBase is running in standalone mode in a > container > > > Key: HBASE-27420 > URL: https://issues.apache.org/jira/browse/HBASE-27420 > Project: HBase > Issue Type: Bug > Components: Zookeeper >Reporter: Sanjeet Malhotra >Assignee: Sanjeet Malhotra >Priority: Major > Fix For: 3.0.0-alpha-4 > > > With [this change|https://issues.apache.org/jira/browse/HBASE-23993] > zookeeper will only listen for client connections on 127.0.0.1 in standalone > mode. If HBase is running in standalone mode inside a docker container and > docker port forwarding is being used to connect to HBase inside container > then, any client trying to connect to zk will have destination IP as > container's private IP rather than loopback IP. This will cause zk to reject > all client connections being initiated from outside the container. > Thus, we need a way to make zk listen for client connections on IP other than > loopback. zk already provides a property named `clientPortAddress` to specify > the address to listen for client connections. And, we can specify zk > properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to > allow user to specify the IP address that zk will listen on using > `hbase.zookeeper.property.clientPortAddress` and if its not specified then > default to loopback as per current behaviour. > This way, the tests will still remain unimpacted and HBase can also be used > in standalone mode in a container. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
[ https://issues.apache.org/jira/browse/HBASE-27420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27420 stopped by Sanjeet Malhotra. > Failure while connecting to zk if HBase is running in standalone mode in a > container > > > Key: HBASE-27420 > URL: https://issues.apache.org/jira/browse/HBASE-27420 > Project: HBase > Issue Type: Bug > Components: Zookeeper >Reporter: Sanjeet Malhotra >Assignee: Sanjeet Malhotra >Priority: Major > Fix For: 3.0.0-alpha-4 > > > With [this change|https://issues.apache.org/jira/browse/HBASE-23993] > zookeeper will only listen for client connections on 127.0.0.1 in standalone > mode. If HBase is running in standalone mode inside a docker container and > docker port forwarding is being used to connect to HBase inside container > then, any client trying to connect to zk will have destination IP as > container's private IP rather than loopback IP. This will cause zk to reject > all client connections being initiated from outside the container. > Thus, we need a way to make zk listen for client connections on IP other than > loopback. zk already provides a property named `clientPortAddress` to specify > the address to listen for client connections. And, we can specify zk > properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to > allow user to specify the IP address that zk will listen on using > `hbase.zookeeper.property.clientPortAddress` and if its not specified then > default to loopback as per current behaviour. > This way, the tests will still remain unimpacted and HBase can also be used > in standalone mode in a container. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [hbase] sanjeet006py opened a new pull request, #4819: HBASE-27420 Allow non-loopback for zk standalone server in minizkcluster
sanjeet006py opened a new pull request, #4819: URL: https://github.com/apache/hbase/pull/4819 Link to JIRA: https://issues.apache.org/jira/browse/HBASE-27420 Add a provision to allow zk to listen for client connections on non-loopback IP. -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #4818: HBASE-27419 Update to hbase-thirdparty 4.1.2
Apache-HBase commented on PR #4818: URL: https://github.com/apache/hbase/pull/4818#issuecomment-1272134078 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 3m 28s | Docker mode activated. | | -0 :warning: | yetus | 0m 2s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +0 :ok: | mvndep | 0m 21s | Maven dependency ordering for branch | | +1 :green_heart: | mvninstall | 2m 26s | master passed | | +1 :green_heart: | compile | 1m 30s | master passed | | +1 :green_heart: | shadedjars | 4m 11s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 1m 41s | master passed | ||| _ Patch Compile Tests _ | | +0 :ok: | mvndep | 0m 30s | Maven dependency ordering for patch | | +1 :green_heart: | mvninstall | 2m 6s | the patch passed | | +1 :green_heart: | compile | 1m 29s | the patch passed | | +1 :green_heart: | javac | 1m 29s | the patch passed | | +1 :green_heart: | shadedjars | 4m 6s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 1m 42s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 401m 59s | root in the patch passed. | | | | 428m 48s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4818 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux 73dc7656bac2 5.4.0-1071-aws #76~18.04.1-Ubuntu SMP Mon Mar 28 17:49:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Temurin-1.8.0_345-b01 | | Test Results | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/testReport/ | | Max. process+thread count | 4867 (vs. ulimit of 3) | | modules | C: hbase-protocol-shaded hbase-examples . U: . | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/console | | versions | git=2.17.1 maven=3.6.3 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (HBASE-27401) Clean up current broken 'n's in our javadoc
[
https://issues.apache.org/jira/browse/HBASE-27401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614297#comment-17614297
]
Hudson commented on HBASE-27401:
Results for branch branch-2.4
[build #437 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/437/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/437/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/437/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/437/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/437/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Clean up current broken 'n's in our javadoc
> ---
>
> Key: HBASE-27401
> URL: https://issues.apache.org/jira/browse/HBASE-27401
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15
>
> Attachments: ns_at_the_end, ns_in_the_middle
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [hbase] Apache-HBase commented on pull request #4818: HBASE-27419 Update to hbase-thirdparty 4.1.2
Apache-HBase commented on PR #4818: URL: https://github.com/apache/hbase/pull/4818#issuecomment-1272056363 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 1m 4s | Docker mode activated. | | -0 :warning: | yetus | 0m 3s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +0 :ok: | mvndep | 0m 19s | Maven dependency ordering for branch | | +1 :green_heart: | mvninstall | 2m 49s | master passed | | +1 :green_heart: | compile | 1m 58s | master passed | | +1 :green_heart: | shadedjars | 3m 49s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 2m 23s | master passed | ||| _ Patch Compile Tests _ | | +0 :ok: | mvndep | 0m 18s | Maven dependency ordering for patch | | +1 :green_heart: | mvninstall | 2m 29s | the patch passed | | +1 :green_heart: | compile | 1m 56s | the patch passed | | +1 :green_heart: | javac | 1m 56s | the patch passed | | +1 :green_heart: | shadedjars | 3m 48s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 2m 24s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 273m 33s | root in the patch passed. | | | | 299m 37s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4818 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux b3be86ebce9b 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Eclipse Adoptium-11.0.16.1+1 | | Test Results | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/testReport/ | | Max. process+thread count | 4978 (vs. ulimit of 3) | | modules | C: hbase-protocol-shaded hbase-examples . U: . | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/console | | versions | git=2.17.1 maven=3.6.3 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (HBASE-27365) Minimise block addition failures due to no space in bucket cache writers queue by introducing wait time
[
https://issues.apache.org/jira/browse/HBASE-27365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614239#comment-17614239
]
Hudson commented on HBASE-27365:
Results for branch branch-2.5
[build #220 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Minimise block addition failures due to no space in bucket cache writers
> queue by introducing wait time
> ---
>
> Key: HBASE-27365
> URL: https://issues.apache.org/jira/browse/HBASE-27365
> Project: HBase
> Issue Type: Improvement
> Components: BucketCache
>Affects Versions: 3.0.0-alpha-3
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> Currently in bucket cache asynchronous caching mechanism introduced where
> initially the blocks to be cached will be added to queue and writer threads
> consume the blocks from the queue and write to bucket cache. In case if block
> writing to bucket cache is slow then there is a chance that queue of writer
> threads become full and following block additions will be failed. In case of
> slower storages like s3 might introduce latencies even if we enable bigger
> sizes of bucket cache using ephemeral storages. So we can allow configurable
> wait time while adding blocks to queue so that chances of queue free up is
> possible during the wait time and block addition failures can be minimised.
> To avoid the performance impact of wait time in regular read paths we can use
> the wait time mainly during background operations like compactions, flushes
> or prefetches etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27407) Fixing check for "description" request param in JMXJsonServlet.java
[
https://issues.apache.org/jira/browse/HBASE-27407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614238#comment-17614238
]
Hudson commented on HBASE-27407:
Results for branch branch-2.5
[build #220 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Fixing check for "description" request param in JMXJsonServlet.java
> ---
>
> Key: HBASE-27407
> URL: https://issues.apache.org/jira/browse/HBASE-27407
> Project: HBase
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.6.0, 3.0.0-alpha-3
>Reporter: Luca Kovacs
>Assignee: Luca Kovacs
>Priority: Minor
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> When trying to access the JMX metrics' description via the "description=true"
> URL parameter, any value is accepted.
> The current version checks only if "description" is in the URL parameter, but
> doesn't check the parameter value.
> I would like to fix this via checking if the parameter value is 'true' and
> showing the description only when this condition is met.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27409) Fix the javadoc for WARCRecord
[
https://issues.apache.org/jira/browse/HBASE-27409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614237#comment-17614237
]
Hudson commented on HBASE-27409:
Results for branch branch-2.5
[build #220 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Fix the javadoc for WARCRecord
> --
>
> Key: HBASE-27409
> URL: https://issues.apache.org/jira/browse/HBASE-27409
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4
>
>
> It has some special format and after landing HBASE-26899 we format it and
> lost the format...
> Let's try to revert it back and use some html tags to keep the format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27401) Clean up current broken 'n's in our javadoc
[
https://issues.apache.org/jira/browse/HBASE-27401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614240#comment-17614240
]
Hudson commented on HBASE-27401:
Results for branch branch-2.5
[build #220 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/220/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Clean up current broken 'n's in our javadoc
> ---
>
> Key: HBASE-27401
> URL: https://issues.apache.org/jira/browse/HBASE-27401
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15
>
> Attachments: ns_at_the_end, ns_in_the_middle
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27365) Minimise block addition failures due to no space in bucket cache writers queue by introducing wait time
[
https://issues.apache.org/jira/browse/HBASE-27365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614234#comment-17614234
]
Hudson commented on HBASE-27365:
Results for branch master
[build #696 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Minimise block addition failures due to no space in bucket cache writers
> queue by introducing wait time
> ---
>
> Key: HBASE-27365
> URL: https://issues.apache.org/jira/browse/HBASE-27365
> Project: HBase
> Issue Type: Improvement
> Components: BucketCache
>Affects Versions: 3.0.0-alpha-3
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> Currently in bucket cache asynchronous caching mechanism introduced where
> initially the blocks to be cached will be added to queue and writer threads
> consume the blocks from the queue and write to bucket cache. In case if block
> writing to bucket cache is slow then there is a chance that queue of writer
> threads become full and following block additions will be failed. In case of
> slower storages like s3 might introduce latencies even if we enable bigger
> sizes of bucket cache using ephemeral storages. So we can allow configurable
> wait time while adding blocks to queue so that chances of queue free up is
> possible during the wait time and block addition failures can be minimised.
> To avoid the performance impact of wait time in regular read paths we can use
> the wait time mainly during background operations like compactions, flushes
> or prefetches etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27401) Clean up current broken 'n's in our javadoc
[
https://issues.apache.org/jira/browse/HBASE-27401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614232#comment-17614232
]
Hudson commented on HBASE-27401:
Results for branch master
[build #696 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Clean up current broken 'n's in our javadoc
> ---
>
> Key: HBASE-27401
> URL: https://issues.apache.org/jira/browse/HBASE-27401
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15
>
> Attachments: ns_at_the_end, ns_in_the_middle
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27409) Fix the javadoc for WARCRecord
[
https://issues.apache.org/jira/browse/HBASE-27409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614233#comment-17614233
]
Hudson commented on HBASE-27409:
Results for branch master
[build #696 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Fix the javadoc for WARCRecord
> --
>
> Key: HBASE-27409
> URL: https://issues.apache.org/jira/browse/HBASE-27409
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4
>
>
> It has some special format and after landing HBASE-26899 we format it and
> lost the format...
> Let's try to revert it back and use some html tags to keep the format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27407) Fixing check for "description" request param in JMXJsonServlet.java
[
https://issues.apache.org/jira/browse/HBASE-27407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614231#comment-17614231
]
Hudson commented on HBASE-27407:
Results for branch master
[build #696 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/696/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Fixing check for "description" request param in JMXJsonServlet.java
> ---
>
> Key: HBASE-27407
> URL: https://issues.apache.org/jira/browse/HBASE-27407
> Project: HBase
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.6.0, 3.0.0-alpha-3
>Reporter: Luca Kovacs
>Assignee: Luca Kovacs
>Priority: Minor
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15
>
>
> When trying to access the JMX metrics' description via the "description=true"
> URL parameter, any value is accepted.
> The current version checks only if "description" is in the URL parameter, but
> doesn't check the parameter value.
> I would like to fix this via checking if the parameter value is 'true' and
> showing the description only when this condition is met.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-27112) Investigate Netty resource usage limits
[
https://issues.apache.org/jira/browse/HBASE-27112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-27112.
-
Resolution: Done
Closing as investigation completed with [~stack]'s contributions on the issue.
> Investigate Netty resource usage limits
> ---
>
> Key: HBASE-27112
> URL: https://issues.apache.org/jira/browse/HBASE-27112
> Project: HBase
> Issue Type: Sub-task
> Components: IPC/RPC
>Affects Versions: 2.5.0
>Reporter: Andrew Kyle Purtell
>Priority: Major
> Attachments: Image 7-11-22 at 10.12 PM.jpg, Image 7-12-22 at 10.45
> PM.jpg
>
>
> We leave Netty level resource limits unbounded. The number of threads to use
> for the event loop is default 0 (unbounded). The default for
> io.netty.eventLoop.maxPendingTasks is INT_MAX.
> We don't do that for our own RPC handlers. We have a notion of maximum
> handler pool size, with a default of 30, typically raised in production by
> the user. We constrain the depth of the request queue in multiple ways...
> limits on number of queued calls, limits on total size of calls data that can
> be queued (to avoid memory usage overrun, CoDel conditioning of the call
> queues if it is enabled, and so on.
> Under load can we pile up a excess of pending request state, such as direct
> buffers containing request bytes, at the netty layer because of downstream
> resource limits? Those limits will act as a bottleneck, as intended, and
> before would have also applied backpressure through RPC too, because
> SimpleRpcServer had thread limits ("hbase.ipc.server.read.threadpool.size",
> default 10), but Netty may be able to queue up a lot more, in comparison,
> because Netty has been optimized to prefer concurrency.
> Consider the hbase.netty.eventloop.rpcserver.thread.count default. It is 0
> (unbounded). I don't know what it can actually get up to in production,
> because we lack the metric, but there are diminishing returns when threads >
> cores so a reasonable default here could be
> Runtime.getRuntime().availableProcessors() instead of unbounded?
> maxPendingTasks probably should not be INT_MAX, but that may matter less.
> The tasks here are:
> - Instrument netty level resources to understand better actual resource
> allocations under load. Investigate what we need to plug in where to gain
> visibility.
> - Where instrumentation designed for this issue can be implemented as low
> overhead metrics, consider formally adding them as a metric.
> - Based on the findings from this instrumentation, consider and implement
> next steps. The goal would be to limit concurrency at the Netty layer in such
> a way that performance is still good, and under load we don't balloon
> resource usage at the Netty layer.
> If the instrumentation and experimental results indicate no changes are
> necessary, we can close this as Not A Problem or WontFix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [hbase] apurtell commented on a diff in pull request #4818: HBASE-27419 Update to hbase-thirdparty 4.1.2
apurtell commented on code in PR #4818: URL: https://github.com/apache/hbase/pull/4818#discussion_r990394445 ## hbase-examples/pom.xml: ## @@ -33,7 +33,7 @@ -3.17.3 +3.21.7 Review Comment: Ditto ## hbase-protocol-shaded/pom.xml: ## @@ -34,7 +34,7 @@ -3.21.1 +3.21.7 Review Comment: Maybe there is a way to tie this setting to hbase-thirdparty somehow. Have hbase-thirdparty export a version property in its POM that we can use here. -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] apurtell commented on a diff in pull request #4818: HBASE-27419 Update to hbase-thirdparty 4.1.2
apurtell commented on code in PR #4818: URL: https://github.com/apache/hbase/pull/4818#discussion_r990394138 ## hbase-protocol-shaded/pom.xml: ## @@ -34,7 +34,7 @@ -3.21.1 +3.21.7 Review Comment: Ditto ## pom.xml: ## @@ -1734,6 +1734,12 @@ test + + + staging + https://repository.apache.org/content/repositories/orgapachehbase-1496/ Review Comment: Should we just wait for a release? We don't need 'staging' here then. ## hbase-examples/pom.xml: ## @@ -33,7 +33,7 @@ -3.17.3 +3.21.7 Review Comment: Maybe there is a way to tie this setting to hbase-thirdparty somehow. Have hbase-thirdparty export a version property in its POM that we can use here. -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Work started] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
[ https://issues.apache.org/jira/browse/HBASE-27420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27420 started by Sanjeet Malhotra. > Failure while connecting to zk if HBase is running in standalone mode in a > container > > > Key: HBASE-27420 > URL: https://issues.apache.org/jira/browse/HBASE-27420 > Project: HBase > Issue Type: Bug > Components: Zookeeper >Reporter: Sanjeet Malhotra >Assignee: Sanjeet Malhotra >Priority: Major > Fix For: 3.0.0-alpha-4 > > > With [this change|https://issues.apache.org/jira/browse/HBASE-23993] > zookeeper will only listen for client connections on 127.0.0.1 in standalone > mode. If HBase is running in standalone mode inside a docker container and > docker port forwarding is being used to connect to HBase inside container > then, any client trying to connect to zk will have destination IP as > container's private IP rather than loopback IP. This will cause zk to reject > all client connections being initiated from outside the container. > Thus, we need a way to make zk listen for client connections on IP other than > loopback. zk already provides a property named `clientPortAddress` to specify > the address to listen for client connections. And, we can specify zk > properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to > allow user to specify the IP address that zk will listen on using > `hbase.zookeeper.property.clientPortAddress` and if its not specified then > default to loopback as per current behaviour. > This way, the tests will still remain unimpacted and HBase can also be used > in standalone mode in a container. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
[
https://issues.apache.org/jira/browse/HBASE-27420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeet Malhotra updated HBASE-27420:
-
Description:
With [this change|https://issues.apache.org/jira/browse/HBASE-23993] zookeeper
will only listen for client connections on 127.0.0.1 in standalone mode. If
HBase is running in standalone mode inside a docker container and docker port
forwarding is being used to connect to HBase inside container then, any client
trying to connect to zk will have destination IP as container's private IP
rather than loopback IP. This will cause zk to reject all client connections
being initiated from outside the container.
Thus, we need a way to make zk listen for client connections on IP other than
loopback. zk already provides a property named `clientPortAddress` to specify
the address to listen for client connections. And, we can specify zk properties
using `hbase.zookeeper.property.` prefix. Thus, the proposal is to allow user
to specify the IP address that zk will listen on using
`hbase.zookeeper.property.clientPortAddress` and if its not specified then
default to loopback as per current behaviour.
This way, the tests will still remain unimpacted and HBase can also be used in
standalone mode in a container.
was:
{*}{*}With this change zookeeper will only listen for client connections on
127.0.0.1 in standalone mode. If HBase is running in standalone mode inside a
docker container and docker port forwarding is being used to connect to HBase
inside container then, any client trying to connect to zk will have destination
IP as container's private IP rather than loopback IP. This will cause zk to
reject all client connections being initiated from outside the container.
Thus, we need a way to make zk listen for client connections on IP other than
loopback. zk already provides a property named `clientPortAddress` to specify
the address to listen for client connections. And, we can specify zk properties
using `hbase.zookeeper.property.` prefix. Thus, the proposal is to allow user
to specify the IP address that zk will listen on using
`hbase.zookeeper.property.clientPortAddress` and if its not specified then
default to loopback as per current behaviour.
This way, the tests will still remain unimpacted and HBase can also be used in
standalone mode in a container.
> Failure while connecting to zk if HBase is running in standalone mode in a
> container
>
>
> Key: HBASE-27420
> URL: https://issues.apache.org/jira/browse/HBASE-27420
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Reporter: Sanjeet Malhotra
>Assignee: Sanjeet Malhotra
>Priority: Major
> Fix For: 3.0.0-alpha-4
>
>
> With [this change|https://issues.apache.org/jira/browse/HBASE-23993]
> zookeeper will only listen for client connections on 127.0.0.1 in standalone
> mode. If HBase is running in standalone mode inside a docker container and
> docker port forwarding is being used to connect to HBase inside container
> then, any client trying to connect to zk will have destination IP as
> container's private IP rather than loopback IP. This will cause zk to reject
> all client connections being initiated from outside the container.
> Thus, we need a way to make zk listen for client connections on IP other than
> loopback. zk already provides a property named `clientPortAddress` to specify
> the address to listen for client connections. And, we can specify zk
> properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to
> allow user to specify the IP address that zk will listen on using
> `hbase.zookeeper.property.clientPortAddress` and if its not specified then
> default to loopback as per current behaviour.
> This way, the tests will still remain unimpacted and HBase can also be used
> in standalone mode in a container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
[
https://issues.apache.org/jira/browse/HBASE-27420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeet Malhotra updated HBASE-27420:
-
Description:
{*}{*}With this change zookeeper will only listen for client connections on
127.0.0.1 in standalone mode. If HBase is running in standalone mode inside a
docker container and docker port forwarding is being used to connect to HBase
inside container then, any client trying to connect to zk will have destination
IP as container's private IP rather than loopback IP. This will cause zk to
reject all client connections being initiated from outside the container.
Thus, we need a way to make zk listen for client connections on IP other than
loopback. zk already provides a property named `clientPortAddress` to specify
the address to listen for client connections. And, we can specify zk properties
using `hbase.zookeeper.property.` prefix. Thus, the proposal is to allow user
to specify the IP address that zk will listen on using
`hbase.zookeeper.property.clientPortAddress` and if its not specified then
default to loopback as per current behaviour.
This way, the tests will still remain unimpacted and HBase can also be used in
standalone mode in a container.
was:
{*}{*}With [this change|https://issues.apache.org/jira/browse/HBASE-23993]
zookeeper will only listen for client connections on 127.0.0.1 in standalone
mode. If HBase is running in standalone mode inside a docker container and
docker port forwarding is being used to connect to HBase inside container then,
any client trying to connect to zk will have destination IP as container's
private IP rather than loopback IP. This will cause zk to reject all client
connections being initiated from outside the container.
Thus, we need a way to make zk listen for client connections on IP other than
loopback. zk already provides a property named `clientPortAddress` to specify
the address to listen for client connections. And, we can specify zk properties
using `hbase.zookeeper.property.` prefix. Thus, the proposal is to allow user
to specify the IP address that zk will listen on using
`hbase.zookeeper.property.clientPortAddress` and if its not specified then
default to loopback as per current behaviour.
This way, the tests will still remain unimpacted and HBase can also be used in
standalone mode in a container.
> Failure while connecting to zk if HBase is running in standalone mode in a
> container
>
>
> Key: HBASE-27420
> URL: https://issues.apache.org/jira/browse/HBASE-27420
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Reporter: Sanjeet Malhotra
>Assignee: Sanjeet Malhotra
>Priority: Major
> Fix For: 3.0.0-alpha-4
>
>
> {*}{*}With this change zookeeper will only listen for client connections on
> 127.0.0.1 in standalone mode. If HBase is running in standalone mode inside a
> docker container and docker port forwarding is being used to connect to HBase
> inside container then, any client trying to connect to zk will have
> destination IP as container's private IP rather than loopback IP. This will
> cause zk to reject all client connections being initiated from outside the
> container.
> Thus, we need a way to make zk listen for client connections on IP other than
> loopback. zk already provides a property named `clientPortAddress` to specify
> the address to listen for client connections. And, we can specify zk
> properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to
> allow user to specify the IP address that zk will listen on using
> `hbase.zookeeper.property.clientPortAddress` and if its not specified then
> default to loopback as per current behaviour.
> This way, the tests will still remain unimpacted and HBase can also be used
> in standalone mode in a container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
[
https://issues.apache.org/jira/browse/HBASE-27420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeet Malhotra updated HBASE-27420:
-
Description:
{*}{*}With [this change|https://issues.apache.org/jira/browse/HBASE-23993]
zookeeper will only listen for client connections on 127.0.0.1 in standalone
mode. If HBase is running in standalone mode inside a docker container and
docker port forwarding is being used to connect to HBase inside container then,
any client trying to connect to zk will have destination IP as container's
private IP rather than loopback IP. This will cause zk to reject all client
connections being initiated from outside the container.
Thus, we need a way to make zk listen for client connections on IP other than
loopback. zk already provides a property named `clientPortAddress` to specify
the address to listen for client connections. And, we can specify zk properties
using `hbase.zookeeper.property.` prefix. Thus, the proposal is to allow user
to specify the IP address that zk will listen on using
`hbase.zookeeper.property.clientPortAddress` and if its not specified then
default to loopback as per current behaviour.
This way, the tests will still remain unimpacted and HBase can also be used in
standalone mode in a container.
was:
With this change zookeeper will only listen for client connections on 127.0.0.1
in standalone mode. If HBase is running in standalone mode inside a docker
container and docker port forwarding is being used to connect to HBase inside
container then, any client trying to connect to zk will have destination IP as
container's private IP rather than loopback IP. This will cause zk to reject
all client connections being initiated from outside the container.
Thus, we need a way to make zk listen for client connections on IP other than
loopback. zk already provides a property named `clientPortAddress` to specify
the address to listen for client connections. And, we can specify zk properties
using `hbase.zookeeper.property.` prefix. Thus, the proposal is to allow user
to specify the IP address that zk will listen on using
`hbase.zookeeper.property.clientPortAddress` and if its not specified then
default to loopback as per current behaviour.
This way, the tests will still remain unimpacted and HBase can also be used in
standalone mode in a container.
> Failure while connecting to zk if HBase is running in standalone mode in a
> container
>
>
> Key: HBASE-27420
> URL: https://issues.apache.org/jira/browse/HBASE-27420
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
>Reporter: Sanjeet Malhotra
>Assignee: Sanjeet Malhotra
>Priority: Major
> Fix For: 3.0.0-alpha-4
>
>
> {*}{*}With [this change|https://issues.apache.org/jira/browse/HBASE-23993]
> zookeeper will only listen for client connections on 127.0.0.1 in standalone
> mode. If HBase is running in standalone mode inside a docker container and
> docker port forwarding is being used to connect to HBase inside container
> then, any client trying to connect to zk will have destination IP as
> container's private IP rather than loopback IP. This will cause zk to reject
> all client connections being initiated from outside the container.
> Thus, we need a way to make zk listen for client connections on IP other than
> loopback. zk already provides a property named `clientPortAddress` to specify
> the address to listen for client connections. And, we can specify zk
> properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to
> allow user to specify the IP address that zk will listen on using
> `hbase.zookeeper.property.clientPortAddress` and if its not specified then
> default to loopback as per current behaviour.
> This way, the tests will still remain unimpacted and HBase can also be used
> in standalone mode in a container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27420) Failure while connecting to zk if HBase is running in standalone mode in a container
Sanjeet Malhotra created HBASE-27420: Summary: Failure while connecting to zk if HBase is running in standalone mode in a container Key: HBASE-27420 URL: https://issues.apache.org/jira/browse/HBASE-27420 Project: HBase Issue Type: Bug Components: Zookeeper Reporter: Sanjeet Malhotra Assignee: Sanjeet Malhotra Fix For: 3.0.0-alpha-4 With this change zookeeper will only listen for client connections on 127.0.0.1 in standalone mode. If HBase is running in standalone mode inside a docker container and docker port forwarding is being used to connect to HBase inside container then, any client trying to connect to zk will have destination IP as container's private IP rather than loopback IP. This will cause zk to reject all client connections being initiated from outside the container. Thus, we need a way to make zk listen for client connections on IP other than loopback. zk already provides a property named `clientPortAddress` to specify the address to listen for client connections. And, we can specify zk properties using `hbase.zookeeper.property.` prefix. Thus, the proposal is to allow user to specify the IP address that zk will listen on using `hbase.zookeeper.property.clientPortAddress` and if its not specified then default to loopback as per current behaviour. This way, the tests will still remain unimpacted and HBase can also be used in standalone mode in a container. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [hbase] Apache-HBase commented on pull request #4818: HBASE-27419 Update to hbase-thirdparty 4.1.2
Apache-HBase commented on PR #4818: URL: https://github.com/apache/hbase/pull/4818#issuecomment-1271769094 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 56s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ master Compile Tests _ | | +0 :ok: | mvndep | 0m 18s | Maven dependency ordering for branch | | +1 :green_heart: | mvninstall | 2m 22s | master passed | | +1 :green_heart: | compile | 6m 26s | master passed | | +1 :green_heart: | spotless | 0m 41s | branch has no errors when running spotless:check. | ||| _ Patch Compile Tests _ | | +0 :ok: | mvndep | 0m 17s | Maven dependency ordering for patch | | +1 :green_heart: | mvninstall | 2m 6s | the patch passed | | +1 :green_heart: | compile | 6m 12s | the patch passed | | -0 :warning: | javac | 6m 12s | root generated 1 new + 702 unchanged - 1 fixed = 703 total (was 703) | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | xml | 0m 2s | The patch has no ill-formed XML file. | | +1 :green_heart: | hadoopcheck | 7m 56s | Patch does not cause any errors with Hadoop 3.2.4 3.3.4. | | +1 :green_heart: | spotless | 0m 39s | patch has no errors when running spotless:check. | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 30s | The patch does not generate ASF License warnings. | | | | 33m 38s | | | Subsystem | Report/Notes | |--:|:-| | Docker | ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/4818 | | Optional Tests | dupname asflicense javac hadoopcheck spotless xml compile | | uname | Linux 4f21b71a6f29 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 46d37a70d6 | | Default Java | Temurin-1.8.0_345-b01 | | javac | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/artifact/yetus-general-check/output/diff-compile-javac-root.txt | | Max. process+thread count | 138 (vs. ulimit of 3) | | modules | C: hbase-protocol-shaded hbase-examples . U: . | | Console output | https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4818/1/console | | versions | git=2.17.1 maven=3.6.3 | | Powered by | Apache Yetus 0.12.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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache9 commented on pull request #4732: HBASE-27333 The condition for using the local hostname is the opposite
Apache9 commented on PR #4732: URL: https://github.com/apache/hbase/pull/4732#issuecomment-1271732725 This is introduced by https://issues.apache.org/jira/browse/HBASE-12954. It seemed that we wanted to solve the problem where a region server can not be accessed through the hostname which we bind to. From my understanding, the current logic seems reasonable. If we have configured the hostname to use, but it is different from what master seen us, then this should be a critical problem and we should abort the region server. If not, we just log it, and use the hostname seen by master as it is more likely to be accessed by others. Does anyone remember the reason why the code is like this? -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (HBASE-27419) Update to hbase-thirdparty 4.1.2
[ https://issues.apache.org/jira/browse/HBASE-27419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614068#comment-17614068 ] Duo Zhang commented on HBASE-27419: --- The RC is ready for vote now. Let me try to prepare a PR with the staging repo. > Update to hbase-thirdparty 4.1.2 > > > Key: HBASE-27419 > URL: https://issues.apache.org/jira/browse/HBASE-27419 > Project: HBase > Issue Type: Bug > Components: dependencies >Affects Versions: 2.5.0, 2.4.14 >Reporter: Andrew Kyle Purtell >Priority: Major > Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15 > > > Update to hbase-thirdparty 4.1.2 when it is released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-27419) Update to hbase-thirdparty 4.1.2
[ https://issues.apache.org/jira/browse/HBASE-27419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27419 started by Duo Zhang. - > Update to hbase-thirdparty 4.1.2 > > > Key: HBASE-27419 > URL: https://issues.apache.org/jira/browse/HBASE-27419 > Project: HBase > Issue Type: Bug > Components: dependencies >Affects Versions: 2.5.0, 2.4.14 >Reporter: Andrew Kyle Purtell >Assignee: Duo Zhang >Priority: Major > Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15 > > > Update to hbase-thirdparty 4.1.2 when it is released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-27419) Update to hbase-thirdparty 4.1.2
[ https://issues.apache.org/jira/browse/HBASE-27419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reassigned HBASE-27419: - Assignee: Duo Zhang > Update to hbase-thirdparty 4.1.2 > > > Key: HBASE-27419 > URL: https://issues.apache.org/jira/browse/HBASE-27419 > Project: HBase > Issue Type: Bug > Components: dependencies >Affects Versions: 2.5.0, 2.4.14 >Reporter: Andrew Kyle Purtell >Assignee: Duo Zhang >Priority: Major > Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15 > > > Update to hbase-thirdparty 4.1.2 when it is released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27419) Update to hbase-thirdparty 4.1.2
[ https://issues.apache.org/jira/browse/HBASE-27419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-27419: -- Component/s: dependencies > Update to hbase-thirdparty 4.1.2 > > > Key: HBASE-27419 > URL: https://issues.apache.org/jira/browse/HBASE-27419 > Project: HBase > Issue Type: Bug > Components: dependencies >Affects Versions: 2.5.0, 2.4.14 >Reporter: Andrew Kyle Purtell >Priority: Major > Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15 > > > Update to hbase-thirdparty 4.1.2 when it is released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [hbase-thirdparty] ndimiduk commented on pull request #90: HBASE-27412 [hbase-thirdparty] Bump dependency versions in hbase-thir…
ndimiduk commented on PR #90: URL: https://github.com/apache/hbase-thirdparty/pull/90#issuecomment-1271504383 Thanks guys. -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Work started] (HBASE-27418) Put up hbase-thirdparty 4.1.2RC0
[ https://issues.apache.org/jira/browse/HBASE-27418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27418 started by Duo Zhang. - > Put up hbase-thirdparty 4.1.2RC0 > > > Key: HBASE-27418 > URL: https://issues.apache.org/jira/browse/HBASE-27418 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HBASE-27418) Put up hbase-thirdparty 4.1.2RC0
[ https://issues.apache.org/jira/browse/HBASE-27418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reassigned HBASE-27418: - Assignee: Duo Zhang > Put up hbase-thirdparty 4.1.2RC0 > > > Key: HBASE-27418 > URL: https://issues.apache.org/jira/browse/HBASE-27418 > Project: HBase > Issue Type: Sub-task > Components: community, thirdparty >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27417) [hbase-thirdparty] Generate CHANGES.md and RELEASENOTES.md for 4.1.2
[ https://issues.apache.org/jira/browse/HBASE-27417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27417. --- Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~apurtell] for reviewing! > [hbase-thirdparty] Generate CHANGES.md and RELEASENOTES.md for 4.1.2 > > > Key: HBASE-27417 > URL: https://issues.apache.org/jira/browse/HBASE-27417 > Project: HBase > Issue Type: Sub-task > Components: thirdparty >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: thirdparty-4.1.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27395) Adding description to Prometheus metrics
[ https://issues.apache.org/jira/browse/HBASE-27395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros resolved HBASE-27395. - Fix Version/s: 2.6.0 3.0.0-alpha-4 Resolution: Fixed > Adding description to Prometheus metrics > > > Key: HBASE-27395 > URL: https://issues.apache.org/jira/browse/HBASE-27395 > Project: HBase > Issue Type: Improvement > Components: metrics >Affects Versions: 2.6.0, 3.0.0-alpha-3 >Reporter: Luca Kovacs >Assignee: Luca Kovacs >Priority: Minor > Fix For: 2.6.0, 3.0.0-alpha-4 > > > As /jmx endpoint provides enabling description for metrics by using > 'description=true' URL parameter I would like to implement this feature for > the /prometheus endpoint as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [hbase] meszibalu merged pull request #4807: HBASE-27395 Adding description to Prometheus metrics
meszibalu merged PR #4807: URL: https://github.com/apache/hbase/pull/4807 -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase-thirdparty] Apache9 merged pull request #92: HBASE-27417 [hbase-thirdparty] Generate CHANGES.md and RELEASENOTES.m…
Apache9 merged PR #92: URL: https://github.com/apache/hbase-thirdparty/pull/92 -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (HBASE-27401) Clean up current broken 'n's in our javadoc
[ https://issues.apache.org/jira/browse/HBASE-27401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27401. --- Fix Version/s: 2.4.15 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.4+. Thanks [~apurtell] for reviewing! > Clean up current broken 'n's in our javadoc > --- > > Key: HBASE-27401 > URL: https://issues.apache.org/jira/browse/HBASE-27401 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15 > > Attachments: ns_at_the_end, ns_in_the_middle > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [hbase] Apache9 commented on pull request #4811: HBASE-27405 Fix the replication hfile/log cleaner report that the replication table does not exist
Apache9 commented on PR #4811: URL: https://github.com/apache/hbase/pull/4811#issuecomment-1271324296 The failed UT is related? -- 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. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
