[KAFKA-3223] Add System (ducktape) Test that asserts strict partition ordering despite node failure

• Type: Test
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Ben Stopford
• Created: 09/Feb/16 10:12
• Updated: 09/Feb/16 10:15

Description

Kafka provides strong ordering when max.inflight.requests.per.connection = 1. There currently exists a bug (patched but not released) against this feature. It's an important feature for many customers so we should add a test to assert that the contract is honoured.

Suggest a similar format to ReassignPartitionsTest (reassign_partitions_test.py) or ReplicationTest (replication_test.py). It should be simply a case of asserting on the order of the messages (which are monotonically increasing numbers in these tests) in each partition with the inflight configuration whilst incurring repeated node failure.

Note that this jira is depended on the merge of KAFKA-3197

Issue Links

• is blocked by: KAFKA-3197 Producer can send message out of order even when in flight request is set to 1.