[jira] [Created] (AMBARI-25825) Port BIGTOP-3872 to fix Ambari-Metrics

2022-12-22 Thread Yu Hou (Jira)
Yu Hou created AMBARI-25825:
---

 Summary: Port BIGTOP-3872 to fix Ambari-Metrics
 Key: AMBARI-25825
 URL: https://issues.apache.org/jira/browse/AMBARI-25825
 Project: Ambari
  Issue Type: Sub-task
  Components: metrics
Affects Versions: 2.8.0
Reporter: Yu Hou
 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] [Assigned] (AMBARI-25825) Port BIGTOP-3872 to fix Ambari-Metrics

2022-12-22 Thread Yu Hou (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yu Hou reassigned AMBARI-25825:
---

Assignee: Yu Hou

> Port BIGTOP-3872 to fix Ambari-Metrics
> --
>
> Key: AMBARI-25825
> URL: https://issues.apache.org/jira/browse/AMBARI-25825
> Project: Ambari
>  Issue Type: Sub-task
>  Components: metrics
>Affects Versions: 2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> 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) Port BIGTOP-3872 to fix Ambari-Metrics

2022-12-22 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-25825:

Labels: pull-request-available  (was: )

> Port BIGTOP-3872 to fix Ambari-Metrics
> --
>
> Key: AMBARI-25825
> URL: https://issues.apache.org/jira/browse/AMBARI-25825
> Project: Ambari
>  Issue Type: Sub-task
>  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 for Ambari-Metrics

2022-12-22 Thread Yu Hou (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yu Hou updated AMBARI-25825:

Summary: Adjust Ambari metrics dependency for Ambari-Metrics  (was: Port 
BIGTOP-3872 to fix Ambari-Metrics)

> Adjust Ambari metrics dependency for Ambari-Metrics
> ---
>
> Key: AMBARI-25825
> URL: https://issues.apache.org/jira/browse/AMBARI-25825
> Project: Ambari
>  Issue Type: Sub-task
>  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

2022-12-22 Thread Yu Hou (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yu Hou updated AMBARI-25825:

Summary: Adjust Ambari metrics dependency  (was: Adjust Ambari metrics 
dependency for Ambari-Metrics)

> Adjust Ambari metrics dependency
> 
>
> Key: AMBARI-25825
> URL: https://issues.apache.org/jira/browse/AMBARI-25825
> Project: Ambari
>  Issue Type: Sub-task
>  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] [Resolved] (AMBARI-25821) Fixed syntax error that caused OOM in the ambari-metrics-collector

2022-12-22 Thread Zhiguo Wu (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiguo Wu resolved AMBARI-25821.

Resolution: Fixed

> 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: Sub-task
>  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] [Resolved] (AMBARI-25822) Remove invalid relocations in pom.xml for ambari-metrics-common

2022-12-22 Thread Zhiguo Wu (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiguo Wu resolved AMBARI-25822.

Resolution: Fixed

> 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: Sub-task
>  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] [Resolved] (AMBARI-25801) Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari

2022-12-22 Thread Zhiguo Wu (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiguo Wu resolved AMBARI-25801.

Resolution: Fixed

> 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: Sub-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] [Resolved] (AMBARI-25825) Adjust Ambari metrics dependency

2022-12-22 Thread Zhiguo Wu (Jira)


 [ 
https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhiguo Wu resolved AMBARI-25825.

Resolution: Fixed

> Adjust Ambari metrics dependency
> 
>
> Key: AMBARI-25825
> URL: https://issues.apache.org/jira/browse/AMBARI-25825
> Project: Ambari
>  Issue Type: Sub-task
>  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] [Commented] (AMBARI-25818) Set default value for jdk.version in ambari-serviceadvisor

2022-12-22 Thread Mohammad Arshad (Jira)


[ 
https://issues.apache.org/jira/browse/AMBARI-25818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651359#comment-17651359
 ] 

Mohammad Arshad commented on AMBARI-25818:
--

This bug is not directly applicable to branch-2.7
But I see another problem there, ambari-serviceadviser is using java 1.7 but 
other modules are using java 1.8. 
I think this should be improved. Set the java version 1.8 for 
ambari-serviceadviser module also. Raised the PR 
https://github.com/apache/ambari/pull/3618



> Set default value for jdk.version in ambari-serviceadvisor
> --
>
> Key: AMBARI-25818
> URL: https://issues.apache.org/jira/browse/AMBARI-25818
> Project: Ambari
>  Issue Type: Bug
>  Components: service-advisor
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 3.0.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> import the ambari trunk into intellij
> try to run any test case. 
> test case run fails with following error
> {noformat}
> java: invalid target release: 17
> Module ambari-serviceadvisor SDK 1.8 is not compatible with the source 
> version 17.
> Upgrade Module SDK in project settings to 17 or higher. Open project settings.
> {noformat}
> This is because for module ambari-serviceadvisor language level got set 
> wrongly to 17.
> Setting default  value for jdk.version in ambari-serviceadvisor solves this 
> problem.



--
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