[jira] [Commented] (YARN-1547) Prevent DoS of ApplicationMasterProtocol by putting in limits

["Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>]

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

Vinod Kumar Vavilapalli commented on YARN-1547:
-----------------------------------------------

bq. Thanks for raising this Vinod Kumar Vavilapalli. I was wondering if I might take this up, if you are not actively working on it. 
Tx [~giovanni.fumarola], please go ahead and assign it to yourselves!

We can discuss after you have a design, but wanted to bring up one point of note w.r.t this ticket and the larger YARN-1545 itself.

It is likely that we can solve 60-70% of our use-case of avoiding accidental DoS'ing by well-behaved apps by way of putting limits in the client, but it is imperative that we handle this on the server-side instead of on client-side, lest an abusive client can circumvent any client-side restrictions.

> Prevent DoS of ApplicationMasterProtocol by putting in limits
> -------------------------------------------------------------
>
>                 Key: YARN-1547
>                 URL: https://issues.apache.org/jira/browse/YARN-1547
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
>
> Points of DoS in ApplicationMasterProtocol
>  - Host and trackingURL in RegisterApplicationMasterRequest
>  - Diagnostics, final trackingURL in FinishApplicationMasterRequest
>  - Unlimited number of resourceAsks, containersToBeReleased and resourceBlacklistRequest in AllocateRequest
>     -- Unbounded number of priorities and/or resourceRequests in each ask.



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