-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMBARI-26131:Fix ambari-metrics-collector service check failed and resolve jar conflict problem #131
Conversation
2.upgrade commons-io to 2.8.0 3.upgrade guava to 32.1.1-jre 4.upgrade kafka to 2.8.2 5.upgrade zookeeper to 3.7.2 6.upgrade hbase to 2.4.17 7.upgrade hadoop to 3.3.6 8.add missing jar sqlline
2.modify download url
@brahmareddybattula @kevinw66 @virajjasani Hi guys,could somebody help review this pr? |
Nice one, this looks good. For those exclusions that you commented, we can remove them. |
+1, @JiaLiangC any review from your side? |
@virajjasani Sorry for the late reply. It's strange that I didn't receive any email notifications for Ambari Metrics PRs or mentions. This PR corrects the download URLs for Hadoop binaries, etc. Excluding the Hadoop and HBase dependencies from Phoenix and explicitly declaring them is indeed more elegant. LGTM +1 |
I am not sure what release version we need to use while closing Jira related to metrics repo. |
Indeed, it's difficult to determine the version in which the issue will be resolved. Ideally, Ambari Metrics should maintain version consistency with Ambari for better management, but Metrics has already released version 3.0... What do you think about 3.1? |
Yes I was thinking about the same. It's time to release 3.1. These are some of the good fixes that we should release. |
@@ -103,7 +103,6 @@ | |||
<dependency> | |||
<groupId>com.google.guava</groupId> | |||
<artifactId>guava</artifactId> | |||
<version>28.0-jre</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would be good to provide a version here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the parent pom's guava version should be used, so I deleted the separate version in here
@@ -141,7 +141,6 @@ limitations under the License. | |||
<dependency> | |||
<groupId>com.google.guava</groupId> | |||
<artifactId>guava</artifactId> | |||
<version>18.0</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add a version here as well ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as the previous comment
<hbase.folder>hbase-2.4.17</hbase.folder> | ||
<hadoop.tar>https://archive.apache.org/dist/hadoop/common/hadoop-3.3.6/hadoop-3.3.6.tar.gz</hadoop.tar> | ||
<hadoop.folder>hadoop-3.3.6</hadoop.folder> | ||
<hadoop.version>3.3.6</hadoop.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we have the hadoop version in sync with ambari where it is 3.3.4 currently ?
or bump up the version in ambari as well ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one, I think we should bump in ambari also.
@xijunmu CI has failed for this. Can you check and update? |
@sandeep318kumar I checked the code and found that the CI failure was not caused by this PR It is caused by some Python libraries ...... [INFO] --- exec:1.2.1:exec (python-test) @ ambari-metrics-host-monitoring --- ======================================================================
|
@sandeep318kumar nice work! |
@xijunmu My PR has been merged. Can you rebase your PR? |
What changes were proposed in this pull request?
After ambari-metrics-collector installed, i find the service check is failed. So i check the service port 6188 on host. The port is listened but access the url is failed return 500 (http://x.x.x.x:6188/ws/v1/timeline/metrics/livenodes)
Finally i find warn log about ambari-metrics-collector.It seems to be caused by jar conflict
At the same time, I upgraded some jar versions:
to solve the CVE problem:
1.upgrade commons-io to 2.8.0
2.upgrade guava to 32.1.1-jre
adapt to bigtop3 and modify tar.gz download url:
1.upgrade kafka to 2.8.2
2.upgrade zookeeper to 3.7.2
3.upgrade hbase to 2.4.17
4.upgrade hadoop to 3.3.6
5.upgrade phoenix to 2.4-5.1.3
add missing jar:
1.sqlline
How was this patch tested?
1.build ambari-metrics
mvn clean package -Dbuild-rpm -Drat.skip=true -DskipTests -Dmaven.test.skip=true
2.install ambari-metrics