I'm not sure if we've been doing it wrong, but after changing our yarn jobs the problem went away, could have been an issue at our end. Although I still have this feeling in the back of my head that the "yarn.resourcemanager.scheduler.address" should be something else than a specific node, it should be the "yarn-cluster" address. But this might be an ambari-problem. Thanks for your time! ... View more