Mingjie Tang created AMBARI-22728:
-------------------------------------
Summary: Ambari is monitoring the wrong Spark Thrift Server and
Spark2 Thrift Server ports when using HTTP transport.
Key: AMBARI-22728
URL: https://issues.apache.org/jira/browse/AMBARI-22728
Project: Ambari
Issue Type: Bug
Reporter: Mingjie Tang
When we are using HTTP transport for the Spark Thrift Server and Spark2 Thrift
Servers.
Looking at the
/var/lib/ambari-server/resources/common-services/SPARK2/2.0.0/package/scripts/alerts/alert_spark2_thrift_port.py
and
/var/lib/ambari-server/resources/common-services/SPARK/1.2.1/package/scripts/alerts/alert_spark_thrift_port.py
scripts, they ignore what the cluster administrator has configured
hive.server2.thrift.port when http transport is set, and completely ignores
what is set in
hive.server2.thrift.http.port.
This causes a false alarm unless you change your http port to what the scripts
default to
(10002 in Spark2 and 10001 in Spark).
This is not an ideal solution, especially in cases where the Spark Thrift
Server is going to be co-located on the same host as a HiveServer2 because it's
likely to result in a port conflict.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
