[
https://issues.apache.org/jira/browse/YARN-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484624#comment-16484624
]
Billie Rinaldi commented on YARN-8316:
--------------------------------------
The issue here appears to be that the YarnClient is throwing a
RuntimeException, and the ApiServer is not catching RuntimeException. I think
we can solve this issue by having the YarnClient throw an IOException when the
timeline server isn't running, instead of a RuntimeException.
{noformat}
2018-05-17 13:26:06,073 WARN webapp.GenericExceptionHandler
(GenericExceptionHandler.java:toResponse(98)) - INTERNAL_SERVER_ERROR
java.lang.RuntimeException: Failed to connect to timeline server. Connection
retries limit exceeded. The posted timeline event may be missing
at
org.apache.hadoop.yarn.client.api.impl.TimelineConnector$TimelineClientConnectionRetry.retryOn(TimelineConnector.java:357)
at
org.apache.hadoop.yarn.client.api.impl.TimelineConnector.operateDelegationToken(TimelineConnector.java:218)
at
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.getDelegationToken(TimelineClientImpl.java:212)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.getTimelineDelegationToken(YarnClientImpl.java:396)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.addTimelineDelegationToken(YarnClientImpl.java:363)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:282)
at
org.apache.hadoop.yarn.service.client.ServiceClient.submitApp(ServiceClient.java:802)
at
org.apache.hadoop.yarn.service.client.ServiceClient.actionCreate(ServiceClient.java:344)
at
org.apache.hadoop.yarn.service.webapp.ApiServer$2.run(ApiServer.java:144)
at
org.apache.hadoop.yarn.service.webapp.ApiServer$2.run(ApiServer.java:138)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1682)
at
org.apache.hadoop.yarn.service.webapp.ApiServer.createService(ApiServer.java:138)
{noformat}
> Diagnostic message should improve when yarn service fails to launch due to
> ATS unavailability
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-8316
> URL: https://issues.apache.org/jira/browse/YARN-8316
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-native-services
> Affects Versions: 3.1.0
> Reporter: Yesha Vora
> Assignee: Billie Rinaldi
> Priority: Major
>
> Scenario:
> 1) shutdown ATS
> 2) launch yarn service.
> yarn service launch cmd fails with below stack trace. There is no diagnostic
> message available in response.
> {code:java}
> bash-4.2$ yarn app -launch hbase-sec /tmp/hbase-secure.yar
> WARNING: YARN_LOGFILE has been replaced by HADOOP_LOGFILE. Using value of
> YARN_LOGFILE.
> WARNING: YARN_PID_DIR has been replaced by HADOOP_PID_DIR. Using value of
> YARN_PID_DIR.
> 18/05/17 13:24:43 INFO client.RMProxy: Connecting to ResourceManager at
> xxx/xxx:8050
> 18/05/17 13:24:44 INFO client.AHSProxy: Connecting to Application History
> server at localhost/xxx:10200
> 18/05/17 13:24:44 INFO client.RMProxy: Connecting to ResourceManager at
> xxx/xxx:8050
> 18/05/17 13:24:44 INFO client.AHSProxy: Connecting to Application History
> server at localhost/127.0.0.1:10200
> 18/05/17 13:24:44 INFO client.ApiServiceClient: Loading service definition
> from local FS: /tmp/hbase-secure.yar
> 18/05/17 13:26:06 ERROR client.ApiServiceClient:
> bash-4.2$ echo $?
> 56{code}
> The Error message should provide ConnectionRefused exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
