hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid
Date Wed, 30 Dec 2015 13:56:49 GMT

    [ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075043#comment-15075043
] 

sandflee commented on YARN-4495:
--------------------------------

Hi, [~leftnoteasy], I do a simple test throwing a exception with applicationId in ApplicationMasterService#allocate,
and couldn't get applicationId in rpc client. I read the code, and find that exception is
put in rpcHeader only with exceptionName and stackTrack info.

{code:title=RpcHeader.proto}

message RpcResponseHeaderProto {
  required uint32 callId = 1; // callId used in Request
  required RpcStatusProto status = 2;
  optional uint32 serverIpcVersionNum = 3; // Sent if success or fail
  optional string exceptionClassName = 4;  // if request fails
  optional string errorMsg = 5;  // if request fails, often contains strack trace
  optional RpcErrorCodeProto errorDetail = 6; // in case of error
  optional bytes clientId = 7; // Globally unique client ID
  optional sint32 retryCount = 8 [default = -1];
}
{code}


> add a way to tell AM container increase/decrease request is invalid
> -------------------------------------------------------------------
>
>                 Key: YARN-4495
>                 URL: https://issues.apache.org/jira/browse/YARN-4495
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: sandflee
>         Attachments: YARN-4495.01.patch
>
>
> now RM may pass InvalidResourceRequestException to AM or just ignore the change request,
the former will cause AMRMClientAsync down. and the latter will leave AM waiting for the relay.
 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message