[
https://issues.apache.org/jira/browse/AMBARI-24232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530223#comment-16530223
]
Hudson commented on AMBARI-24232:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9560 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9560/])
AMBARI-24232 Alert definitions have not updated after stack upgrade
(hapy.lestat:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f8f46deea10e18597f8d1c2e3a703c480970e12b])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/StackUpgradeFinishListenerTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackUpgradeFinishListener.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
> Alert definitions have not updated after stack upgrade
> ------------------------------------------------------
>
> Key: AMBARI-24232
> URL: https://issues.apache.org/jira/browse/AMBARI-24232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Dmytro Grinenko
> Assignee: Dmytro Grinenko
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> After Stack upgrade , an alert is seen for Hive Metastore with following
> error:
> {code:java}
> Metastore on ctr-e138-1518143905142-380941-01-000006.hwx.site failed
> (Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_metastore.py",
> line 203, in execute
> timeout_kill_strategy=TerminateStrategy.KILL_PROCESS_TREE,
> 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 263, 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)
> ExecutionFailed: Execution of 'export
> HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf' ; hive --hiveconf
> hive.metastore.uris=thrift://ctr-e138-1518143905142-380941-01-000006.hwx.site:9083
> --hiveconf hive.metastore.client.connect.retry.delay=1
> --hiveconf hive.metastore.failure.retries=1
> --hiveconf hive.metastore.connect.retries=1 --hiveconf
> hive.metastore.client.socket.timeout=14 --hiveconf
> hive.execution.engine=mr -e 'show databases;'' returned 1. ########
> Hortonworks #############
> This is MOTD message, added for testing in qe infra
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/grid/0/hdp/3.0.0.0-1554/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/grid/0/hdp/3.0.0.0-1554/hadoop/lib/slf4j-log4j12-1.7.25.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]
> Hive-on-MR is deprecated in Hive 2 and may not be available in the future
> versions. Consider using a different execution engine (i.e. spark, tez) or
> using Hive 1.X releases.
> Connecting to
> jdbc:hive2://ctr-e138-1518143905142-380941-01-000003.hwx.site:2181,ctr-e138-1518143905142-380941-01-000002.hwx.site:2181,ctr-e138-1518143905142-380941-01-000007.hwx.site:2181,ctr-e138-1518143905142-380941-01-000004.hwx.site:2181/default;principal=hive/[email protected];serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2
> 18/06/27 10:37:10 [main]: INFO jdbc.HiveConnection: Connected to
> ctr-e138-1518143905142-380941-01-000006.hwx.site:10000
> 18/06/27 10:37:10 [main]: WARN jdbc.HiveConnection: Failed to connect to
> ctr-e138-1518143905142-380941-01-000006.hwx.site:10000
> 18/06/27 10:37:10 [main]: ERROR jdbc.Utils: Unable to read HiveServer2
> configs from ZooKeeper
> Error: Could not open client transport for any of the Server URI's in
> ZooKeeper: Failed to open new session: java.lang.IllegalArgumentException:
> Cannot modify hive.metastore.client.connect.retry.delay at runtime. It is not
> in list of params that are allowed to be modified at runtime
> (state=08S01,code=0)
> Cannot run commands specified using -e. No current connection
> )
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
