[BOOKKEEPER-199] Provide bookie readonly mode, when journal/ledgers flushing has failed with IOE

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Implemented
• Affects Version/s: 4.0.0
• Component/s: bookkeeper-server
• Assignee: Vinayakumar B
• Reporter: Rakesh Radhakrishnan
• Created: 30/Mar/12 12:18
• Updated: 02/May/13 02:29
• Resolved: 04/Dec/12 14:49

Description

Bookkeeper should change to readonly(r-o) mode when the journal/ledgers flushing has failed with IOException. Later on, reject write requests on server side and will accept only the read requests from the clients, because even if flushing fails, the data in the bookie which has been flushed is still valid.

Issue Links

• is depended upon by: BOOKKEEPER-126 EntryLogger doesn't detect when one of it's logfiles is corrupt
• is related to: BOOKKEEPER-126 EntryLogger doesn't detect when one of it's logfiles is corrupt

Sub-Tasks

• Utility functions for checking disk problem: Resolved
• Detect IOExceptions on entrylogger and bookie should consider next ledger dir(if any): Closed
• Detect IOExceptions in LedgerCache and bookie should look at next ledger dir(if any): Closed
• Provide mechanism to detect r-o bookie by the bookie clients: Closed