{"action":"created","issue":{"url":"https://api.github.com/repos/apache/spark/issues/6082","labels_url":"https://api.github.com/repos/apache/spark/issues/6082/labels{/name}","comments_url":"https://api.github.com/repos/apache/spark/issues/6082/comments","events_url":"https://api.github.com/repos/apache/spark/issues/6082/events","html_url":"https://github.com/apache/spark/pull/6082","id":75600180,"number":6082,"title":"[SPARK-7533] [YARN] Decrease spacing between AM-RM heartbeats.","user":{"login":"ehnalis","id":8371789,"avatar_url":"https://avatars.githubusercontent.com/u/8371789?v=3","gravatar_id":"","url":"https://api.github.com/users/ehnalis","html_url":"https://github.com/ehnalis","followers_url":"https://api.github.com/users/ehnalis/followers","following_url":"https://api.github.com/users/ehnalis/following{/other_user}","gists_url":"https://api.github.com/users/ehnalis/gists{/gist_id}","starred_url":"https://api.github.com/users/ehnalis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ehnalis/subscriptions","organizations_url":"https://api.github.com/users/ehnalis/orgs","repos_url":"https://api.github.com/users/ehnalis/repos","events_url":"https://api.github.com/users/ehnalis/events{/privacy}","received_events_url":"https://api.github.com/users/ehnalis/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-05-12T13:23:18Z","updated_at":"2015-05-14T00:01:06Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/apache/spark/pulls/6082","html_url":"https://github.com/apache/spark/pull/6082","diff_url":"https://github.com/apache/spark/pull/6082.diff","patch_url":"https://github.com/apache/spark/pull/6082.patch"},"body":"Added faster RM-heartbeats on pending container allocations with multiplicative back-off.\r\nAlso updated related documentations."},"comment":{"url":"https://api.github.com/repos/apache/spark/issues/comments/101854622","html_url":"https://github.com/apache/spark/pull/6082#issuecomment-101854622","issue_url":"https://api.github.com/repos/apache/spark/issues/6082","id":101854622,"user":{"login":"tgravescs","id":4563792,"avatar_url":"https://avatars.githubusercontent.com/u/4563792?v=3","gravatar_id":"","url":"https://api.github.com/users/tgravescs","html_url":"https://github.com/tgravescs","followers_url":"https://api.github.com/users/tgravescs/followers","following_url":"https://api.github.com/users/tgravescs/following{/other_user}","gists_url":"https://api.github.com/users/tgravescs/gists{/gist_id}","starred_url":"https://api.github.com/users/tgravescs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tgravescs/subscriptions","organizations_url":"https://api.github.com/users/tgravescs/orgs","repos_url":"https://api.github.com/users/tgravescs/repos","events_url":"https://api.github.com/users/tgravescs/events{/privacy}","received_events_url":"https://api.github.com/users/tgravescs/received_events","type":"User","site_admin":false},"created_at":"2015-05-14T00:01:06Z","updated_at":"2015-05-14T00:01:06Z","body":"I agree it should be automated or have reasonable default (5 is definitely high), but I think there are so many different configs and possible setups that is very hard to do based on the current yarn RM.  How fast you get containers is factor of to many things - nm heartbeats, size of cluster, load on cluster, etc.\r\nWe could just change default to 1 second like MR and have folks like myself change our default to be higher for our clusters.  \r\nI'm not necessarily against this, my question is how useful is it in the current form or could it be better?  For instance, have we run any tests wit this?  Does using the backoff differ any then having 2 configs and setting one 1 second and the other (when I don't need containers) to 3 or 5 seconds?  The difference there is in 1400ms I heartbeat in 3 times compared to 1 time in 1 second.   How does that affect the overall job time?  In this case I'm assuming we are mostly concerned with small jobs as a few seconds in large jobs shouldn't show up.  It would be nice to see some numbers on that.  If my job is delayed even a few seconds then this doesn't have any affect at all.  So if I run a simple test being second in the queue where the first app is asking for containers I assume this does nothing?     Could it better having the 2 configs where it heartbeats faster when I need containers but still doesn't overwhelm RM.\r\n\r\nIf there is a difference great, lets go with this, if not is it really necessarily or is there a better option.   Then the question comes down to RM load.  If we do end up heartbeating in every 1 second does that hurt the RM. This again is going to be very cluster dependent.  I would guess on most small and medium clusters its fine.   Folks with larger clusters can configure it up slightly.\r\n"}}