MENG DING commented on YARN-4495:

I guess my point is if you are not going to do any automated action upon 
exception, it might be sufficient to just look at AM log to see why a resource 
request has failed via the exception message. The key point we are addressing 
here is to not let AMRMClientAsync stop while invalid resource request 
exception occurs, which is fatal to user logic.

If you have use case to do automated actions based on various failed reasons, 
then it may be needed to enhance the protocol, which I believe the community 
tend not to do unless absolutely necessary.

> 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

Reply via email to