Looks exactly like all the similar issues, this time there's no deadlock, probably a different root cause. Internal app IDs application_1431919257083_3137 and application_1431919257083_3133, logs upon request. This time there's no deadlock. The hypothesis during discussion was that shared hashtable loader got preempted and those waiting for this hashtable run forever. May be something else.