[jira] [Commented] (HBASE-27403) Remove 'Remove unhelpful javadoc stubs' spotless rule for now
[
https://issues.apache.org/jira/browse/HBASE-27403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612482#comment-17612482
]
Hudson commented on HBASE-27403:
Results for branch branch-2
[build #655 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/655/]:
(/) *{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/655/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/655/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/655/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/655/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}
> Remove 'Remove unhelpful javadoc stubs' spotless rule for now
> -
>
> Key: HBASE-27403
> URL: https://issues.apache.org/jira/browse/HBASE-27403
> 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
>
>
> Until we fix the spotless issue:
> https://github.com/diffplug/spotless/issues/1359
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-27359) Publish binaries and maven artifacts for both hadoop2 and hadoop3
[ https://issues.apache.org/jira/browse/HBASE-27359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612478#comment-17612478 ] Andrew Kyle Purtell commented on HBASE-27359: - Back this week. Should have some time. > Publish binaries and maven artifacts for both hadoop2 and hadoop3 > - > > Key: HBASE-27359 > URL: https://issues.apache.org/jira/browse/HBASE-27359 > Project: HBase > Issue Type: Improvement > Components: build, community, pom, scripts >Reporter: Duo Zhang >Assignee: Andrew Kyle Purtell >Priority: Major > > As per the discussion in this thread > https://lists.apache.org/thread/y05gspk4mnxsz6nk7hc5ots8wt50366b > And this is possible after we land HBASE-27340. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-27109) Move replication queue storage from zookeeper to a separated HBase table
[
https://issues.apache.org/jira/browse/HBASE-27109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612460#comment-17612460
]
Hudson commented on HBASE-27109:
Results for branch HBASE-27109/table_based_rqs
[build #25 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/HBASE-27109%252Ftable_based_rqs/25/]:
(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/HBASE-27109%252Ftable_based_rqs/25/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/HBASE-27109%252Ftable_based_rqs/25/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/HBASE-27109%252Ftable_based_rqs/25/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}
> Move replication queue storage from zookeeper to a separated HBase table
>
>
> Key: HBASE-27109
> URL: https://issues.apache.org/jira/browse/HBASE-27109
> Project: HBase
> Issue Type: New Feature
> Components: Replication
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
>
> This is a more specific issue based on the works which are already done in
> HBASE-15867.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[ https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kyle Purtell updated HBASE-27381: Fix Version/s: 2.5.1 2.4.15 Assignee: Bryan Beaudreault Status: Patch Available (was: Open) > Still seeing 'Stuck' in static initialization creating RegionInfo instance > -- > > Key: HBASE-27381 > URL: https://issues.apache.org/jira/browse/HBASE-27381 > Project: HBase > Issue Type: Bug >Reporter: Bryan Beaudreault >Assignee: Bryan Beaudreault >Priority: Major > Fix For: 2.5.1, 2.4.15 > > > See https://issues.apache.org/jira/browse/HBASE-24896 for the original > description. Despite having that fix, we are seeing this issue in a > 2.4.6-based deploy. We recently started seeing it as we were moving to > centos8. I'm not sure why the centos version would affect this, otherwise the > hbase server version and java versions were not changing. > We're seeing this in a non-trivial number of new centos8 servers that we spin > up. I'm pushing a hotfix which removes RegionInfo.UNDEFINED to see if that > resolves our issue. > As mentioned in my last comments on that jira, it could be that this field is > still an issue because according to > [https://stackoverflow.com/questions/28631656/runnable-thread-state-but-in-object-wait:] > > Such deadlocks may be caused by a [typical > > bug|https://bugs.openjdk.org/browse/JDK-8037567] when a subclass is > > referenced from a static initializer. > If that's true, in this case MutableRegionInfo is a subclass/implementer of > RegionInfo, so that could trigger it. Granted the linked bug is marked "Not > An Issue". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27410) Document TLS mutual authentication
[ https://issues.apache.org/jira/browse/HBASE-27410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Beaudreault updated HBASE-27410: -- Issue Type: Task (was: Improvement) > Document TLS mutual authentication > -- > > Key: HBASE-27410 > URL: https://issues.apache.org/jira/browse/HBASE-27410 > Project: HBase > Issue Type: Task >Reporter: Bryan Beaudreault >Priority: Major > Labels: tls > Fix For: 2.6.0, 3.0.0-alpha-4 > > > Now that HBASE-27280 has landed, we need to update docs to include the new > features. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27410) Document TLS mutual authentication
[ https://issues.apache.org/jira/browse/HBASE-27410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Beaudreault updated HBASE-27410: -- Labels: tls (was: ) > Document TLS mutual authentication > -- > > Key: HBASE-27410 > URL: https://issues.apache.org/jira/browse/HBASE-27410 > Project: HBase > Issue Type: Improvement >Reporter: Bryan Beaudreault >Priority: Major > Labels: tls > Fix For: 2.6.0, 3.0.0-alpha-4 > > > Now that HBASE-27280 has landed, we need to update docs to include the new > features. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27410) Document TLS mutual authentication
Bryan Beaudreault created HBASE-27410: - Summary: Document TLS mutual authentication Key: HBASE-27410 URL: https://issues.apache.org/jira/browse/HBASE-27410 Project: HBase Issue Type: Improvement Reporter: Bryan Beaudreault Fix For: 2.6.0, 3.0.0-alpha-4 Now that HBASE-27280 has landed, we need to update docs to include the new features. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27226) Document native TLS support in Netty RPC
[
https://issues.apache.org/jira/browse/HBASE-27226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault updated HBASE-27226:
--
Labels: tls (was: )
> Document native TLS support in Netty RPC
>
>
> Key: HBASE-27226
> URL: https://issues.apache.org/jira/browse/HBASE-27226
> Project: HBase
> Issue Type: Task
> Components: documentation
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Labels: tls
> Fix For: 3.0.0-alpha-4
>
>
> Add a new section to the HBase book on how a developer can get this going.
> Should include
> * relevant TLS properties added in X509Util.java which need to be added to
> hbase-site.xml
> * how to generate a self-signed CA and certs using
> {{{}keytool{}}}/{{{}openssl{}}}
> * any known limitations
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27342) Use Hadoop Credentials API to retrieve passwords of TLS key/trust stores
[ https://issues.apache.org/jira/browse/HBASE-27342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Beaudreault updated HBASE-27342: -- Labels: tls (was: ) > Use Hadoop Credentials API to retrieve passwords of TLS key/trust stores > > > Key: HBASE-27342 > URL: https://issues.apache.org/jira/browse/HBASE-27342 > Project: HBase > Issue Type: Improvement > Components: IPC/RPC, security >Reporter: Andor Molnar >Assignee: Andor Molnar >Priority: Major > Labels: tls > Fix For: 2.6.0, 3.0.0-alpha-4 > > > Based on a discussion in the TLS Jira and mailing list, it would be > beneficial to protect the password of trust and key stores for TLS encryption > support in Netty RPC. > Hadoop Credentials API is built for the same purpose, extensible and simple > to use: > [https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/CredentialProviderAPI.html] > -- 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=17612373#comment-17612373
]
Hudson commented on HBASE-27365:
Results for branch master
[build #692 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/692/]:
(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/master/692/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/692/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/master/692/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
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
>
> 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-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[ https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612372#comment-17612372 ] Bryan Beaudreault commented on HBASE-27381: --- Thanks Andrew. I just put a PR up > Still seeing 'Stuck' in static initialization creating RegionInfo instance > -- > > Key: HBASE-27381 > URL: https://issues.apache.org/jira/browse/HBASE-27381 > Project: HBase > Issue Type: Bug >Reporter: Bryan Beaudreault >Priority: Major > > See https://issues.apache.org/jira/browse/HBASE-24896 for the original > description. Despite having that fix, we are seeing this issue in a > 2.4.6-based deploy. We recently started seeing it as we were moving to > centos8. I'm not sure why the centos version would affect this, otherwise the > hbase server version and java versions were not changing. > We're seeing this in a non-trivial number of new centos8 servers that we spin > up. I'm pushing a hotfix which removes RegionInfo.UNDEFINED to see if that > resolves our issue. > As mentioned in my last comments on that jira, it could be that this field is > still an issue because according to > [https://stackoverflow.com/questions/28631656/runnable-thread-state-but-in-object-wait:] > > Such deadlocks may be caused by a [typical > > bug|https://bugs.openjdk.org/browse/JDK-8037567] when a subclass is > > referenced from a static initializer. > If that's true, in this case MutableRegionInfo is a subclass/implementer of > RegionInfo, so that could trigger it. Granted the linked bug is marked "Not > An Issue". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HBASE-27381) Still seeing 'Stuck' in static initialization creating RegionInfo instance
[
https://issues.apache.org/jira/browse/HBASE-27381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612367#comment-17612367
]
Andrew Kyle Purtell commented on HBASE-27381:
-
{quote}Removing RegionInfo.UNDEFINED has eliminated the deadlocks we were
seeing. This is probably no surprise
{quote}
+1 for removal. We should get this into the next 2.4 and 2.5 releases. I will
defend the change.
> Still seeing 'Stuck' in static initialization creating RegionInfo instance
> --
>
> Key: HBASE-27381
> URL: https://issues.apache.org/jira/browse/HBASE-27381
> Project: HBase
> Issue Type: Bug
>Reporter: Bryan Beaudreault
>Priority: Major
>
> See https://issues.apache.org/jira/browse/HBASE-24896 for the original
> description. Despite having that fix, we are seeing this issue in a
> 2.4.6-based deploy. We recently started seeing it as we were moving to
> centos8. I'm not sure why the centos version would affect this, otherwise the
> hbase server version and java versions were not changing.
> We're seeing this in a non-trivial number of new centos8 servers that we spin
> up. I'm pushing a hotfix which removes RegionInfo.UNDEFINED to see if that
> resolves our issue.
> As mentioned in my last comments on that jira, it could be that this field is
> still an issue because according to
> [https://stackoverflow.com/questions/28631656/runnable-thread-state-but-in-object-wait:]
> > Such deadlocks may be caused by a [typical
> > bug|https://bugs.openjdk.org/browse/JDK-8037567] when a subclass is
> > referenced from a static initializer.
> If that's true, in this case MutableRegionInfo is a subclass/implementer of
> RegionInfo, so that could trigger it. Granted the linked bug is marked "Not
> An Issue".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (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 updated HBASE-27401: -- Component/s: documentation > 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 > Attachments: ns_at_the_end, ns_in_the_middle > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27400) The 'Remove unhelpful javadoc stubs' spotless rule will leave a 'n' instead of '\n'
[ https://issues.apache.org/jira/browse/HBASE-27400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-27400: -- Component/s: documentation > The 'Remove unhelpful javadoc stubs' spotless rule will leave a 'n' instead > of '\n' > --- > > Key: HBASE-27400 > URL: https://issues.apache.org/jira/browse/HBASE-27400 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Duo Zhang >Priority: Major > > That's why there are lots of 'n' in our code base... > Let me find a way to fix this and clean up all the 'n's. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27403) Remove 'Remove unhelpful javadoc stubs' spotless rule for now
[ https://issues.apache.org/jira/browse/HBASE-27403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-27403: -- Component/s: documentation > Remove 'Remove unhelpful javadoc stubs' spotless rule for now > - > > Key: HBASE-27403 > URL: https://issues.apache.org/jira/browse/HBASE-27403 > 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 > > > Until we fix the spotless issue: > https://github.com/diffplug/spotless/issues/1359 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27409) Fix the javadoc for WARCRecord
Duo Zhang created HBASE-27409: - Summary: 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 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] [Updated] (HBASE-27403) Remove 'Remove unhelpful javadoc stubs' spotless rule for now
[ https://issues.apache.org/jira/browse/HBASE-27403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-27403: -- Fix Version/s: 2.6.0 2.5.1 3.0.0-alpha-4 2.4.15 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.4+. Thanks [~ndimiduk] for reviewing! > Remove 'Remove unhelpful javadoc stubs' spotless rule for now > - > > Key: HBASE-27403 > URL: https://issues.apache.org/jira/browse/HBASE-27403 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4, 2.4.15 > > > Until we fix the spotless issue: > https://github.com/diffplug/spotless/issues/1359 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27408) Improve BucketAllocatorException log to always include HFile name
Bryan Beaudreault created HBASE-27408:
-
Summary: Improve BucketAllocatorException log to always include
HFile name
Key: HBASE-27408
URL: https://issues.apache.org/jira/browse/HBASE-27408
Project: HBase
Issue Type: Improvement
Reporter: Bryan Beaudreault
In HBASE-26444 the logging around BucketAllocatorException was improved. One
thing I'm noticing is that I'm often seeing logs like this:
{quote}2022-10-03T13:13:18,284 [main-BucketCacheWriter-0] WARN
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache: Most recent failed
allocation after 6 ms; Message: Allocation too big size=771956; adjust
BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate if size seems
reasonable and you want it cached.
{quote}
According to the logic in the code, this means the failure was for an
HFileBlock but the block's getColumnFamily and/or getTableName were null. I'm
not sure why that is the case, we don't have any special customizations here.
But as a result we don't print any indication of the hfile name. We should add
an option to fallback here on the default printing which includes the
re.getKey() (HFile name) in all cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HBASE-27407) Bug in JMX metrics description
[ https://issues.apache.org/jira/browse/HBASE-27407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Kovacs updated HBASE-27407: Description: 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. was: When trying to access the JMX metrics' description via the "description=true" URL parameter, any value is accepted. The current version only checks 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. > Bug in JMX metrics description > -- > > 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 > > 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] [Created] (HBASE-27407) Bug in JMX metrics description
Luca Kovacs created HBASE-27407: --- Summary: Bug in JMX metrics description Key: HBASE-27407 URL: https://issues.apache.org/jira/browse/HBASE-27407 Project: HBase Issue Type: Bug Components: metrics Affects Versions: 3.0.0-alpha-3, 2.6.0 Reporter: Luca Kovacs Assignee: Luca Kovacs When trying to access the JMX metrics' description via the "description=true" URL parameter, any value is accepted. The current version only checks 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] [Updated] (HBASE-27406) Make "/prometheus" endpoint accessible from HBase UI
[ https://issues.apache.org/jira/browse/HBASE-27406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Kovacs updated HBASE-27406: Description: Prometheus metrics feature were added in HBASE-20904, but it's not in the UI yet, so the only option to use it is the URL. I would like to make a change in the web UI, so it can be accessed via a dropdown menu there and I would like to include the description option, so metrics can be viewed with or without description. was: Prometheus metrics feature were added in HBASE-20904, but it's not in the UI yet, so you can only access it via the URL. I would like to make a change in the web UI, so it can be accessed from there. Also I would like to include the description option, so metrics can be viewed with or without > Make "/prometheus" endpoint accessible from HBase UI > > > Key: HBASE-27406 > URL: https://issues.apache.org/jira/browse/HBASE-27406 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 2.6.0, 3.0.0-alpha-3 >Reporter: Luca Kovacs >Assignee: Luca Kovacs >Priority: Minor > > Prometheus metrics feature were added in HBASE-20904, but it's not in the UI > yet, so the only option to use it is the URL. > I would like to make a change in the web UI, so it can be accessed via a > dropdown menu there and I would like to include the description option, so > metrics can be viewed with or without description. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HBASE-27406) Make "/prometheus" endpoint accessible from HBase UI
[ https://issues.apache.org/jira/browse/HBASE-27406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Kovacs updated HBASE-27406: Description: Prometheus metrics feature were added in HBASE-20904, but it's not in the UI yet, so you can only access it via the URL. I would like to make a change in the web UI, so it can be accessed from there. Also I would like to include the description option, so metrics can be viewed with or without was: Prometheus metrics feature were added in [HBASE-20904|https://issues.apache.org/jira/browse/HBASE-20904], but it's not in the UI yet, so you can only access it via the URL. I would like to make a change in the web UI, so it can be accessed from there. > Make "/prometheus" endpoint accessible from HBase UI > > > Key: HBASE-27406 > URL: https://issues.apache.org/jira/browse/HBASE-27406 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 2.6.0, 3.0.0-alpha-3 >Reporter: Luca Kovacs >Assignee: Luca Kovacs >Priority: Minor > > Prometheus metrics feature were added in HBASE-20904, but it's not in the UI > yet, so you can only access it via the URL. > I would like to make a change in the web UI, so it can be accessed from > there. > Also I would like to include the description option, so metrics can be viewed > with or without -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27406) Make "/prometheus" endpoint accessible from HBase UI
Luca Kovacs created HBASE-27406: --- Summary: Make "/prometheus" endpoint accessible from HBase UI Key: HBASE-27406 URL: https://issues.apache.org/jira/browse/HBASE-27406 Project: HBase Issue Type: Improvement Components: UI Affects Versions: 3.0.0-alpha-3, 2.6.0 Reporter: Luca Kovacs Assignee: Luca Kovacs Prometheus metrics feature were added in [HBASE-20904|https://issues.apache.org/jira/browse/HBASE-20904], but it's not in the UI yet, so you can only access it via the URL. I would like to make a change in the web UI, so it can be accessed from there. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HBASE-27406) Make "/prometheus" endpoint accessible from HBase UI
[ https://issues.apache.org/jira/browse/HBASE-27406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-27406 started by Luca Kovacs. --- > Make "/prometheus" endpoint accessible from HBase UI > > > Key: HBASE-27406 > URL: https://issues.apache.org/jira/browse/HBASE-27406 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 2.6.0, 3.0.0-alpha-3 >Reporter: Luca Kovacs >Assignee: Luca Kovacs >Priority: Minor > > Prometheus metrics feature were added in > [HBASE-20904|https://issues.apache.org/jira/browse/HBASE-20904], but it's not > in the UI yet, so you can only access it via the URL. > I would like to make a change in the web UI, so it can be accessed from there. -- This message was sent by Atlassian Jira (v8.20.10#820010)
