[MAPREDUCE-4707] Add a comment to explain why FairScheduler#dump()'s body is synchronized on eventLog

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Won't Fix
• Affects Version/s: 1.0.3
• Component/s: contrib/fair-share
• Assignee: Karthik Kambatla
• Reporter: Karthik Kambatla
• Created: 05/Oct/12 07:58
• Updated: 03/Nov/14 18:33
• Resolved: 07/Jun/13 03:49

Description

FairScheduler#dump() is a synchronized method. In addition to that, the entire method body is in a synchronized block on eventLog. However, there is no other portion of the code that tries to acquire a lock on eventLog. So, it seems like the second synchronized block is redundant, and can be removed.