RunOnSpark sanity check queries fail with timeouts and User sparkJobSubmitter not found - Aster Analytics

Teradata AsterĀ® Spark Connector User Guide

Product
Aster Analytics
Release Number
7.00.00.01
Published
May 2017
Language
English (United States)
Last Update
2018-04-13
dita:mapPath
dbt1482959363906.ditamap
dita:ditavalPath
Generic_no_ie_no_tempfilter.ditaval
dita:id
dbt1482959363906
lifecycle
previous
Product Category
Software
Problem: RunOnSpark sanity check queries fail with:
SQL-MR function RUNONSPARK failed: Timeout exceeded.
On the HDP Hadoop Spark side, browsing Ambari (YARN > Quick Links > Resource Manager UI > Applications) shows that RunOnSpark-initiated Spark jobs fail with:
Application application_1479228852593_0001 failed 2 times due to AM Container for appattempt_1479228852593_0001_000002 exited with exitCode: -1000
For more detailed output, check application tracking page:http://hrh050m1.labs.teradata.com:8088/cluster/app/application_1479228852593_0001Then, click on links to logs of each attempt.
Diagnostics: Application application_1479228852593_0001 initialization failed (exitCode=255) with output:
main : command provided 0
main : run as user is sparkJobSubmittermain : requested yarn user is sparkJobSubmitter
User sparkJobSubmitter not foundFailing this attempt.
Failing the application.

Solution: Create sparkJobSubmitter as a cluster-wise userid.