[jira] [Resolved] (AMBARI-25820) Update Spark and Flink versions to be consistent with BigTop
[ https://issues.apache.org/jira/browse/AMBARI-25820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25820. Resolution: Fixed > Update Spark and Flink versions to be consistent with BigTop > > > Key: AMBARI-25820 > URL: https://issues.apache.org/jira/browse/AMBARI-25820 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 > Bigtop-3.2.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Refer to follow issue description. > https://issues.apache.org/jira/browse/BIGTOP-3888 > https://issues.apache.org/jira/browse/BIGTOP-3874 -- 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-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 resolved AMBARI-25828. Resolution: Fixed > Switch class Metrics to KafkaYammerMetrics on Ambari Metrics > > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Sub-task > 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: --- Summary: Switch class Metrics to KafkaYammerMetrics on Ambari Metrics (was: Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6) > Switch class Metrics to KafkaYammerMetrics on Ambari Metrics > > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Sub-task > 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] [Resolved] (AMBARI-25702) Release ambari-2.7.7
[ https://issues.apache.org/jira/browse/AMBARI-25702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved AMBARI-25702. --- Resolution: Fixed Closing the epic as 2.7.7 is released. > Release ambari-2.7.7 > > > Key: AMBARI-25702 > URL: https://issues.apache.org/jira/browse/AMBARI-25702 > Project: Ambari > Issue Type: Epic > Components: ambari-admin, ambari-agent, ambari-server, > ambari-upgrade, ambari-web >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > > Roadmap for 2.7.7 release > * CVE fixes > * Bug fixes (Mainly critical/blocker) > * New stack which can support upgrade/rollback > > Please feel free to add and participate mailing discussion[1]. > 1. https://lists.apache.org/thread/m77lhzo0njr2dhoock5twtm0c19j2py8 -- 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-25703) Fix all possible CVE's on branch-2.7
[ https://issues.apache.org/jira/browse/AMBARI-25703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved AMBARI-25703. --- Resolution: Fixed Closing this feature as 2.7.7 is released. > Fix all possible CVE's on branch-2.7 > > > Key: AMBARI-25703 > URL: https://issues.apache.org/jira/browse/AMBARI-25703 > Project: Ambari > Issue Type: New Feature >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > > Fix all possible CVE's on branch-2.7 -- 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-25725) Upgrade bootstrap.min.js to v5.2.0
[ https://issues.apache.org/jira/browse/AMBARI-25725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved AMBARI-25725. --- Fix Version/s: 2.8.0 2.7.7 Resolution: Fixed Committed to branch-2.7 also. thanks [~ananysin] for your contribution. > Upgrade bootstrap.min.js to v5.2.0 > -- > > Key: AMBARI-25725 > URL: https://issues.apache.org/jira/browse/AMBARI-25725 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Fix For: 2.8.0, 2.7.7 > > Time Spent: 1h 50m > Remaining Estimate: 0h > -- 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-25813) upgrade httpclient-4.5.2.jar to 4.5.13
[ https://issues.apache.org/jira/browse/AMBARI-25813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652044#comment-17652044 ] Brahma Reddy Battula commented on AMBARI-25813: --- HI [~ananysin] , Are you planning to handle this jira.? > upgrade httpclient-4.5.2.jar to 4.5.13 > -- > > Key: AMBARI-25813 > URL: https://issues.apache.org/jira/browse/AMBARI-25813 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > > |[CVE-2020-13956 > |http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-13956]| > |CWE-22| -- 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-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:comment-tabpanel&focusedCommentId=17652042#comment-17652042 ] Brahma Reddy Battula commented on AMBARI-25815: --- [~ananysin] are you planning to raise the PR for this.? > 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 > > |[CVE-2022-25647 > |http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25647]| -- 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-25814) upgrade commons-io-2.4.jar to 2.8.0
[ https://issues.apache.org/jira/browse/AMBARI-25814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652043#comment-17652043 ] Brahma Reddy Battula commented on AMBARI-25814: --- HI [~ananysin] Are you planning to raise the PR for this.? > upgrade commons-io-2.4.jar to 2.8.0 > --- > > Key: AMBARI-25814 > URL: https://issues.apache.org/jira/browse/AMBARI-25814 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > > |[CVE-2021-29425|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29425]| -- 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-25812) upgrade jackson-databind-2.10.0.jar to 2.13.2 to resolve CVEs
[ https://issues.apache.org/jira/browse/AMBARI-25812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652041#comment-17652041 ] Brahma Reddy Battula commented on AMBARI-25812: --- [~ananysin] are you planning to raise the PR for this.? > upgrade jackson-databind-2.10.0.jar to 2.13.2 to resolve CVEs > -- > > Key: AMBARI-25812 > URL: https://issues.apache.org/jira/browse/AMBARI-25812 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > > CVE-2020-25649 > CVE-2020-36518 -- 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-25818) Set default value for jdk.version in ambari-serviceadvisor
[
https://issues.apache.org/jira/browse/AMBARI-25818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula updated AMBARI-25818:
--
Fix Version/s: 2.7.8
Resolution: Fixed
Status: Resolved (was: Patch Available)
[~arshad.mohammad] thanks for raising for branch-2.7 also. Committed to
branch-2.7 also.
> 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, 2.7.8
>
> Time Spent: 1h
> 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
[jira] [Updated] (AMBARI-25817) Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test failures
[
https://issues.apache.org/jira/browse/AMBARI-25817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula updated AMBARI-25817:
--
Fix Version/s: 2.8.0
> Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test
> failures
> ---
>
> Key: AMBARI-25817
> URL: https://issues.apache.org/jira/browse/AMBARI-25817
> Project: Ambari
> Issue Type: Bug
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> FAILURE! - in org.apache.ambari.server.orm.db.DDLTests in testVerifyMySQL and
> testCompareMySQL
> {code:java}
> [ERROR] testVerifyMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.054 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> [ERROR] testCompareMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.047 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> {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] [Comment Edited] (AMBARI-25817) Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test failures
[
https://issues.apache.org/jira/browse/AMBARI-25817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652037#comment-17652037
]
Brahma Reddy Battula edited comment on AMBARI-25817 at 12/26/22 5:49 PM:
-
Committed to trunk. [~hmaurya] thanks for your contribution. are you planning
to provide patch for branch-2.7 also.?
was (Author: brahmareddy):
Committed to trunk. [~hmaurya] thanks for your contribution.
> Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test
> failures
> ---
>
> Key: AMBARI-25817
> URL: https://issues.apache.org/jira/browse/AMBARI-25817
> Project: Ambari
> Issue Type: Bug
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> FAILURE! - in org.apache.ambari.server.orm.db.DDLTests in testVerifyMySQL and
> testCompareMySQL
> {code:java}
> [ERROR] testVerifyMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.054 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> [ERROR] testCompareMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.047 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> {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] [Commented] (AMBARI-25817) Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test failures
[
https://issues.apache.org/jira/browse/AMBARI-25817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652037#comment-17652037
]
Brahma Reddy Battula commented on AMBARI-25817:
---
Committed to trunk. [~hmaurya] thanks for your contribution.
> Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test
> failures
> ---
>
> Key: AMBARI-25817
> URL: https://issues.apache.org/jira/browse/AMBARI-25817
> Project: Ambari
> Issue Type: Bug
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> FAILURE! - in org.apache.ambari.server.orm.db.DDLTests in testVerifyMySQL and
> testCompareMySQL
> {code:java}
> [ERROR] testVerifyMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.054 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> [ERROR] testCompareMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.047 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> {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-25828) Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25828: External issue ID: KAFKA-9106 > Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6 > -- > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Sub-task > 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) Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25828: Labels: pull-request-available (was: ) > Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6 > -- > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Sub-task > 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) Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25828: Description: 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. was: 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! > Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6 > -- > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Sub-task > 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 > 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] [Assigned] (AMBARI-25828) Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25828: --- Assignee: Yu Hou > Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6 > -- > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Sub-task > 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 > Fix For: 2.8.0 > > Attachments: image-2022-12-26-21-25-54-719.png > > > 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! -- 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-25828) Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6
Yu Hou created AMBARI-25828: --- Summary: Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6 Key: AMBARI-25828 URL: https://issues.apache.org/jira/browse/AMBARI-25828 Project: Ambari Issue Type: Sub-task Components: metrics Affects Versions: 2.8.0 Environment: Centos7(x86_64) Ambari-2.8 Ambari-Metrics-2.0 Reporter: Yu Hou Fix For: 2.8.0 Attachments: image-2022-12-26-21-25-54-719.png 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! -- 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
