[HDFS-3726] QJM: if a logger misses an RPC, don't retry that logger until next segment

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: QuorumJournalManager (HDFS-3077)
• Fix Version/s: QuorumJournalManager (HDFS-3077)
• Component/s: ha
• Target Version/s: QuorumJournalManager (HDFS-3077)
• Hadoop Flags: Reviewed
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 26/Jul/12 01:08
• Updated: 06/Sep/12 17:00
• Resolved: 06/Sep/12 07:00

Description

Currently, if a logger misses an RPC in the middle of a log segment, or misses the startLogSegment RPC (eg it was down or network was disconnected during that time period), then it will throw an exception on every subsequent journal() call in that segment, since it knows that it missed some edits in the middle.

We should change this exception to a specific IOE subclass, and have the client side of QJM detect the situation and stop sending IPCs until the next startLogSegment call.

This isn't critical for correctness but will help reduce log spew on both sides.