[jira] [Created] (AMBARI-25880) For hadoop_logs collection of Infra-solr, indexed log_message field is too large to copy to key_log_message field
guluo created AMBARI-25880:
--
Summary: For hadoop_logs collection of Infra-solr, indexed
log_message field is too large to copy to key_log_message field
Key: AMBARI-25880
URL: https://issues.apache.org/jira/browse/AMBARI-25880
Project: Ambari
Issue Type: Bug
Components: ambari-infra, ambari-logsearch
Affects Versions: 2.7.3
Reporter: guluo
The hadoop_logs collection of Infra-solr is used to store logs generated by
services, such as hadoop、spark， etc.
However, Infra-solr will report an error when the length of the single-line log
generated by services exceeds 2^15-2, Because Infra-solr cannot copy the data
of field log_message to field key_log_messag
{code:java}
//代码占位符
org.apache.solr.common.SolrException: Exception writing document id
54d786cd-f6a7-4746-9b17-e9b2b0fe389a to the index; possible analysis error:
Document contains at least one immense term in field="action" (whose UTF8
encoding is longer than the max length 32766), all of which were skipped.
Please correct the analyzer to not produce such terms. The prefix of the first
immense term is: '[98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98,
98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98]...', original
message: bytes can be at most 32766 in length; got 32767. Perhaps the document
has an indexed string field (solr.StrField) which is too large {code}
*Reproduce Step:*
1 Create a json File named data.json
[
{
"log_message": "",
"id": "54d786cd-f6a7-4746-9b17-e9b2b0fe3efa"
}
]
Note: the content of field log_message is a randomly generated string with a
length exceeding 2^15-2
2 Update the hadoop_logs
curl http://ip:port/solr/hadoop_logs/update?commit=true -H
'Content-type:application/json' --data-binary @data.json
3 Get the error message mentioned above
*similar issue：*
AMBARI-24067: Log Search: indexed string field could be too large for audit_logs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25782) Fix Ambari Metrics build failure
[ https://issues.apache.org/jira/browse/AMBARI-25782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25782: --- Epic Link: AMBARI-25860 Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) Issue Type: Bug (was: Task) > Fix Ambari Metrics build failure > > > Key: AMBARI-25782 > URL: https://issues.apache.org/jira/browse/AMBARI-25782 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: lucas >Assignee: lucas >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > Fix syntax, refactor and versions after forwarding from Ambari to > ambari-metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25780) Ambari metrics should upgrade hadoop and hbase for known CVE issues
[ https://issues.apache.org/jira/browse/AMBARI-25780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25780: --- Epic Link: AMBARI-25860 Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) > Ambari metrics should upgrade hadoop and hbase for known CVE issues > --- > > Key: AMBARI-25780 > URL: https://issues.apache.org/jira/browse/AMBARI-25780 > Project: Ambari > Issue Type: Bug >Reporter: Lei Yao >Assignee: lucas >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25808) Metrics data simulator throws NPE
[
https://issues.apache.org/jira/browse/AMBARI-25808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25808:
---
Epic Link: AMBARI-25860
Fix Version/s: ambari-metrics-3.0.0
(was: 2.0.0)
> Metrics data simulator throws NPE
> -
>
> Key: AMBARI-25808
> URL: https://issues.apache.org/jira/browse/AMBARI-25808
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.8, ambari-metrics-3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> user@host1 bin % ./start.sh localhost:6188 2
> {noformat}
> {code:java}
> 2022-12-10 00:00:15,245 INFO [main] loadsimulator.MetricsLoadSimulator
> (MetricsLoadSimulator.java:parseArgs(110)) - Recognized options:
> baseHostName=host1 hosts#=2 trafficMode=burst metricsHostName=localhost:6188
> collectIntervalMillis=15000 sendIntervalMillis=6 simulateMaster=false
> 2022-12-10 00:00:15,250 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/HOST.dat
> 2022-12-10 00:00:15,269 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/DATANODE.dat
> 2022-12-10 00:00:15,270 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/NODEMANAGER.dat
> 2022-12-10 00:00:15,272 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/SLAVE_HBASE.dat
> Exception in thread "main" java.lang.NullPointerException
> at java.io.Reader.(Reader.java:78)
> at java.io.InputStreamReader.(InputStreamReader.java:72)
> at
> org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.readMetrics(MetricsGeneratorConfigurer.java:72)
> at
> org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.createMetricsForHost(MetricsGeneratorConfigurer.java:57)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.createApplicationMetrics(LoadRunner.java:112)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.addMetricsWorkers(LoadRunner.java:100)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.prepareWorkers(LoadRunner.java:88)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.(LoadRunner.java:69)
> at
> org.apache.ambari.metrics.core.loadsimulator.MetricsLoadSimulator.main(MetricsLoadSimulator.java:48)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25810) Allow skipping Python unit tests in ambari-metrics
[ https://issues.apache.org/jira/browse/AMBARI-25810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25810: --- Epic Link: AMBARI-25860 Fix Version/s: ambari-metrics-3.0.0 (was: 2.0.0) > Allow skipping Python unit tests in ambari-metrics > -- > > Key: AMBARI-25810 > URL: https://issues.apache.org/jira/browse/AMBARI-25810 > Project: Ambari > Issue Type: Bug > Components: metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Minor > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > Currently skipPythonTests flag is available in ambari but not in metrics. > Lets add in metrics too. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25809) ambari-metrics-host-monitoring project build creates temp folder outside of target folder
[
https://issues.apache.org/jira/browse/AMBARI-25809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25809:
---
Epic Link: AMBARI-25860
Fix Version/s: ambari-metrics-3.0.0
(was: 2.8.0)
> ambari-metrics-host-monitoring project build creates temp folder outside of
> target folder
> -
>
> Key: AMBARI-25809
> URL: https://issues.apache.org/jira/browse/AMBARI-25809
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Labels: pull-request-available
> Fix For: ambari-metrics-3.0.0
>
>
> ambari-metrics-host-monitoring project creates
> ambari-metrics-host-monitoring\target\psutil_build_temp folder under ambari
> folder
> it should be created under the target folder
> Run mvn clean install -DskipTests then run git status to know the folder
> creation status
> {noformat}
> user1@host1 ambari-metrics-host-monitoring % git status
> On branch master
> Your branch is up to date with 'origin/master'.
> Untracked files:
> (use "git add ..." to include in what will be committed)
> "../ambari-metrics-host-monitoring\\target\\psutil_build_temp/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25819) Ambari Metrics build fails when using -Dbuild-rpm
[ https://issues.apache.org/jira/browse/AMBARI-25819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25819: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) > Ambari Metrics build fails when using -Dbuild-rpm > - > > Key: AMBARI-25819 > URL: https://issues.apache.org/jira/browse/AMBARI-25819 > Project: Ambari > Issue Type: Bug > Components: metrics > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: ambari-metrics-3.0.0 > > Attachments: image-2022-12-16-20-11-49-087.png > > > !image-2022-12-16-20-11-49-087.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25811) Optimize ambari metrics build time
[
https://issues.apache.org/jira/browse/AMBARI-25811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25811:
---
Epic Link: AMBARI-25860
Fix Version/s: ambari-metrics-3.0.0
(was: 2.0.0)
> Optimize ambari metrics build time
> --
>
> Key: AMBARI-25811
> URL: https://issues.apache.org/jira/browse/AMBARI-25811
> Project: Ambari
> Issue Type: Improvement
> Components: build, metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.8, ambari-metrics-3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently in ambari metrics build, most of the time is taken by
> ambari-metrics-assembly.
> Looks maven-assembly-plugin is taking lot of time in stitching the artifacts.
> Upgrading maven-assembly-plugin from 2.2-beta-5 to 3.4.2(latest version)
> reduces the build time significantly
> *Before change:*
> {noformat}
> 15:58:46,215 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT:
> 15:58:46,215 [INFO]
> 15:58:46,218 [INFO] ambari-metrics .
> SUCCESS [ 3.960 s]
> 15:58:46,220 [INFO] Ambari Metrics Common ..
> SUCCESS [ 11.492 s]
> 15:58:46,220 [INFO] Ambari Metrics Hadoop Sink .
> SUCCESS [ 7.655 s]
> 15:58:46,220 [INFO] Ambari Metrics Flume Sink ..
> SUCCESS [ 4.045 s]
> 15:58:46,220 [INFO] Ambari Metrics Kafka Sink ..
> SUCCESS [ 3.465 s]
> 15:58:46,220 [INFO] Ambari Metrics Storm Sink ..
> SUCCESS [ 2.887 s]
> 15:58:46,220 [INFO] Ambari Metrics Collector ...
> SUCCESS [ 19.416 s]
> 15:58:46,220 [INFO] Ambari Metrics Monitor .
> SUCCESS [ 4.791 s]
> 15:58:46,220 [INFO] Ambari Metrics Grafana .
> SUCCESS [ 2.838 s]
> 15:58:46,220 [INFO] Ambari Metrics Host Aggregator .
> SUCCESS [ 8.363 s]
> 15:58:46,220 [INFO] Ambari Metrics Assembly
> SUCCESS [09:09 min]
> 15:58:46,220 [INFO]
>
> 15:58:46,220 [INFO] BUILD SUCCESS
> 15:58:46,220 [INFO]
>
> 15:58:46,221 [INFO] Total time: 10:18 min
> 15:58:46,221 [INFO] Finished at: 2022-12-14T15:58:46+05:30
> {noformat}
> *After Change:*
> {noformat}
> 16:18:22,667 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT:
> 16:18:22,667 [INFO]
> 16:18:22,670 [INFO] ambari-metrics .
> SUCCESS [ 3.897 s]
> 16:18:22,671 [INFO] Ambari Metrics Common ..
> SUCCESS [ 10.880 s]
> 16:18:22,671 [INFO] Ambari Metrics Hadoop Sink .
> SUCCESS [ 4.681 s]
> 16:18:22,671 [INFO] Ambari Metrics Flume Sink ..
> SUCCESS [ 2.184 s]
> 16:18:22,671 [INFO] Ambari Metrics Kafka Sink ..
> SUCCESS [ 2.949 s]
> 16:18:22,671 [INFO] Ambari Metrics Storm Sink ..
> SUCCESS [ 3.071 s]
> 16:18:22,671 [INFO] Ambari Metrics Collector ...
> SUCCESS [ 18.471 s]
> 16:18:22,671 [INFO] Ambari Metrics Monitor .
> SUCCESS [ 5.416 s]
> 16:18:22,671 [INFO] Ambari Metrics Grafana .
> SUCCESS [ 2.458 s]
> 16:18:22,671 [INFO] Ambari Metrics Host Aggregator .
> SUCCESS [ 8.963 s]
> 16:18:22,671 [INFO] Ambari Metrics Assembly
> SUCCESS [ 57.413 s]
> 16:18:22,671 [INFO]
>
> 16:18:22,671 [INFO] BUILD SUCCESS
> 16:18:22,671 [INFO]
>
> 16:18:22,671 [INFO] Total time: 02:00 min
> 16:18:22,673 [INFO] Finished at: 2022-12-14T16:18:22+05:30
> {noformat}
> *As shown above, in my build environment, build time is reduced from 10
> minute to 2 minute.*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25819) Ambari Metrics build fails when using -Dbuild-rpm
[ https://issues.apache.org/jira/browse/AMBARI-25819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25819: --- Parent: (was: AMBARI-25799) Issue Type: Bug (was: Sub-task) > Ambari Metrics build fails when using -Dbuild-rpm > - > > Key: AMBARI-25819 > URL: https://issues.apache.org/jira/browse/AMBARI-25819 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2022-12-16-20-11-49-087.png > > > !image-2022-12-16-20-11-49-087.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25819) Ambari Metrics build fails when using -Dbuild-rpm
[ https://issues.apache.org/jira/browse/AMBARI-25819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25819: --- Epic Link: AMBARI-25792 > Ambari Metrics build fails when using -Dbuild-rpm > - > > Key: AMBARI-25819 > URL: https://issues.apache.org/jira/browse/AMBARI-25819 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2022-12-16-20-11-49-087.png > > > !image-2022-12-16-20-11-49-087.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25801) Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25801: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) Environment: Centos7 Ambari Metrics 3.0.0 was: Centos7 Ambari-2.8.0 > Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari > > > Key: AMBARI-25801 > URL: https://issues.apache.org/jira/browse/AMBARI-25801 > Project: Ambari > Issue Type: Task > Components: ambari-metrics > Environment: Centos7 > Ambari Metrics 3.0.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > Like the component version of BIGTOP > ' > Hbase-2.4.13 > Kafka-2.8.1 > Hadoop-3.3.4 > ' > We should also upgrade the above components to keep the versions consistent. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25821) Fixed syntax error that caused OOM in the ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25821: --- Parent: (was: AMBARI-25799) Issue Type: Bug (was: Sub-task) > Fixed syntax error that caused OOM in the ambari-metrics-collector > -- > > Key: AMBARI-25821 > URL: https://issues.apache.org/jira/browse/AMBARI-25821 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: screenshot-1.png, screenshot-2.png > > > The following code does not find a method StopHandler. > !screenshot-1.png! > This will cause the scheduled task of calculating and uploading data with an > interval of 60 seconds to fail. Here's the picture. > !screenshot-2.png! > Ambari-2.7 does not have this problem in the first place. The problem is > caused by the spin-off of the Ambari-Metrics sub-project from Ambari. > The reason is that ambari-metrics also relies on OS_check in ambari-commons. > After the subproject is split, ambari-commons module is not pulled over, so > the subproject ambari-metrics needs to remove the commons dependency. > However, there are omissions in this process leading to incomplete adaptation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25821) Fixed syntax error that caused OOM in the ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25821: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) > Fixed syntax error that caused OOM in the ambari-metrics-collector > -- > > Key: AMBARI-25821 > URL: https://issues.apache.org/jira/browse/AMBARI-25821 > Project: Ambari > Issue Type: Bug > Components: metrics > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > Attachments: screenshot-1.png, screenshot-2.png > > > The following code does not find a method StopHandler. > !screenshot-1.png! > This will cause the scheduled task of calculating and uploading data with an > interval of 60 seconds to fail. Here's the picture. > !screenshot-2.png! > Ambari-2.7 does not have this problem in the first place. The problem is > caused by the spin-off of the Ambari-Metrics sub-project from Ambari. > The reason is that ambari-metrics also relies on OS_check in ambari-commons. > After the subproject is split, ambari-commons module is not pulled over, so > the subproject ambari-metrics needs to remove the commons dependency. > However, there are omissions in this process leading to incomplete adaptation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25821) Fixed syntax error that caused OOM in the ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25821: --- Epic Link: AMBARI-25792 > Fixed syntax error that caused OOM in the ambari-metrics-collector > -- > > Key: AMBARI-25821 > URL: https://issues.apache.org/jira/browse/AMBARI-25821 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: screenshot-1.png, screenshot-2.png > > > The following code does not find a method StopHandler. > !screenshot-1.png! > This will cause the scheduled task of calculating and uploading data with an > interval of 60 seconds to fail. Here's the picture. > !screenshot-2.png! > Ambari-2.7 does not have this problem in the first place. The problem is > caused by the spin-off of the Ambari-Metrics sub-project from Ambari. > The reason is that ambari-metrics also relies on OS_check in ambari-commons. > After the subproject is split, ambari-commons module is not pulled over, so > the subproject ambari-metrics needs to remove the commons dependency. > However, there are omissions in this process leading to incomplete adaptation. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25801) Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25801: --- Parent: (was: AMBARI-25799) Issue Type: Task (was: Sub-task) > Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari > > > Key: AMBARI-25801 > URL: https://issues.apache.org/jira/browse/AMBARI-25801 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Like the component version of BIGTOP > ' > Hbase-2.4.13 > Kafka-2.8.1 > Hadoop-3.3.4 > ' > We should also upgrade the above components to keep the versions consistent. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25801) Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25801: --- Epic Link: AMBARI-25792 > Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari > > > Key: AMBARI-25801 > URL: https://issues.apache.org/jira/browse/AMBARI-25801 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Like the component version of BIGTOP > ' > Hbase-2.4.13 > Kafka-2.8.1 > Hadoop-3.3.4 > ' > We should also upgrade the above components to keep the versions consistent. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25822) Remove invalid relocations in pom.xml for ambari-metrics-common
[ https://issues.apache.org/jira/browse/AMBARI-25822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25822: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) > Remove invalid relocations in pom.xml for ambari-metrics-common > --- > > Key: AMBARI-25822 > URL: https://issues.apache.org/jira/browse/AMBARI-25822 > Project: Ambari > Issue Type: Bug > Components: metrics > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > Attachments: screenshot-1.png > > > The introduced class does not exist, so the following configurations need to > be removed as well. > https://github.com/apache/ambari-metrics/blob/86abdc4bfe19760b6a55a9104abf6c7dbbd45054/ambari-metrics-common/pom.xml#L70-L127 > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25822) Remove invalid relocations in pom.xml for ambari-metrics-common
[ https://issues.apache.org/jira/browse/AMBARI-25822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25822: --- Parent: (was: AMBARI-25799) Issue Type: Bug (was: Sub-task) > Remove invalid relocations in pom.xml for ambari-metrics-common > --- > > Key: AMBARI-25822 > URL: https://issues.apache.org/jira/browse/AMBARI-25822 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: screenshot-1.png > > > The introduced class does not exist, so the following configurations need to > be removed as well. > https://github.com/apache/ambari-metrics/blob/86abdc4bfe19760b6a55a9104abf6c7dbbd45054/ambari-metrics-common/pom.xml#L70-L127 > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25822) Remove invalid relocations in pom.xml for ambari-metrics-common
[ https://issues.apache.org/jira/browse/AMBARI-25822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25822: --- Epic Link: AMBARI-25792 > Remove invalid relocations in pom.xml for ambari-metrics-common > --- > > Key: AMBARI-25822 > URL: https://issues.apache.org/jira/browse/AMBARI-25822 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: screenshot-1.png > > > The introduced class does not exist, so the following configurations need to > be removed as well. > https://github.com/apache/ambari-metrics/blob/86abdc4bfe19760b6a55a9104abf6c7dbbd45054/ambari-metrics-common/pom.xml#L70-L127 > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25825) Adjust Ambari metrics dependency
[ https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25825: --- Epic Link: AMBARI-25792 > Adjust Ambari metrics dependency > > > Key: AMBARI-25825 > URL: https://issues.apache.org/jira/browse/AMBARI-25825 > Project: Ambari > Issue Type: Improvement > Components: metrics >Affects Versions: 2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > As discussed in following > https://github.com/apache/ambari-metrics/pull/79#issuecomment-1362638692 > I will > 1. Port BIGTOP-3872 to Ambari-Metrics. > 2. Add dependency phoenix-hbase-compat-2.4.1 for ambari-metrics-timeline. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25825) Adjust Ambari metrics dependency
[ https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25825: --- Parent: (was: AMBARI-25799) Issue Type: Improvement (was: Sub-task) > Adjust Ambari metrics dependency > > > Key: AMBARI-25825 > URL: https://issues.apache.org/jira/browse/AMBARI-25825 > Project: Ambari > Issue Type: Improvement > Components: metrics >Affects Versions: 2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > As discussed in following > https://github.com/apache/ambari-metrics/pull/79#issuecomment-1362638692 > I will > 1. Port BIGTOP-3872 to Ambari-Metrics. > 2. Add dependency phoenix-hbase-compat-2.4.1 for ambari-metrics-timeline. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25825) Adjust Ambari metrics dependency
[ https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25825: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) > Adjust Ambari metrics dependency > > > Key: AMBARI-25825 > URL: https://issues.apache.org/jira/browse/AMBARI-25825 > Project: Ambari > Issue Type: Improvement > Components: metrics >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > As discussed in following > https://github.com/apache/ambari-metrics/pull/79#issuecomment-1362638692 > I will > 1. Port BIGTOP-3872 to Ambari-Metrics. > 2. Add dependency phoenix-hbase-compat-2.4.1 for ambari-metrics-timeline. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25828) Switch class Metrics to KafkaYammerMetrics on Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25828: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) Environment: Centos7(x86_64) Ambari Metrics 3.0.0 was: Centos7(x86_64) Ambari-2.8 Ambari-Metrics-2.0 > Switch class Metrics to KafkaYammerMetrics on Ambari Metrics > > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Bug > Components: metrics > Environment: Centos7(x86_64) > Ambari Metrics 3.0.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > Attachments: image-2022-12-26-21-25-54-719.png > > > 1. As KAFKA-9106 > https://issues.apache.org/jira/browse/KAFKA-9106 > and > https://cwiki.apache.org/confluence/display/KAFKA/KIP-544%3A+Make+metrics+exposed+via+JMX+configurable > said. > Any code currently using will switch to using > com.yammer.metrics.Metrics.defaultRegistry()KafkaYammerMetrics.defaultRegistry() > This change started with kafka-2.6. > Reference: > !image-2022-12-26-21-25-54-719.png! > 2. This issue also fix NPE because of > https://issues.apache.org/jira/browse/AMBARI-24797. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25828) Switch class Metrics to KafkaYammerMetrics on Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25828: --- Epic Link: AMBARI-25792 > Switch class Metrics to KafkaYammerMetrics on Ambari Metrics > > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7(x86_64) > Ambari-2.8 > Ambari-Metrics-2.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2022-12-26-21-25-54-719.png > > > 1. As KAFKA-9106 > https://issues.apache.org/jira/browse/KAFKA-9106 > and > https://cwiki.apache.org/confluence/display/KAFKA/KIP-544%3A+Make+metrics+exposed+via+JMX+configurable > said. > Any code currently using will switch to using > com.yammer.metrics.Metrics.defaultRegistry()KafkaYammerMetrics.defaultRegistry() > This change started with kafka-2.6. > Reference: > !image-2022-12-26-21-25-54-719.png! > 2. This issue also fix NPE because of > https://issues.apache.org/jira/browse/AMBARI-24797. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25828) Switch class Metrics to KafkaYammerMetrics on Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25828: --- Parent: (was: AMBARI-25799) Issue Type: Bug (was: Sub-task) > Switch class Metrics to KafkaYammerMetrics on Ambari Metrics > > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Bug > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7(x86_64) > Ambari-2.8 > Ambari-Metrics-2.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2022-12-26-21-25-54-719.png > > > 1. As KAFKA-9106 > https://issues.apache.org/jira/browse/KAFKA-9106 > and > https://cwiki.apache.org/confluence/display/KAFKA/KIP-544%3A+Make+metrics+exposed+via+JMX+configurable > said. > Any code currently using will switch to using > com.yammer.metrics.Metrics.defaultRegistry()KafkaYammerMetrics.defaultRegistry() > This change started with kafka-2.6. > Reference: > !image-2022-12-26-21-25-54-719.png! > 2. This issue also fix NPE because of > https://issues.apache.org/jira/browse/AMBARI-24797. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25834) Fix syntax errors for ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25834: --- Parent: (was: AMBARI-25799) Issue Type: Bug (was: Sub-task) > Fix syntax errors for ambari-metrics-collector > -- > > Key: AMBARI-25834 > URL: https://issues.apache.org/jira/browse/AMBARI-25834 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-01-05-21-40-59-872.png > > > Fix the syntax errors shown in the image below. > !image-2023-01-05-21-40-59-872.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25834) Fix syntax errors for ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25834: --- Epic Link: AMBARI-25792 > Fix syntax errors for ambari-metrics-collector > -- > > Key: AMBARI-25834 > URL: https://issues.apache.org/jira/browse/AMBARI-25834 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-01-05-21-40-59-872.png > > > Fix the syntax errors shown in the image below. > !image-2023-01-05-21-40-59-872.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25834) Fix syntax errors for ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25834: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) Environment: Centos7 Ambari Metrics 3.0.0 was: Centos7 Ambari-2.8.0 > Fix syntax errors for ambari-metrics-collector > -- > > Key: AMBARI-25834 > URL: https://issues.apache.org/jira/browse/AMBARI-25834 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Centos7 > Ambari Metrics 3.0.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > Attachments: image-2023-01-05-21-40-59-872.png > > > Fix the syntax errors shown in the image below. > !image-2023-01-05-21-40-59-872.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25815) upgrade gson-2.2.2.jar to 2.9.0
[ https://issues.apache.org/jira/browse/AMBARI-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25815: --- Epic Link: AMBARI-25860 Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) > upgrade gson-2.2.2.jar to 2.9.0 > --- > > Key: AMBARI-25815 > URL: https://issues.apache.org/jira/browse/AMBARI-25815 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > |[CVE-2022-25647 > |http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25647]| > upgrade gson in ambari-metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
[ https://issues.apache.org/jira/browse/AMBARI-25840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25840: --- Epic Link: AMBARI-25860 (was: AMBARI-25792) Fix Version/s: ambari-metrics-3.0.0 (was: 2.8.0) Affects Version/s: (was: 2.8.0) Environment: Centos7 Ambari Metrics 3.0.0 was: Centos7 Ambari-2.8.0 > Optimized rpm packaging for the Ambari-Metric-Collector > --- > > Key: AMBARI-25840 > URL: https://issues.apache.org/jira/browse/AMBARI-25840 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics > Environment: Centos7 > Ambari Metrics 3.0.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > Attachments: image-2023-01-12-10-55-23-747.png > > > The hadoop and hbase versions of the ambari-metric-Collector are inconsistent > with the pom.xml. > We should get it from the hadoop and hbase tarball. > !image-2023-01-12-10-55-23-747.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
[ https://issues.apache.org/jira/browse/AMBARI-25840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25840: --- Parent: (was: AMBARI-25799) Issue Type: Improvement (was: Sub-task) > Optimized rpm packaging for the Ambari-Metric-Collector > --- > > Key: AMBARI-25840 > URL: https://issues.apache.org/jira/browse/AMBARI-25840 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-01-12-10-55-23-747.png > > > The hadoop and hbase versions of the ambari-metric-Collector are inconsistent > with the pom.xml. > We should get it from the hadoop and hbase tarball. > !image-2023-01-12-10-55-23-747.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
[ https://issues.apache.org/jira/browse/AMBARI-25840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25840: --- Epic Link: AMBARI-25792 > Optimized rpm packaging for the Ambari-Metric-Collector > --- > > Key: AMBARI-25840 > URL: https://issues.apache.org/jira/browse/AMBARI-25840 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-01-12-10-55-23-747.png > > > The hadoop and hbase versions of the ambari-metric-Collector are inconsistent > with the pom.xml. > We should get it from the hadoop and hbase tarball. > !image-2023-01-12-10-55-23-747.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25866) Fix an unit test failure on ambari-metrics-kafka-sink
[
https://issues.apache.org/jira/browse/AMBARI-25866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25866:
---
Epic Link: AMBARI-25860
Fix Version/s: ambari-metrics-3.0.0
> Fix an unit test failure on ambari-metrics-kafka-sink
> -
>
> Key: AMBARI-25866
> URL: https://issues.apache.org/jira/browse/AMBARI-25866
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Kengo Seki
>Assignee: Zhiguo Wu
>Priority: Major
> Labels: pull-request-available
> Fix For: ambari-metrics-3.0.0
>
>
> I tried to run unit tests on the release-2.0.0-rc0 branch and ran into the
> following error:
> {code}
> $ mvn test -f ambari-metrics-kafka-sink/pom.xml
> ...
> Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 1.519 sec <<<
> FAILURE! - in
> org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest
> testReporterStartStop(org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest)
> Time elapsed: 0.817 sec <<< FAILURE!
> java.lang.AssertionError:
> Expectation failure on verify:
> Metrics.defaultRegistry(): expected: 2, actual: 0
> at
> org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest.testReporterStartStop(KafkaTimelineMetricsReporterTest.java:102)
> testReporterStartStopHttps(org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest)
> Time elapsed: 0.022 sec <<< FAILURE!
> java.lang.AssertionError:
> Expectation failure on verify:
> Metrics.defaultRegistry(): expected: 2, actual: 0
> at
> org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest.testReporterStartStopHttps(KafkaTimelineMetricsReporterTest.java:131)
> testMetricsExclusionPolicy(org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest)
> Time elapsed: 0.021 sec <<< FAILURE!
> java.lang.AssertionError:
> Expectation failure on verify:
> Metrics.defaultRegistry(): expected: 2, actual: 0
> at
> org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest.testMetricsExclusionPolicy(KafkaTimelineMetricsReporterTest.java:151)
> Results :
> Failed tests:
> KafkaTimelineMetricsReporterTest.testMetricsExclusionPolicy:151
> Expectation failure on verify:
> Metrics.defaultRegistry(): expected: 2, actual: 0
> KafkaTimelineMetricsReporterTest.testReporterStartStop:102
> Expectation failure on verify:
> Metrics.defaultRegistry(): expected: 2, actual: 0
> KafkaTimelineMetricsReporterTest.testReporterStartStopHttps:131
> Expectation failure on verify:
> Metrics.defaultRegistry(): expected: 2, actual: 0
> Tests run: 5, Failures: 3, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4.238 s
> [INFO] Finished at: 2023-02-24T09:46:44+09:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on
> project ambari-metrics-kafka-sink: There are test failures.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25864) Fix an unit test failure on ambari-metrics-common
[
https://issues.apache.org/jira/browse/AMBARI-25864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25864:
---
Epic Link: AMBARI-25860
Fix Version/s: ambari-metrics-3.0.0
> Fix an unit test failure on ambari-metrics-common
> -
>
> Key: AMBARI-25864
> URL: https://issues.apache.org/jira/browse/AMBARI-25864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Labels: pull-request-available
> Fix For: ambari-metrics-3.0.0
>
>
> I tried to run unit tests on the release-2.0.0-rc0 branch and ran into the
> following error:
> {code}
> $ mvn test -f ambari-metrics-common/pom.xml
> ...
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<<
> FAILURE! - in
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest
> testEmbeddedModeCollectorZK(org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest)
> Time elapsed: 0.007 sec <<< ERROR!
> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest.testEmbeddedModeCollectorZK(MetricCollectorHATest.java:88)
> Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest.testEmbeddedModeCollectorZK(MetricCollectorHATest.java:88)
> Results :
> Tests in error:
> MetricCollectorHATest.testEmbeddedModeCollectorZK:88 » NoClassDefFound
> org/slf...
> Tests run: 20, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 35.496 s
> [INFO] Finished at: 2023-02-24T09:54:00+09:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on
> project ambari-metrics-common: There are test failures.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25865) Fix an unit test failure on ambari-metrics-host-monitoring
[
https://issues.apache.org/jira/browse/AMBARI-25865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25865:
---
Epic Link: AMBARI-25860
Fix Version/s: ambari-metrics-3.0.0
> Fix an unit test failure on ambari-metrics-host-monitoring
> --
>
> Key: AMBARI-25865
> URL: https://issues.apache.org/jira/browse/AMBARI-25865
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Kengo Seki
>Assignee: Kengo Seki
>Priority: Major
> Labels: pull-request-available
> Fix For: ambari-metrics-3.0.0
>
>
> I tried to run unit tests on the release-2.0.0-rc0 branch and ran into the
> following error:
> {code}
> $ mvn test -f ambari-metrics-host-monitoring/pom.xml
> ...
> [INFO] --- exec-maven-plugin:1.2.1:exec (python-test) @
> ambari-metrics-host-monitoring ---
> Running tests
> No handlers could be found for logger "root"
> Traceback (most recent call last):
> File "unitTests.py", line 137, in
> sys.exit(main())
> File "unitTests.py", line 106, in main
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/sekikn/repos/ambari-metrics/ambari-metrics-host-monitoring/src/test/python/core/TestMetricCollector.py",
> line 24, in
> from core.application_metric_map import ApplicationMetricMap
> File
> "/home/sekikn/repos/ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/__init__.py",
> line 29, in
> for dir in os.walk(path).next()[1]:
> StopIteration
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.126 s
> [INFO] Finished at: 2023-02-24T09:45:36+09:00
> [INFO]
>
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (python-test) on project ambari-metrics-host-monitoring: Command execution
> failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25867) Introduce CI build for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25867: --- Epic Link: AMBARI-25860 Fix Version/s: ambari-metrics-3.0.0 > Introduce CI build for Ambari Metrics > - > > Key: AMBARI-25867 > URL: https://issues.apache.org/jira/browse/AMBARI-25867 > Project: Ambari > Issue Type: Improvement >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > It would be better if we had CI build for Ambari Metrics so that we could > notice unit test failures before merging PR. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25867) Introduce CI build for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25867: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Introduce CI build for Ambari Metrics > - > > Key: AMBARI-25867 > URL: https://issues.apache.org/jira/browse/AMBARI-25867 > Project: Ambari > Issue Type: Improvement >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > It would be better if we had CI build for Ambari Metrics so that we could > notice unit test failures before merging PR. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25859) Correct Ambari Metrics version parsing logic
[
https://issues.apache.org/jira/browse/AMBARI-25859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25859:
---
Epic Link: AMBARI-25860
Fix Version/s: ambari-metrics-3.0.0
> Correct Ambari Metrics version parsing logic
>
>
> Key: AMBARI-25859
> URL: https://issues.apache.org/jira/browse/AMBARI-25859
> Project: Ambari
> Issue Type: Bug
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Labels: pull-request-available
> Fix For: ambari-metrics-3.0.0
>
> Attachments: image-2023-02-22-16-49-06-587.png
>
>
> Currently Ambari Metrics uses *2.0.0.0-SNAPSHOT* as its version number, and
> the regex
> {*}^([0-9]{+})\.([0-9]{+})\.([0-9]{+})\.([0-9]{+})((\.|-)(([0-9]+)|(SNAPSHOT)|(techwin)).)?{*}*
> and get *$7* as its release version number, but when we remove *SNAPSHOT*
> suffix, the parse will return empty value cause build rpm package fails.
>
> If I understand it correctly, the old logic is trying to get number(or word
> *SNAPSHOT* or {*}techwin{*}) after the symbol "-" as its release version, so
> I'd like to change the version format to *x.y.z-p* where *x.y.z* means ambari
> version and *p* means release(or patch) version.(if the branch is under
> development, we can use *SNAPSHOT* for {*}p{*})
>
> Like this:
> !image-2023-02-22-16-49-06-587.png!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25875) Use separate property for release version for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25875: --- Epic Link: AMBARI-25860 Fix Version/s: ambari-metrics-3.0.0 > Use separate property for release version for Ambari Metrics > > > Key: AMBARI-25875 > URL: https://issues.apache.org/jira/browse/AMBARI-25875 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for > release version, but this may confused for people, so I'd like to split *p* > into a separate property -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25876) Define next version number for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25876: --- Fix Version/s: ambari-metrics-3.0.0 > Define next version number for Ambari Metrics > - > > Key: AMBARI-25876 > URL: https://issues.apache.org/jira/browse/AMBARI-25876 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > Fix For: ambari-metrics-3.0.0 > > > When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, > and the version number contains 5 digits, x.x.x.x.x, which also contains the > release version number. > If we merge AMBARI-25875, then the version number will only be 3 digits and > will no longer contain the release version number, I think this is a big > change for identifying versions, so I prefer to upgrade the major version and > set the next version to 3.0.0 for ambari-metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25860) Ambari Metrics 3.0.0 Releases
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25860: --- Labels: 3.0.0 Ambari Metrics Releases (was: ) > Ambari Metrics 3.0.0 Releases > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.8.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: 3.0.0, Ambari, Metrics, Releases > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25876) Define next version number for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25876: --- Epic Link: AMBARI-25860 > Define next version number for Ambari Metrics > - > > Key: AMBARI-25876 > URL: https://issues.apache.org/jira/browse/AMBARI-25876 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > > When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, > and the version number contains 5 digits, x.x.x.x.x, which also contains the > release version number. > If we merge AMBARI-25875, then the version number will only be 3 digits and > will no longer contain the release version number, I think this is a big > change for identifying versions, so I prefer to upgrade the major version and > set the next version to 3.0.0 for ambari-metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25860) Ambari Metrics 3.0.0 Releases
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25860: --- Epic Name: Ambari Metrics 3.0.0 Releases > Ambari Metrics 3.0.0 Releases > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.8.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25860) Ambari Metrics 3.0.0 Releases
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25860: --- Labels: (was: 3.0.0 Ambari Metrics Releases) > Ambari Metrics 3.0.0 Releases > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.8.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25860) Ambari Metrics 2.0.0 Releases
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25860: --- Fix Version/s: 2.8.0 Affects Version/s: 2.8.0 Description: (was: Commits related to Ambari Metrics 2.0.0 Releases will be linked here) Issue Type: Epic (was: Task) Summary: Ambari Metrics 2.0.0 Releases (was: Release Ambari Metrics 2.0.0) > Ambari Metrics 2.0.0 Releases > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.8.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25860) Ambari Metrics 3.0.0 Releases
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25860: --- Summary: Ambari Metrics 3.0.0 Releases (was: Ambari Metrics 2.0.0 Releases) > Ambari Metrics 3.0.0 Releases > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.8.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25879) ambari server hang when test kerberos clients
caijialiang created AMBARI-25879: Summary: ambari server hang when test kerberos clients Key: AMBARI-25879 URL: https://issues.apache.org/jira/browse/AMBARI-25879 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.8.0 Reporter: caijialiang Attachments: ambari_hang.png ambari server hang when test kerberos clients! after restart the ambari server,it showed test failed . i just click test client again , it test passed. so all kerberos are right ,something wrong in ambari server. !ambari_hang.png! these are some log in ambari server 2023-03-01 12:13:46,408 ERROR [agent-command-publisher-2] AgentCommandsPublisher:115 - Exception on sendAgentCommand java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:552) at java.lang.Long.valueOf(Long.java:803) at org.apache.ambari.server.events.publishers.AgentCommandsPublisher.lambda$null$0(AgentCommandsPublisher.java:110) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at com.google.common.collect.CollectSpliterators$1.lambda$forEachRemaining$1(CollectSpliterators.java:116) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at com.google.common.collect.CollectSpliterators$1.forEachRemaining(CollectSpliterators.java:116) at com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.lambda$forEachRemaining$1(CollectSpliterators.java:247) at java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1696) at com.google.common.collect.CollectSpliterators$1FlatMapSpliterator.forEachRemaining(CollectSpliterators.java:247) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:291) at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) 2023-03-01 12:13:59,599 INFO [ambari-client-thread-27] RoleGraph:175 - Detecting cycle graphs 2023-03-01 12:13:59,600 INFO [ambari-client-thread-27] RoleGraph:176 - Graph: (KERBEROS_CLIENT, CUSTOM_COMMAND, 0) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25876) Define next version number for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki resolved AMBARI-25876. - Resolution: Fixed > Define next version number for Ambari Metrics > - > > Key: AMBARI-25876 > URL: https://issues.apache.org/jira/browse/AMBARI-25876 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > > When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, > and the version number contains 5 digits, x.x.x.x.x, which also contains the > release version number. > If we merge AMBARI-25875, then the version number will only be 3 digits and > will no longer contain the release version number, I think this is a big > change for identifying versions, so I prefer to upgrade the major version and > set the next version to 3.0.0 for ambari-metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25875) Use separate property for release version for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kengo Seki resolved AMBARI-25875. - Resolution: Fixed > Use separate property for release version for Ambari Metrics > > > Key: AMBARI-25875 > URL: https://issues.apache.org/jira/browse/AMBARI-25875 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > > In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for > release version, but this may confused for people, so I'd like to split *p* > into a separate property -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
