Dmytro Vitiuk commented on AMBARI-25502:

[~jprey] Hi, I tried to setup 2.7.5 cluster which contains spark2 with enabled 
ssl. Service check works fine for me:
2020-04-15 10:35:23,262 - Using hadoop conf dir: 
2020-04-15 10:35:23,277 - Execute['curl -s -o /dev/null -w'%{http_code}' 
--negotiate -u: -k https://c7403.ambari.apache.org:18481 | grep 200'] 
{'logoutput': True, 'tries': 5, 'user': 'ambari-qa', 'try_sleep': 3}
2020-04-15 10:35:23,480 - Execute['! /usr/hdp/current/spark2-client/bin/beeline 
-u 'jdbc:hive2://c7403.ambari.apache.org:10016/default;transportMode=binary'  
-e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL' -e 
'Error: Could not open''] {'path': 
[u'/usr/hdp/current/spark2-client/bin/beeline'], 'user': 'ambari-qa', 
'timeout': 60.0}

Command completed successfully!
Also I checked that redirect to port spark.history.ui.port + 400 in the case 
when SSL is enabled is built-in feature of spark2.
Could you please provide the content of 
*/usr/hdp/current/spark2-historyserver/conf/spark-defaults.conf* from the host 
with Spark History server, out of service check where you faced the issue and 
steps which you used to enable ssl for spark2?

> Spark2 service check fails when SSL is enabled
> ----------------------------------------------
>                 Key: AMBARI-25502
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25502
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.7.5
>            Reporter: Jesus Perez Rey
>            Assignee: Dmytro Grinenko
>            Priority: Major
> AMBARI-18091 fixed Spark2 service check to use the correct URL scheme (HTTPS) 
> to connect to Spark2 History Server when SSL is enabled. But also, for some 
> reason that I can't understand, it adds 400 to spark_history_ui_port` when 
> connecting if SSL is enabled:
> {code:java}
> if ui_ssl_enabled:
>   spark_history_ui_port = str(int(spark_history_ui_port) + 400){code}
> So if SSL is enabled and `spark_history_ui_port` is 18081, the service check 
> will actually try to connect to port 18481 and will fail.
> I know the stacks where removed from Ambari, but this is still affecting the 
> latest stable version available to download.

This message was sent by Atlassian Jira

Reply via email to