[jira] [Created] (AMBARI-26133) Add RockyLinux-9 support
Yu Hou created AMBARI-26133: --- Summary: Add RockyLinux-9 support Key: AMBARI-26133 URL: https://issues.apache.org/jira/browse/AMBARI-26133 Project: Ambari Issue Type: Task Reporter: Yu Hou -- 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-26133) Add RockyLinux-9 support
[ https://issues.apache.org/jira/browse/AMBARI-26133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-26133: --- Assignee: Yu Hou > Add RockyLinux-9 support > > > Key: AMBARI-26133 > URL: https://issues.apache.org/jira/browse/AMBARI-26133 > Project: Ambari > Issue Type: Task >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > -- 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-26126) Add openEuler-22.03 support
[ https://issues.apache.org/jira/browse/AMBARI-26126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-26126: --- Assignee: Yu Hou > Add openEuler-22.03 support > --- > > Key: AMBARI-26126 > URL: https://issues.apache.org/jira/browse/AMBARI-26126 > Project: Ambari > Issue Type: Task >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Time Spent: 0.5h > 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] [Created] (AMBARI-26125) Fix rpm packaging errors for ambari-web and ambari-views
Yu Hou created AMBARI-26125: --- Summary: Fix rpm packaging errors for ambari-web and ambari-views Key: AMBARI-26125 URL: https://issues.apache.org/jira/browse/AMBARI-26125 Project: Ambari Issue Type: Task Reporter: Yu Hou Attachments: image-2024-09-05-17-21-25-581.png !image-2024-09-05-17-21-25-581.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-25894) Missing file service_advisor.py in some serivces
[ https://issues.apache.org/jira/browse/AMBARI-25894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou resolved AMBARI-25894. - Resolution: Resolved > Missing file service_advisor.py in some serivces > - > > Key: AMBARI-25894 > URL: https://issues.apache.org/jira/browse/AMBARI-25894 > Project: Ambari > Issue Type: Task >Reporter: Lei Yao >Assignee: Lei Yao >Priority: Major > Fix For: trunk > > Time Spent: 1h 10m > Remaining Estimate: 0h > > See AMBARI-19090 > Stack advisor should be broken into service advisor per service > In bigtop 3.20 stack, we can add hdfs/yarn/zookeeper service advisor and > delete BIGTOP/3.2.0/services/stack_advisor.py -- 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-25863) Fix a problem where the 'supported-refresh-commands' Element in configuration files for service was invalided
[ https://issues.apache.org/jira/browse/AMBARI-25863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou resolved AMBARI-25863. - Resolution: Resolved > Fix a problem where the 'supported-refresh-commands' Element in configuration > files for service was invalided > - > > Key: AMBARI-25863 > URL: https://issues.apache.org/jira/browse/AMBARI-25863 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Environment: Centos7(x86_64) > Ambari-2.8.0 > Bigtop-3.2.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Attachments: image-2023-02-23-21-53-04-918.png, > image-2023-02-23-21-56-07-440.png, image-2023-02-23-21-58-31-071.png > > Time Spent: 1h > Remaining Estimate: 0h > > As https://issues.apache.org/jira/browse/AMBARI-21406 > describes，'supported-refresh-commands' can Refresh configurations without > restart command. > But it has a few bugs that cause the 'supported-refresh-commands' tags to > fail, as shown below, > !image-2023-02-23-21-53-04-918.png! > which they should be to stay consistent with the rest. > !image-2023-02-23-21-56-07-440.png! > How was this patch tested? > !image-2023-02-23-21-58-31-071.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-25775) Failed to compile Ambari-Infra because of invalid url
[
https://issues.apache.org/jira/browse/AMBARI-25775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou resolved AMBARI-25775.
-
Resolution: Resolved
> Failed to compile Ambari-Infra because of invalid url
> -
>
> Key: AMBARI-25775
> URL: https://issues.apache.org/jira/browse/AMBARI-25775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
> Environment: Centos7
> Ambari-infra-2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-11-04-10-05-46-029.png
>
>
> http://central.maven.org/maven2 has been unable to access
> !image-2022-11-04-10-05-46-029.png!
> {code}
> kage/code/ambari-infra/ambari-infra-solr-client/target/migrate/lucene-core-6.6.2.jar
> [INFO]
>
> [INFO] Reactor Summary for ambari-infra 3.0.0.0-SNAPSHOT:
> [INFO]
> [INFO] ambari-infra ... SUCCESS [ 6.914
> s]
> [INFO] Ambari Infra Solr Client ... FAILURE [ 7.090
> s]
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Infra Manager ... SKIPPED
> [INFO] Ambari Infra Assembly .. SKIPPED
> [INFO] Ambari Infra Manager Integration Tests . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 14.279 s
> [INFO] Finished at: 2022-11-04T10:04:29+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project
> ambari-infra-solr-client: An Ant BuildException has occured: The following
> error occurred while executing this line:
> [ERROR] /opt/package/code/ambari-infra/ambari-infra-solr-client/build.xml:39:
> java.net.UnknownHostException: central.maven.org
> [ERROR] around Ant part .. @ 4:28 in
> /opt/package/code/ambari-infra/ambari-infra-solr-client/target/antrun/build-main.xml:
> Unknown host central.maven.org
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :ambari-infra-solr-client
> make: *** [rpm] Error 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] [Resolved] (AMBARI-25946) Fix CI/CD error for Ambari WebUI Tests
[ https://issues.apache.org/jira/browse/AMBARI-25946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou resolved AMBARI-25946. - Resolution: Resolved > Fix CI/CD error for Ambari WebUI Tests > -- > > Key: AMBARI-25946 > URL: https://issues.apache.org/jira/browse/AMBARI-25946 > Project: Ambari > Issue Type: Bug > Environment: Jenkins CI/CD >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Attachments: image-2023-05-22-11-25-18-637.png > > Time Spent: 50m > Remaining Estimate: 0h > > As [TEZ-4492 : Approach 1 : Update Bower Registry to a different mirror by > AnmolSun · Pull Request #284 · apache/tez > (github.com)|https://github.com/apache/tez/pull/284] > said, > we can solve problems in the same way. > > > !image-2023-05-22-11-25-18-637.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] [Assigned] (AMBARI-25946) Fix CI/CD error for Ambari WebUI Tests
[ https://issues.apache.org/jira/browse/AMBARI-25946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25946: --- Assignee: Yu Hou > Fix CI/CD error for Ambari WebUI Tests > -- > > Key: AMBARI-25946 > URL: https://issues.apache.org/jira/browse/AMBARI-25946 > Project: Ambari > Issue Type: Bug > Environment: Jenkins CI/CD >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Attachments: image-2023-05-22-11-25-18-637.png > > Time Spent: 20m > Remaining Estimate: 0h > > As [TEZ-4492 : Approach 1 : Update Bower Registry to a different mirror by > AnmolSun · Pull Request #284 · apache/tez > (github.com)|https://github.com/apache/tez/pull/284] > said, > we can solve problems in the same way. > > > !image-2023-05-22-11-25-18-637.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-25946) Fix CI/CD error for Ambari WebUI Tests
[ https://issues.apache.org/jira/browse/AMBARI-25946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25946: Description: As [TEZ-4492 : Approach 1 : Update Bower Registry to a different mirror by AnmolSun · Pull Request #284 · apache/tez (github.com)|https://github.com/apache/tez/pull/284] said, we can solve problems in the same way. !image-2023-05-22-11-25-18-637.png! was: !image-2023-05-22-11-25-18-637.png! > Fix CI/CD error for Ambari WebUI Tests > -- > > Key: AMBARI-25946 > URL: https://issues.apache.org/jira/browse/AMBARI-25946 > Project: Ambari > Issue Type: Bug > Environment: Jenkins CI/CD >Reporter: Yu Hou >Priority: Major > Attachments: image-2023-05-22-11-25-18-637.png > > Time Spent: 10m > Remaining Estimate: 0h > > As [TEZ-4492 : Approach 1 : Update Bower Registry to a different mirror by > AnmolSun · Pull Request #284 · apache/tez > (github.com)|https://github.com/apache/tez/pull/284] > said, > we can solve problems in the same way. > > > !image-2023-05-22-11-25-18-637.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-25946) Fix CI/CD error for Ambari WebUI Tests
Yu Hou created AMBARI-25946: --- Summary: Fix CI/CD error for Ambari WebUI Tests Key: AMBARI-25946 URL: https://issues.apache.org/jira/browse/AMBARI-25946 Project: Ambari Issue Type: Bug Environment: Jenkins CI/CD Reporter: Yu Hou Attachments: image-2023-05-22-11-25-18-637.png !image-2023-05-22-11-25-18-637.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-25887) Blueprint inconsistent import/export logic for database connection url
[
https://issues.apache.org/jira/browse/AMBARI-25887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25887:
Fix Version/s: 2.8.0
> Blueprint inconsistent import/export logic for database connection url
> --
>
> Key: AMBARI-25887
> URL: https://issues.apache.org/jira/browse/AMBARI-25887
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: blueprint-configuration.json,
> image-2023-03-09-18-53-14-454.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When I manually deploy a cluster which contains hive service, and get
> blueprint config from the cluster:
> !image-2023-03-09-18-53-14-454.png!
>
> then create a new cluster by this config, an error occurs because it cannot
> resolve mysql connection url on hive-site configuration
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 201, in
> HiveMetastore().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 61, in start
> create_metastore_schema() # execute without config lock
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive.py",
> line 466, in create_metastore_schema
> user = params.hive_user
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 280, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'export
> HIVE_CONF_DIR=/etc/hive/conf ; /usr/bigtop/current/hive-client/bin/schematool
> -initSchema -dbType mysql -userName hive -passWord [PROTECTED] -verbose'
> returned 1. SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hive/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hadoop/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> Metastore connection URL: jdbc:mysql://%HOSTGROUP::host_group_1%/hive
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> Underlying cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException : Cannot
> load connection class because of underlying exception:
> 'java.lang.NumberFormatException: For input string: ":host_group_1%"'.
> SQL Error code: 0
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> at
> org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getConnectionToMetastore(HiveSchemaHelper.java:94)
> at
> org.apache.hive.beeline.HiveSchemaTool.getConnectionToMetastore(HiveSchemaTool.java:169)
> at
> org.apache.hive.beeline.HiveSchemaTool.testConnectionToMetastore(HiveSchemaTool.java:475)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:581)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:567)
> at org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:1517)
> at sun.reflect.NativeMethodAccessorImpl.in
[jira] [Updated] (AMBARI-25887) Blueprint inconsistent import/export logic for database connection url
[
https://issues.apache.org/jira/browse/AMBARI-25887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25887:
Component/s: ambari-server
blueprints
> Blueprint inconsistent import/export logic for database connection url
> --
>
> Key: AMBARI-25887
> URL: https://issues.apache.org/jira/browse/AMBARI-25887
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Attachments: blueprint-configuration.json,
> image-2023-03-09-18-53-14-454.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When I manually deploy a cluster which contains hive service, and get
> blueprint config from the cluster:
> !image-2023-03-09-18-53-14-454.png!
>
> then create a new cluster by this config, an error occurs because it cannot
> resolve mysql connection url on hive-site configuration
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 201, in
> HiveMetastore().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 61, in start
> create_metastore_schema() # execute without config lock
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive.py",
> line 466, in create_metastore_schema
> user = params.hive_user
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 280, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'export
> HIVE_CONF_DIR=/etc/hive/conf ; /usr/bigtop/current/hive-client/bin/schematool
> -initSchema -dbType mysql -userName hive -passWord [PROTECTED] -verbose'
> returned 1. SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hive/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hadoop/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> Metastore connection URL: jdbc:mysql://%HOSTGROUP::host_group_1%/hive
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> Underlying cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException : Cannot
> load connection class because of underlying exception:
> 'java.lang.NumberFormatException: For input string: ":host_group_1%"'.
> SQL Error code: 0
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> at
> org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getConnectionToMetastore(HiveSchemaHelper.java:94)
> at
> org.apache.hive.beeline.HiveSchemaTool.getConnectionToMetastore(HiveSchemaTool.java:169)
> at
> org.apache.hive.beeline.HiveSchemaTool.testConnectionToMetastore(HiveSchemaTool.java:475)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:581)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:567)
> at org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:1517)
> at sun.reflect.NativeMethodAccessorImpl
[jira] [Updated] (AMBARI-25886) Blueprint fails to select configurations
[
https://issues.apache.org/jira/browse/AMBARI-25886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25886:
Component/s: ambari-server
blueprints
> Blueprint fails to select configurations
>
>
> Key: AMBARI-25886
> URL: https://issues.apache.org/jira/browse/AMBARI-25886
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2023-03-09-17-42-54-720.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When I'm using blueprint to create a cluster, it fails to select
> configuration sometimes
> !image-2023-03-09-17-42-54-720.png!
>
> It causes errors when installing services:
> {code:java}
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 75, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
> was not found in configurations dictionary! {code}
>
> Blueprint document:
> https://cwiki.apache.org/confluence/display/AMBARI/Blueprints
--
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-25887) Blueprint inconsistent import/export logic for database connection url
[
https://issues.apache.org/jira/browse/AMBARI-25887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou resolved AMBARI-25887.
-
Resolution: Resolved
> Blueprint inconsistent import/export logic for database connection url
> --
>
> Key: AMBARI-25887
> URL: https://issues.apache.org/jira/browse/AMBARI-25887
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: blueprint-configuration.json,
> image-2023-03-09-18-53-14-454.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When I manually deploy a cluster which contains hive service, and get
> blueprint config from the cluster:
> !image-2023-03-09-18-53-14-454.png!
>
> then create a new cluster by this config, an error occurs because it cannot
> resolve mysql connection url on hive-site configuration
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 201, in
> HiveMetastore().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 61, in start
> create_metastore_schema() # execute without config lock
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive.py",
> line 466, in create_metastore_schema
> user = params.hive_user
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 280, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'export
> HIVE_CONF_DIR=/etc/hive/conf ; /usr/bigtop/current/hive-client/bin/schematool
> -initSchema -dbType mysql -userName hive -passWord [PROTECTED] -verbose'
> returned 1. SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hive/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hadoop/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> Metastore connection URL: jdbc:mysql://%HOSTGROUP::host_group_1%/hive
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> Underlying cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException : Cannot
> load connection class because of underlying exception:
> 'java.lang.NumberFormatException: For input string: ":host_group_1%"'.
> SQL Error code: 0
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> at
> org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getConnectionToMetastore(HiveSchemaHelper.java:94)
> at
> org.apache.hive.beeline.HiveSchemaTool.getConnectionToMetastore(HiveSchemaTool.java:169)
> at
> org.apache.hive.beeline.HiveSchemaTool.testConnectionToMetastore(HiveSchemaTool.java:475)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:581)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:567)
> at org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:1517)
> at sun.reflect.NativeMethodAccessorImpl.
[jira] [Resolved] (AMBARI-25886) Blueprint fails to select configurations
[
https://issues.apache.org/jira/browse/AMBARI-25886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou resolved AMBARI-25886.
-
Fix Version/s: 2.8.0
Resolution: Resolved
> Blueprint fails to select configurations
>
>
> Key: AMBARI-25886
> URL: https://issues.apache.org/jira/browse/AMBARI-25886
> Project: Ambari
> Issue Type: Bug
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2023-03-09-17-42-54-720.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When I'm using blueprint to create a cluster, it fails to select
> configuration sometimes
> !image-2023-03-09-17-42-54-720.png!
>
> It causes errors when installing services:
> {code:java}
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 75, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
> was not found in configurations dictionary! {code}
>
> Blueprint document:
> https://cwiki.apache.org/confluence/display/AMBARI/Blueprints
--
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-25889) Add Yaml Config support for services
[ https://issues.apache.org/jira/browse/AMBARI-25889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25889: --- Assignee: Yu Hou > Add Yaml Config support for services > > > Key: AMBARI-25889 > URL: https://issues.apache.org/jira/browse/AMBARI-25889 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: trunk > Environment: Ambari-trunk > Centos7(x_86_64) >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: trunk > > > As more and more components, such as Flink, use Yaml configuration files, we > need to support this format. -- 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-25889) Add Yaml Config support for services
Yu Hou created AMBARI-25889: --- Summary: Add Yaml Config support for services Key: AMBARI-25889 URL: https://issues.apache.org/jira/browse/AMBARI-25889 Project: Ambari Issue Type: New Feature Components: ambari-server Affects Versions: trunk Environment: Ambari-trunk Centos7(x_86_64) Reporter: Yu Hou Fix For: trunk As more and more components, such as Flink, use Yaml configuration files, we need to support this format. -- 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-25863) Fix a problem where the 'supported-refresh-commands' Element in configuration files for service was invalided
Yu Hou created AMBARI-25863: --- Summary: Fix a problem where the 'supported-refresh-commands' Element in configuration files for service was invalided Key: AMBARI-25863 URL: https://issues.apache.org/jira/browse/AMBARI-25863 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.8.0 Environment: Centos7(x86_64) Ambari-2.8.0 Bigtop-3.2.0 Reporter: Yu Hou Fix For: 2.8.0 Attachments: image-2023-02-23-21-53-04-918.png, image-2023-02-23-21-56-07-440.png, image-2023-02-23-21-58-31-071.png As https://issues.apache.org/jira/browse/AMBARI-21406 describes，'supported-refresh-commands' can Refresh configurations without restart command. But it has a few bugs that cause the 'supported-refresh-commands' tags to fail, as shown below, !image-2023-02-23-21-53-04-918.png! which they should be to stay consistent with the rest. !image-2023-02-23-21-56-07-440.png! How was this patch tested? !image-2023-02-23-21-58-31-071.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] [Assigned] (AMBARI-25863) Fix a problem where the 'supported-refresh-commands' Element in configuration files for service was invalided
[ https://issues.apache.org/jira/browse/AMBARI-25863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25863: --- Assignee: Yu Hou > Fix a problem where the 'supported-refresh-commands' Element in configuration > files for service was invalided > - > > Key: AMBARI-25863 > URL: https://issues.apache.org/jira/browse/AMBARI-25863 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.8.0 > Environment: Centos7(x86_64) > Ambari-2.8.0 > Bigtop-3.2.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-02-23-21-53-04-918.png, > image-2023-02-23-21-56-07-440.png, image-2023-02-23-21-58-31-071.png > > > As https://issues.apache.org/jira/browse/AMBARI-21406 > describes，'supported-refresh-commands' can Refresh configurations without > restart command. > But it has a few bugs that cause the 'supported-refresh-commands' tags to > fail, as shown below, > !image-2023-02-23-21-53-04-918.png! > which they should be to stay consistent with the rest. > !image-2023-02-23-21-56-07-440.png! > How was this patch tested? > !image-2023-02-23-21-58-31-071.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] [Assigned] (AMBARI-25857) Ambari-Metrics should in embedded mode when HDFS wasn't installed
[ https://issues.apache.org/jira/browse/AMBARI-25857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25857: --- Assignee: Yu Hou > Ambari-Metrics should in embedded mode when HDFS wasn't installed > - > > Key: AMBARI-25857 > URL: https://issues.apache.org/jira/browse/AMBARI-25857 > Project: Ambari > Issue Type: Sub-task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7(x86_64) > Ambari-2.8.0 > Ambari-Metrics-2.0.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > > Ambari-Metrics should in embedded mode when HDFS wasn't installed -- 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-25857) Ambari-Metrics should in embedded mode when HDFS wasn't installed
Yu Hou created AMBARI-25857: --- Summary: Ambari-Metrics should in embedded mode when HDFS wasn't installed Key: AMBARI-25857 URL: https://issues.apache.org/jira/browse/AMBARI-25857 Project: Ambari Issue Type: Sub-task Components: ambari-metrics Affects Versions: 2.8.0 Environment: Centos7(x86_64) Ambari-2.8.0 Ambari-Metrics-2.0.0 Reporter: Yu Hou Fix For: 2.8.0 Ambari-Metrics should in embedded mode when HDFS wasn't installed -- 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-25853) 'hbase.zookeeper.quorum' was wrong for Ambari-Metrics in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-25853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25853:
Summary: 'hbase.zookeeper.quorum' was wrong for Ambari-Metrics in embedded
mode (was: Fix failed to start Ambari-Metrics in embedded mode)
> 'hbase.zookeeper.quorum' was wrong for Ambari-Metrics in embedded mode
> --
>
> Key: AMBARI-25853
> URL: https://issues.apache.org/jira/browse/AMBARI-25853
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-metrics
>Affects Versions: 2.8.0
> Environment: Ambari-2.8.0
> Bigtop-3.2.0
> Centos-7(x86_64)
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2023-02-09-11-32-23-603.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When 'timeline.metrics.service.operation.mode=embedded' and
> 'hbase.cluster.distributed=false'
> The hbase-master.log is
> {code:java}
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:user.home=/home/ams
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:user.dir=/usr/lib/ams-hbase/bin
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:os.memory.free=1587MB
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:os.memory.max=1981MB
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:os.memory.total=1981MB
> 2023-02-09 02:04:46,910 INFO [main] zookeeper.ZooKeeper: Initiating client
> connection, connectString=ambari-agent-01:61181 sessionTimeout=12
> watcher=org.apache.hadoop.hbase.zookeeper.PendingWatcher@56da52a7
> 2023-02-09 02:04:46,915 INFO [main] common.X509Util: Setting -D
> jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated
> TLS renegotiation
> 2023-02-09 02:04:46,920 INFO [main] zookeeper.ClientCnxnSocket:
> jute.maxbuffer value is 4194304 Bytes
> 2023-02-09 02:04:46,930 INFO [main] zookeeper.ClientCnxn:
> zookeeper.request.timeout value is 0. feature enabled=
> 2023-02-09 02:04:46,939 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:46,940 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:48,043 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:48,044 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:49,145 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:49,145 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:50,246 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:50,247 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:51,347 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:51,348 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:52,449 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:52,449 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:53,550 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown
[jira] [Updated] (AMBARI-25853) Fix failed to start Ambari-Metrics in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-25853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25853:
Summary: Fix failed to start Ambari-Metrics in embedded mode (was: Fix
failed to start Ambari-Metrics when
'timeline.metrics.service.operation.mode=embedded')
> Fix failed to start Ambari-Metrics in embedded mode
> ---
>
> Key: AMBARI-25853
> URL: https://issues.apache.org/jira/browse/AMBARI-25853
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-metrics
>Affects Versions: 2.8.0
> Environment: Ambari-2.8.0
> Bigtop-3.2.0
> Centos-7(x86_64)
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2023-02-09-11-32-23-603.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When 'timeline.metrics.service.operation.mode=embedded' and
> 'hbase.cluster.distributed=false'
> The hbase-master.log is
> {code:java}
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:user.home=/home/ams
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:user.dir=/usr/lib/ams-hbase/bin
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:os.memory.free=1587MB
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:os.memory.max=1981MB
> 2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
> environment:os.memory.total=1981MB
> 2023-02-09 02:04:46,910 INFO [main] zookeeper.ZooKeeper: Initiating client
> connection, connectString=ambari-agent-01:61181 sessionTimeout=12
> watcher=org.apache.hadoop.hbase.zookeeper.PendingWatcher@56da52a7
> 2023-02-09 02:04:46,915 INFO [main] common.X509Util: Setting -D
> jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated
> TLS renegotiation
> 2023-02-09 02:04:46,920 INFO [main] zookeeper.ClientCnxnSocket:
> jute.maxbuffer value is 4194304 Bytes
> 2023-02-09 02:04:46,930 INFO [main] zookeeper.ClientCnxn:
> zookeeper.request.timeout value is 0. feature enabled=
> 2023-02-09 02:04:46,939 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:46,940 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:48,043 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:48,044 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:49,145 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:49,145 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:50,246 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:50,247 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:51,347 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:51,348 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:52,449 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02-09 02:04:52,449 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Socket error occurred:
> ambari-agent-01/172.21.0.3:61181: Connection refused
> 2023-02-09 02:04:53,550 INFO [main-SendThread(ambari-agent-01:61181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
> (unknown error)
> 2023-02
[jira] [Created] (AMBARI-25853) Fix failed to start Ambari-Metrics when 'timeline.metrics.service.operation.mode=embedded'
Yu Hou created AMBARI-25853:
---
Summary: Fix failed to start Ambari-Metrics when
'timeline.metrics.service.operation.mode=embedded'
Key: AMBARI-25853
URL: https://issues.apache.org/jira/browse/AMBARI-25853
Project: Ambari
Issue Type: Sub-task
Components: ambari-metrics
Affects Versions: 2.8.0
Environment: Ambari-2.8.0
Bigtop-3.2.0
Centos-7(x86_64)
Reporter: Yu Hou
Assignee: Yu Hou
Fix For: 2.8.0
Attachments: image-2023-02-09-11-32-23-603.png
When 'timeline.metrics.service.operation.mode=embedded' and
'hbase.cluster.distributed=false'
The hbase-master.log is
{code:java}
2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
environment:user.home=/home/ams
2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
environment:user.dir=/usr/lib/ams-hbase/bin
2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
environment:os.memory.free=1587MB
2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
environment:os.memory.max=1981MB
2023-02-09 02:04:46,905 INFO [main] zookeeper.ZooKeeper: Client
environment:os.memory.total=1981MB
2023-02-09 02:04:46,910 INFO [main] zookeeper.ZooKeeper: Initiating client
connection, connectString=ambari-agent-01:61181 sessionTimeout=12
watcher=org.apache.hadoop.hbase.zookeeper.PendingWatcher@56da52a7
2023-02-09 02:04:46,915 INFO [main] common.X509Util: Setting -D
jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS
renegotiation
2023-02-09 02:04:46,920 INFO [main] zookeeper.ClientCnxnSocket: jute.maxbuffer
value is 4194304 Bytes
2023-02-09 02:04:46,930 INFO [main] zookeeper.ClientCnxn:
zookeeper.request.timeout value is 0. feature enabled=
2023-02-09 02:04:46,939 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
2023-02-09 02:04:46,940 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Socket error occurred: ambari-agent-01/172.21.0.3:61181:
Connection refused
2023-02-09 02:04:48,043 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
2023-02-09 02:04:48,044 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Socket error occurred: ambari-agent-01/172.21.0.3:61181:
Connection refused
2023-02-09 02:04:49,145 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
2023-02-09 02:04:49,145 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Socket error occurred: ambari-agent-01/172.21.0.3:61181:
Connection refused
2023-02-09 02:04:50,246 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
2023-02-09 02:04:50,247 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Socket error occurred: ambari-agent-01/172.21.0.3:61181:
Connection refused
2023-02-09 02:04:51,347 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
2023-02-09 02:04:51,348 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Socket error occurred: ambari-agent-01/172.21.0.3:61181:
Connection refused
2023-02-09 02:04:52,449 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
2023-02-09 02:04:52,449 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Socket error occurred: ambari-agent-01/172.21.0.3:61181:
Connection refused
2023-02-09 02:04:53,550 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
2023-02-09 02:04:53,551 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Socket error occurred: ambari-agent-01/172.21.0.3:61181:
Connection refused
2023-02-09 02:04:54,652 INFO [main-SendThread(ambari-agent-01:61181)]
zookeeper.ClientCnxn: Opening socket connection to server
ambari-agent-01/172.21.0.3:61181. Will not attempt to authenticate using SASL
(unknown error)
{code}
'hbase.zookeeper.quorum' should be localhost
After fixed, Ambari-metrics start successful.
!image-2023-02-09-11-32-23-603.png!
[jira] [Updated] (AMBARI-25835) Fix alerts path for BIGTOP-3.2.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-25835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25835: Summary: Fix alerts path for BIGTOP-3.2.0 stack (was: Fix alerts for BIGTOP-3.2.0 stack) > Fix alerts path for BIGTOP-3.2.0 stack > -- > > Key: AMBARI-25835 > URL: https://issues.apache.org/jira/browse/AMBARI-25835 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-01-07-15-45-31-641.png, > image-2023-01-07-15-46-56-488.png, image-2023-01-07-15-47-41-105.png > > Time Spent: 10m > Remaining Estimate: 0h > > As shown in the following figure, the alert fails because the alerts.json > path of HDFS is incorrectly defined. > !image-2023-01-07-15-47-41-105.png! > !image-2023-01-07-15-45-31-641.png! > After fix this error. > !image-2023-01-07-15-46-56-488.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] [Assigned] (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 ] Yu Hou reassigned AMBARI-25840: --- Assignee: Yu Hou > Optimized rpm packaging for the Ambari-Metric-Collector > --- > > Key: AMBARI-25840 > URL: https://issues.apache.org/jira/browse/AMBARI-25840 > 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 > 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] [Created] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
Yu Hou created AMBARI-25840: --- Summary: Optimized rpm packaging for the Ambari-Metric-Collector Key: AMBARI-25840 URL: https://issues.apache.org/jira/browse/AMBARI-25840 Project: Ambari Issue Type: Sub-task Components: ambari-metrics Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou 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-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
[
https://issues.apache.org/jira/browse/AMBARI-25838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25838:
Description:
1. When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
org.apache.kafka.common.config.ConfigException: Only one of
inter.broker.listener.name and security.inter.broker.protocol should be set.
at
kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
at
kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
{code}
2. Remove the DEPRECATED attribute port
!screenshot-1.png!
was:
1. When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.ser
[jira] [Updated] (AMBARI-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
[
https://issues.apache.org/jira/browse/AMBARI-25838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25838:
Description:
1. When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
org.apache.kafka.common.config.ConfigException: Only one of
inter.broker.listener.name and security.inter.broker.protocol should be set.
at
kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
at
kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
{code}
2. Remove the DEPRECATED attribute port
was:
When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validate
[jira] [Updated] (AMBARI-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
[
https://issues.apache.org/jira/browse/AMBARI-25838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25838:
Attachment: screenshot-1.png
> Add kafka_listeners to kafka to fix startup failures on kerberos enabled
>
>
> Key: AMBARI-25838
> URL: https://issues.apache.org/jira/browse/AMBARI-25838
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Centos7
> Ambari-2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 1. When kerberos enabled, kafka failed to start.
> The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
> when kerberos is enabled, an attribute controlled by kafka_listeners.
> {code:java}
> [2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
> (kafka.server.KafkaServer)
> [2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> org.apache.kafka.common.config.ConfigException: Only one of
> inter.broker.listener.name and security.inter.broker.protocol should be set.
> at
> kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
> at
> kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> {code}
> 2. Remove the DEPRECATED attribute port
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
[jira] [Assigned] (AMBARI-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
[
https://issues.apache.org/jira/browse/AMBARI-25838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou reassigned AMBARI-25838:
---
Assignee: Yu Hou
> Add kafka_listeners to kafka to fix startup failures on kerberos enabled
>
>
> Key: AMBARI-25838
> URL: https://issues.apache.org/jira/browse/AMBARI-25838
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Centos7
> Ambari-2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
>
> When kerberos enabled, kafka failed to start.
> The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
> when kerberos is enabled, an attribute controlled by kafka_listeners.
> {code:java}
> [2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
> (kafka.server.KafkaServer)
> [2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> org.apache.kafka.common.config.ConfigException: Only one of
> inter.broker.listener.name and security.inter.broker.protocol should be set.
> at
> kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
> at
> kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> {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.apa
[jira] [Created] (AMBARI-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
Yu Hou created AMBARI-25838:
---
Summary: Add kafka_listeners to kafka to fix startup failures on
kerberos enabled
Key: AMBARI-25838
URL: https://issues.apache.org/jira/browse/AMBARI-25838
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.8.0
Environment: Centos7
Ambari-2.8.0
Reporter: Yu Hou
Fix For: 2.8.0
When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
org.apache.kafka.common.config.ConfigException: Only one of
inter.broker.listener.name and security.inter.broker.protocol should be set.
at
kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
at
kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
{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] [Assigned] (AMBARI-25836) Remove resources/stacks/BIGTOP/3.2.0/widgets.json and resources/stacks/BIGTOP/3.2.0/kerberos.json
[ https://issues.apache.org/jira/browse/AMBARI-25836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25836: --- Assignee: Yu Hou > Remove resources/stacks/BIGTOP/3.2.0/widgets.json and > resources/stacks/BIGTOP/3.2.0/kerberos.json > - > > Key: AMBARI-25836 > URL: https://issues.apache.org/jira/browse/AMBARI-25836 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > > As https://issues.apache.org/jira/browse/AMBARI-22131 and > https://issues.apache.org/jira/browse/AMBARI-22147 said. > The resources/stacks/BIGTOP/3.2.0/widgets.json and > resources/stacks/BIGTOP/3.2.0/kerberos.json were invalid. > They should be removed because they have been replaced by > resources/widgets.json and resources/kerberos.json. -- 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-25836) Remove resources/stacks/BIGTOP/3.2.0/widgets.json and resources/stacks/BIGTOP/3.2.0/kerberos.json
Yu Hou created AMBARI-25836: --- Summary: Remove resources/stacks/BIGTOP/3.2.0/widgets.json and resources/stacks/BIGTOP/3.2.0/kerberos.json Key: AMBARI-25836 URL: https://issues.apache.org/jira/browse/AMBARI-25836 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou Fix For: 2.8.0 As https://issues.apache.org/jira/browse/AMBARI-22131 and https://issues.apache.org/jira/browse/AMBARI-22147 said. The resources/stacks/BIGTOP/3.2.0/widgets.json and resources/stacks/BIGTOP/3.2.0/kerberos.json were invalid. They should be removed because they have been replaced by resources/widgets.json and resources/kerberos.json. -- 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-25835) Fix alerts for BIGTOP-3.2.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-25835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25835: --- Assignee: Yu Hou > Fix alerts for BIGTOP-3.2.0 stack > - > > Key: AMBARI-25835 > URL: https://issues.apache.org/jira/browse/AMBARI-25835 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-01-07-15-45-31-641.png, > image-2023-01-07-15-46-56-488.png, image-2023-01-07-15-47-41-105.png > > > As shown in the following figure, the alert fails because the alerts.json > path of HDFS is incorrectly defined. > !image-2023-01-07-15-47-41-105.png! > !image-2023-01-07-15-45-31-641.png! > After fix this error. > !image-2023-01-07-15-46-56-488.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-25835) Fix alerts for BIGTOP-3.2.0 stack
Yu Hou created AMBARI-25835: --- Summary: Fix alerts for BIGTOP-3.2.0 stack Key: AMBARI-25835 URL: https://issues.apache.org/jira/browse/AMBARI-25835 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou Fix For: 2.8.0 Attachments: image-2023-01-07-15-45-31-641.png, image-2023-01-07-15-46-56-488.png, image-2023-01-07-15-47-41-105.png As shown in the following figure, the alert fails because the alerts.json path of HDFS is incorrectly defined. !image-2023-01-07-15-47-41-105.png! !image-2023-01-07-15-45-31-641.png! After fix this error. !image-2023-01-07-15-46-56-488.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-25834) Fix syntax errors for ambari-metrics-collector
Yu Hou created AMBARI-25834: --- Summary: Fix syntax errors for ambari-metrics-collector Key: AMBARI-25834 URL: https://issues.apache.org/jira/browse/AMBARI-25834 Project: Ambari Issue Type: Sub-task Components: ambari-metrics Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou 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] [Assigned] (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 ] Yu Hou reassigned AMBARI-25834: --- Assignee: Yu Hou > Fix syntax errors for ambari-metrics-collector > -- > > Key: AMBARI-25834 > URL: https://issues.apache.org/jira/browse/AMBARI-25834 > 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 > 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] [Assigned] (AMBARI-25832) Fixed Permission denied error in ZOOKEEPER service_check
[ https://issues.apache.org/jira/browse/AMBARI-25832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25832: --- Assignee: Yu Hou > Fixed Permission denied error in ZOOKEEPER service_check > > > Key: AMBARI-25832 > URL: https://issues.apache.org/jira/browse/AMBARI-25832 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-01-05-15-51-21-534.png > > Time Spent: 10m > Remaining Estimate: 0h > > Permission denied error occurs when Zookeeper runs service_check. > We should chmod /var/log/zookeeper/zookeeper.log 644 to 664. > !image-2023-01-05-15-51-21-534.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] [Assigned] (AMBARI-25833) An error occurs when Hbase service_check is run for the first time after Kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-25833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou reassigned AMBARI-25833:
---
Assignee: Yu Hou
> An error occurs when Hbase service_check is run for the first time after
> Kerberos is enabled
>
>
> Key: AMBARI-25833
> URL: https://issues.apache.org/jira/browse/AMBARI-25833
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Centos7
> Ambari-2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2023-01-05-15-57-31-938.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> An error occurs when Hbase service_check is run for the first time after
> Kerberos is enabled.
> An error for {code:sh}grant 'ambari-qa','RWXCA'{code} maybe occurs because
> Hbase initialization isn't completed.
> We need to add retry to this command.
> !image-2023-01-05-15-57-31-938.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-25832) Fixed Permission denied error in ZOOKEEPER service_check
[ https://issues.apache.org/jira/browse/AMBARI-25832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25832: Summary: Fixed Permission denied error in ZOOKEEPER service_check (was: Fixed Permission denied in ZOOKEEPER service_check) > Fixed Permission denied error in ZOOKEEPER service_check > > > Key: AMBARI-25832 > URL: https://issues.apache.org/jira/browse/AMBARI-25832 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-01-05-15-51-21-534.png > > > Permission denied error occurs when Zookeeper runs service_check. > We should chmod /var/log/zookeeper/zookeeper.log 644 to 664. > !image-2023-01-05-15-51-21-534.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-25832) Fixed Permission denied in ZOOKEEPER service_check
[ https://issues.apache.org/jira/browse/AMBARI-25832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25832: Description: Permission denied error occurs when Zookeeper runs service_check. We should chmod /var/log/zookeeper/zookeeper.log 644 to 664. !image-2023-01-05-15-51-21-534.png! was: Permission denied error occurs when Zookeeper runs service_check. !image-2023-01-05-15-51-21-534.png! > Fixed Permission denied in ZOOKEEPER service_check > -- > > Key: AMBARI-25832 > URL: https://issues.apache.org/jira/browse/AMBARI-25832 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-01-05-15-51-21-534.png > > > Permission denied error occurs when Zookeeper runs service_check. > We should chmod /var/log/zookeeper/zookeeper.log 644 to 664. > !image-2023-01-05-15-51-21-534.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-25833) An error occurs when Hbase service_check is run for the first time after Kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-25833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25833:
Epic Link: AMBARI-25792
> An error occurs when Hbase service_check is run for the first time after
> Kerberos is enabled
>
>
> Key: AMBARI-25833
> URL: https://issues.apache.org/jira/browse/AMBARI-25833
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Centos7
> Ambari-2.8.0
>Reporter: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2023-01-05-15-57-31-938.png
>
>
> An error occurs when Hbase service_check is run for the first time after
> Kerberos is enabled.
> An error for {code:sh}grant 'ambari-qa','RWXCA'{code} maybe occurs because
> Hbase initialization isn't completed.
> We need to add retry to this command.
> !image-2023-01-05-15-57-31-938.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-25832) Fixed Permission denied in ZOOKEEPER service_check
[ https://issues.apache.org/jira/browse/AMBARI-25832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25832: Epic Link: AMBARI-25792 > Fixed Permission denied in ZOOKEEPER service_check > -- > > Key: AMBARI-25832 > URL: https://issues.apache.org/jira/browse/AMBARI-25832 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-01-05-15-51-21-534.png > > > Permission denied error occurs when Zookeeper runs service_check. > !image-2023-01-05-15-51-21-534.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-25833) An error occurs when Hbase service_check is run for the first time after Kerberos is enabled
Yu Hou created AMBARI-25833:
---
Summary: An error occurs when Hbase service_check is run for the
first time after Kerberos is enabled
Key: AMBARI-25833
URL: https://issues.apache.org/jira/browse/AMBARI-25833
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.8.0
Environment: Centos7
Ambari-2.8.0
Reporter: Yu Hou
Fix For: 2.8.0
Attachments: image-2023-01-05-15-57-31-938.png
An error occurs when Hbase service_check is run for the first time after
Kerberos is enabled.
An error for {code:sh}grant 'ambari-qa','RWXCA'{code} maybe occurs because
Hbase initialization isn't completed.
We need to add retry to this command.
!image-2023-01-05-15-57-31-938.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-25832) Fixed Permission denied in ZOOKEEPER service_check
Yu Hou created AMBARI-25832: --- Summary: Fixed Permission denied in ZOOKEEPER service_check Key: AMBARI-25832 URL: https://issues.apache.org/jira/browse/AMBARI-25832 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou Fix For: 2.8.0 Attachments: image-2023-01-05-15-51-21-534.png Permission denied error occurs when Zookeeper runs service_check. !image-2023-01-05-15-51-21-534.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] [Assigned] (AMBARI-25830) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-25830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25830: --- Assignee: Yu Hou > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-25830 > URL: https://issues.apache.org/jira/browse/AMBARI-25830 > 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 > Fix For: 2.8.0 > > > Upgrade grafana from 6.7.4 to 9.3.2. -- 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-25830) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-25830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25830: Description: Upgrade grafana from 6.7.4 to 9.3.2. > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-25830 > URL: https://issues.apache.org/jira/browse/AMBARI-25830 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Priority: Major > Fix For: 2.8.0 > > > Upgrade grafana from 6.7.4 to 9.3.2. -- 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-23466) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-23466: Summary: Upgrade AMS Grafana version to 9.3.2 (was: Upgrade AMS Grafana version to 6.7.4) > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: lucas >Priority: Critical > 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-23466) Upgrade AMS Grafana version to 6.7.4
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-23466: Epic Name: AMS Grafana Version upgrade to 9.3.2 (was: AMS Grafana Version upgrade to 6.7.4) > Upgrade AMS Grafana version to 6.7.4 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: lucas >Priority: Critical > 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-25830) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-25830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25830: Epic Link: AMBARI-23466 > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-25830 > URL: https://issues.apache.org/jira/browse/AMBARI-25830 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >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-25830) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-25830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25830: Parent: (was: AMBARI-23466) Issue Type: Task (was: Sub-task) > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-25830 > URL: https://issues.apache.org/jira/browse/AMBARI-25830 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >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-25830) Upgrade AMS Grafana version to 9.3.2
Yu Hou created AMBARI-25830: --- Summary: Upgrade AMS Grafana version to 9.3.2 Key: AMBARI-25830 URL: https://issues.apache.org/jira/browse/AMBARI-25830 Project: Ambari Issue Type: Sub-task Components: ambari-metrics Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou 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-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 ] 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
[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 ] 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] [Updated] (AMBARI-25825) Adjust Ambari metrics dependency for Ambari-Metrics
[ 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] [Assigned] (AMBARI-25825) Port BIGTOP-3872 to fix Ambari-Metrics
[ 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] [Created] (AMBARI-25825) Port BIGTOP-3872 to fix Ambari-Metrics
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] [Updated] (AMBARI-25800) Add AMBARI-METRICS to common-services
[ https://issues.apache.org/jira/browse/AMBARI-25800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25800: Description: Add AMBARI-METRICS 2.0.0 to common-services. > Add AMBARI-METRICS to common-services > - > > Key: AMBARI-25800 > URL: https://issues.apache.org/jira/browse/AMBARI-25800 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add AMBARI-METRICS 2.0.0 to common-services. -- 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 ] Yu Hou updated AMBARI-25801: Description: 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. > 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] [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 ] Yu Hou updated AMBARI-25822: Description: 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! was: The classes introduced in the following code have been removed, 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! > 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] [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 ] Yu Hou updated AMBARI-25822: Description: The classes introduced in the following code have been removed, 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! > 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 classes introduced in the following code have been removed, 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 ] Yu Hou updated AMBARI-25822: Attachment: screenshot-1.png > 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 > > -- 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 ] Yu Hou updated AMBARI-25821: Description: 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. > 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] [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 ] Yu Hou updated AMBARI-25821: Attachment: screenshot-2.png > 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 > > -- 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 ] Yu Hou updated AMBARI-25821: Attachment: screenshot-1.png > 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 > > -- 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] (AMBARI-25800) Add AMBARI-METRICS to common-services
[ https://issues.apache.org/jira/browse/AMBARI-25800 ] Yu Hou deleted comment on AMBARI-25800: - was (Author: JIRAUSER292368): yuqi will port AMBARI-METRICS from BigTop. > Add AMBARI-METRICS to common-services > - > > Key: AMBARI-25800 > URL: https://issues.apache.org/jira/browse/AMBARI-25800 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Time Spent: 0.5h > 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] [Reopened] (AMBARI-25800) Add AMBARI-METRICS to common-services
[ https://issues.apache.org/jira/browse/AMBARI-25800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reopened AMBARI-25800: - > Add AMBARI-METRICS to common-services > - > > Key: AMBARI-25800 > URL: https://issues.apache.org/jira/browse/AMBARI-25800 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Time Spent: 0.5h > 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] [Resolved] (AMBARI-25800) Add AMBARI-METRICS to common-services
[ https://issues.apache.org/jira/browse/AMBARI-25800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou resolved AMBARI-25800. - Resolution: Duplicate yuqi will port AMBARI-METRICS from BigTop. > Add AMBARI-METRICS to common-services > - > > Key: AMBARI-25800 > URL: https://issues.apache.org/jira/browse/AMBARI-25800 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Time Spent: 0.5h > 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] [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 ] Yu Hou updated AMBARI-25801: Summary: Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari (was: Fix the Ambari-Metrics rpm package deployment failure) > 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 > > -- 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-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 ] Yu Hou reassigned AMBARI-25822: --- Assignee: Yu Hou > 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 > 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] [Assigned] (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 ] Yu Hou reassigned AMBARI-25821: --- Assignee: Yu Hou > 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 > > -- 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-25822) Remove invalid relocations in pom.xml for ambari-metrics-common
Yu Hou created AMBARI-25822: --- Summary: 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 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-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 ] Yu Hou updated AMBARI-25821: Summary: Fixed syntax error that caused OOM in the ambari-metrics-collector (was: Fixed syntax error that caused OOM in the ambari-metric-collector) > 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 >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-25821) Fixed syntax error that caused OOM in the ambari-metric-collector
[ https://issues.apache.org/jira/browse/AMBARI-25821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25821: Summary: Fixed syntax error that caused OOM in the ambari-metric-collector (was: Fix the OOM in the ambari-metric-collector) > Fixed syntax error that caused OOM in the ambari-metric-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 >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-25821) Fix the OOM in the ambari-metric-collector
Yu Hou created AMBARI-25821: --- Summary: Fix the OOM in the ambari-metric-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 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-25820) Update Spark and Flink versions to be consistent with BigTop
Yu Hou created AMBARI-25820: --- Summary: 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 Fix For: 2.8.0 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] [Assigned] (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 ] Yu Hou reassigned AMBARI-25820: --- Assignee: Yu Hou > 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 > > > 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] [Created] (AMBARI-25819) Fix failed to build Ambari-Metrics
Yu Hou created AMBARI-25819: --- Summary: Fix failed to build Ambari-Metrics Key: AMBARI-25819 URL: https://issues.apache.org/jira/browse/AMBARI-25819 Project: Ambari Issue Type: Sub-task Components: metrics Affects Versions: 2.8.0 Environment: Centos7 Reporter: Yu Hou 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] [Assigned] (AMBARI-25819) Fix failed to build Ambari-Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25819: --- Assignee: Yu Hou > Fix failed to build Ambari-Metrics > -- > > Key: AMBARI-25819 > URL: https://issues.apache.org/jira/browse/AMBARI-25819 > Project: Ambari > Issue Type: Sub-task > 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) Fix the Ambari-Metrics rpm package deployment failure
[ https://issues.apache.org/jira/browse/AMBARI-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25801: Summary: Fix the Ambari-Metrics rpm package deployment failure (was: Fix the Ambari-Metrics deployment failure) > Fix the Ambari-Metrics rpm package deployment failure > - > > 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 > 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] [Assigned] (AMBARI-25801) Fix the Ambari-Metrics deployment failure
[ https://issues.apache.org/jira/browse/AMBARI-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25801: --- Assignee: Yu Hou > Fix the Ambari-Metrics deployment failure > - > > 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 > 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-25801) Fix the Ambari-Metrics deployment failure
Yu Hou created AMBARI-25801: --- Summary: Fix the Ambari-Metrics deployment failure 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 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-25800) Add AMBARI-METRICS to common-services
Yu Hou created AMBARI-25800: --- Summary: Add AMBARI-METRICS to common-services Key: AMBARI-25800 URL: https://issues.apache.org/jira/browse/AMBARI-25800 Project: Ambari Issue Type: Sub-task Components: stacks Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou 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] [Assigned] (AMBARI-25800) Add AMBARI-METRICS to common-services
[ https://issues.apache.org/jira/browse/AMBARI-25800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25800: --- Assignee: Yu Hou > Add AMBARI-METRICS to common-services > - > > Key: AMBARI-25800 > URL: https://issues.apache.org/jira/browse/AMBARI-25800 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >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] [Assigned] (AMBARI-25799) Introduce AMBARI-METRICS to BIGTOP stack
[ https://issues.apache.org/jira/browse/AMBARI-25799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25799: --- Assignee: Yu Hou > Introduce AMBARI-METRICS to BIGTOP stack > > > Key: AMBARI-25799 > URL: https://issues.apache.org/jira/browse/AMBARI-25799 > 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 > Fix For: 2.8.0 > > > Introduce AMBARI-METRICS service to common-services -- 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-25799) Introduce AMBARI-METRICS to BIGTOP stack
Yu Hou created AMBARI-25799: --- Summary: Introduce AMBARI-METRICS to BIGTOP stack Key: AMBARI-25799 URL: https://issues.apache.org/jira/browse/AMBARI-25799 Project: Ambari Issue Type: Improvement Components: ambari-metrics Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou Fix For: 2.8.0 Introduce AMBARI-METRICS service to common-services -- 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-25789) Add stack version suffix for BIGTOP packages
[
https://issues.apache.org/jira/browse/AMBARI-25789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25789:
Summary: Add stack version suffix for BIGTOP packages (was: Support
BIGTOP-3.2.0 stack upgrade)
> Add stack version suffix for BIGTOP packages
>
>
> Key: AMBARI-25789
> URL: https://issues.apache.org/jira/browse/AMBARI-25789
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Ambari-2.8.0
> BigTop-3.2.0
> Centos7(x86_64)
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Update to support BIGTOP-3.2.0 stack upgrade.
> e.g. {code}BIGTOP-3.2.0 -> BIGTOP-3.2.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-25775) Failed to compile Ambari-Infra because of invalid url
[
https://issues.apache.org/jira/browse/AMBARI-25775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25775:
Epic Link: AMBARI-25792
> Failed to compile Ambari-Infra because of invalid url
> -
>
> Key: AMBARI-25775
> URL: https://issues.apache.org/jira/browse/AMBARI-25775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
>Affects Versions: 2.8.0
> Environment: Centos7
> Ambari-infra-2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: image-2022-11-04-10-05-46-029.png
>
>
> http://central.maven.org/maven2 has been unable to access
> !image-2022-11-04-10-05-46-029.png!
> {code}
> kage/code/ambari-infra/ambari-infra-solr-client/target/migrate/lucene-core-6.6.2.jar
> [INFO]
>
> [INFO] Reactor Summary for ambari-infra 3.0.0.0-SNAPSHOT:
> [INFO]
> [INFO] ambari-infra ... SUCCESS [ 6.914
> s]
> [INFO] Ambari Infra Solr Client ... FAILURE [ 7.090
> s]
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Infra Manager ... SKIPPED
> [INFO] Ambari Infra Assembly .. SKIPPED
> [INFO] Ambari Infra Manager Integration Tests . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 14.279 s
> [INFO] Finished at: 2022-11-04T10:04:29+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project
> ambari-infra-solr-client: An Ant BuildException has occured: The following
> error occurred while executing this line:
> [ERROR] /opt/package/code/ambari-infra/ambari-infra-solr-client/build.xml:39:
> java.net.UnknownHostException: central.maven.org
> [ERROR] around Ant part .. @ 4:28 in
> /opt/package/code/ambari-infra/ambari-infra-solr-client/target/antrun/build-main.xml:
> Unknown host central.maven.org
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :ambari-infra-solr-client
> make: *** [rpm] Error 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-25789) Support BIGTOP-3.2.0 stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-25789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25789:
Issue Type: Task (was: Improvement)
> Support BIGTOP-3.2.0 stack upgrade
> --
>
> Key: AMBARI-25789
> URL: https://issues.apache.org/jira/browse/AMBARI-25789
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Ambari-2.8.0
> BigTop-3.2.0
> Centos7(x86_64)
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Update to support BIGTOP-3.2.0 stack upgrade.
> e.g. {code}BIGTOP-3.2.0 -> BIGTOP-3.2.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-25735) Fix build failure on Ambari Agent due to maven-shade-plugin version
[ https://issues.apache.org/jira/browse/AMBARI-25735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25735: Epic Link: AMBARI-25792 Fix Version/s: (was: trunk) Affects Version/s: 2.8.0 (was: trunk) > Fix build failure on Ambari Agent due to maven-shade-plugin version > --- > > Key: AMBARI-25735 > URL: https://issues.apache.org/jira/browse/AMBARI-25735 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.8.0 > Environment: Ambari: trunk >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2022-09-21-16-12-10-861.png > > Time Spent: 50m > Remaining Estimate: 0h > > !image-2022-09-21-16-12-10-861.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-25774) Fix Namenode warn `java.nio.file.NoSuchFileException: /etc/security/clientKeys/all.jks`
[
https://issues.apache.org/jira/browse/AMBARI-25774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25774:
Epic Link: AMBARI-25792
> Fix Namenode warn `java.nio.file.NoSuchFileException:
> /etc/security/clientKeys/all.jks`
> ---
>
> Key: AMBARI-25774
> URL: https://issues.apache.org/jira/browse/AMBARI-25774
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Ambari-2.8.0
> Centos-7
> Bigtop-3.2.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When start namenode, will appear warn log as follow
> {code}
> 2022-10-31 13:36:25,524 WARN web.URLConnectionFactory
> (URLConnectionFactory.java:getSSLConnectionConfiguration(102)) - Cannot load
> customized ss
> l related configuration. Fallback to system-generic settings.
> java.nio.file.NoSuchFileException: /etc/security/clientKeys/all.jks
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel(Files.java:361)
> at java.nio.file.Files.newByteChannel(Files.java:407)
> at
> java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream(Files.java:152)
> at
> org.apache.hadoop.security.ssl.ReloadingX509TrustManager.loadTrustManager(ReloadingX509TrustManager.java:131)
> at
> org.apache.hadoop.security.ssl.ReloadingX509TrustManager.(ReloadingX509TrustManager.java:79)
> at
> org.apache.hadoop.security.ssl.FileBasedKeyStoresFactory.createTrustManagersFromConfiguration(FileBasedKeyStoresFactory.java:131)
> at
> org.apache.hadoop.security.ssl.FileBasedKeyStoresFactory.init(FileBasedKeyStoresFactory.java:292)
> at org.apache.hadoop.security.ssl.SSLFactory.init(SSLFactory.java:180)
> at
> org.apache.hadoop.hdfs.web.SSLConnectionConfigurator.(SSLConnectionConfigurator.java:50)
> at
> org.apache.hadoop.hdfs.web.URLConnectionFactory.getSSLConnectionConfiguration(URLConnectionFactory.java:100)
> at
> org.apache.hadoop.hdfs.web.URLConnectionFactory.newDefaultURLConnectionFactory(URLConnectionFactory.java:79)
> at org.apache.hadoop.hdfs.server.common.Util.(Util.java:76)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getStorageDirs(FSNamesystem.java:1630)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getNamespaceDirs(FSNamesystem.java:1585)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkConfiguration(FSNamesystem.java:716)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:767)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:681)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:768)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:1020)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:995)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1769)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1834)
> {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-25777) Service Issues in Host Checks incompatible with Centos7 when hosts registered
[ https://issues.apache.org/jira/browse/AMBARI-25777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25777: Epic Link: AMBARI-25792 > Service Issues in Host Checks incompatible with Centos7 when hosts registered > - > > Key: AMBARI-25777 > URL: https://issues.apache.org/jira/browse/AMBARI-25777 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2022-11-10-23-20-06-618.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > `service ntpd status` incompatible with Centos7, it should be `systemctl > status ntpd`. > !image-2022-11-10-23-20-06-618.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-25737) Update pom.xml to ignore dependency-reduced-pom.xml for maven-shade-plugin
[ https://issues.apache.org/jira/browse/AMBARI-25737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25737: Component/s: ambari-agent Epic Link: AMBARI-25792 Affects Version/s: 2.8.0 (was: trunk) > Update pom.xml to ignore dependency-reduced-pom.xml for maven-shade-plugin > -- > > Key: AMBARI-25737 > URL: https://issues.apache.org/jira/browse/AMBARI-25737 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-trunk >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Minor > Fix For: 2.8.0 > > Attachments: pom_20220926093349.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Update pom.xml to ignore dependency-reduced-pom.xml for maven-shade-plugin > The question is as follows: > !pom_20220926093349.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-25776) The `Database Connectivity Warning` is incorrectly reported when Hive is installed in the initial cluster
[ https://issues.apache.org/jira/browse/AMBARI-25776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25776: Epic Link: AMBARI-25792 Affects Version/s: (was: 2.7.5) (was: 2.7.6) > The `Database Connectivity Warning` is incorrectly reported when Hive is > installed in the initial cluster > - > > Key: AMBARI-25776 > URL: https://issues.apache.org/jira/browse/AMBARI-25776 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.8.0 > Environment: Centos-7(x86_64) > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2022-11-10-20-26-14-789.png > > Time Spent: 20m > Remaining Estimate: 0h > > When Hive is installed in the initial cluster, the `Database Connectivity > Warning` is incorrectly reported even though the connection is normal. > !image-2022-11-10-20-26-14-789.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-25783) Fix CI test failed
[ https://issues.apache.org/jira/browse/AMBARI-25783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou updated AMBARI-25783: Component/s: ambari-server Epic Link: AMBARI-25792 > Fix CI test failed > -- > > Key: AMBARI-25783 > URL: https://issues.apache.org/jira/browse/AMBARI-25783 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.8.0 > Environment: ambari-2.8.0 > centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2022-11-19-20-59-12-469.png > > Time Spent: 20m > Remaining Estimate: 0h > > !image-2022-11-19-20-59-12-469.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
