[ 
https://issues.apache.org/jira/browse/KAFKA-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben Stopford updated KAFKA-3223:
--------------------------------
    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 

  was:
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.

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


> Add System (ducktape) Test that asserts strict partition ordering despite 
> node failure
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-3223
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3223
>             Project: Kafka
>          Issue Type: Test
>            Reporter: Ben Stopford
>
> 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 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to