[KUDU-560] Consensus/WAL/Transactions Optimizations and tests

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: M4.5
• Component/s: consensus, log
• Labels: roadmap-candidate
• Target Version/s: 1.8.0
• Assignee: Unassigned
• Reporter: David Alves
• Created: 04/Dec/14 20:06
• Updated: 18/Jun/19 13:02

Description

This is an umbrella jira for several optimization and tests that we should add in the near future.

Sub-Tasks

• Don't need to block on COMMIT before sending write responses: Resolved
• Clean up repeated code in ConsensusQueue dump functions: Resolved
• Refactor/Rename consensus terminology: Resolved
• Consider splitting the WAL in two, one for replicated operations and one for local operations: Open
• On boot make sure to discard the prefix of segments without operations with ids: Resolved
• Leader should proactively propagate commitIndex to followers: Resolved
• On Log appends, allow to specify if an fsync is required per message: Resolved
• Make LogCache more flexible with regard to what it keeps in memory: Resolved
• When a peer is partitioned, it should ask a majority if they still think the leader is alive: Resolved
• Consensus logging improvements for better operability: Open
• Remove 'update_lock_' from consensus: Open
• Don't trigger elections when waiting for our own Log: Resolved
• Exactly-once semantics on writes: Resolved
• Enable failure detection/leader election by default: Resolved
• Investigate "optimization" where LMP mismatch is handled in two places: Open