[KUDU-1035] Crash in tablet bootstrap due to out of order timestamp on consensus-only op

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Feature Complete
• Component/s: consensus
• Target Version/s: Public beta
• Code Review: http://gerrit.sjc.cloudera.com:8080/#/c/7545/
• Assignee: Mike Percy
• Reporter: Mike Percy
• Created: 19/Aug/15 05:19
• Updated: 29/Feb/16 09:32
• Resolved: 21/Aug/15 18:12

Description

Tablet bootstrap assumes that it can move the offline safe time any time a transaction commits, however it considers consensus-only operations such as NO_OP and CHANGE_CONFIG_OP to be included in this as well. This is no longer a safe assumption, because we do not assign the timestamps for these operations on the prepare thread like we do for the tablet transactions.

The fix is to exclude consensus-only operations from tablet bootstrap's safe time advancement logic.

Issue Links

• relates to: KUDU-1042 Consider serializing timestamp assignment for non-tablet operations