[KAFKA-5366] Add cases for concurrent transactional reads and writes in system tests

• Type: Test
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.11.0.0
• Fix Version/s: 0.11.0.0
• Labels: exactly-once
• Assignee: Apurva Mehta
• Reporter: Apurva Mehta
• Created: 02/Jun/17 07:05
• Updated: 07/Jun/17 00:24
• Resolved: 07/Jun/17 00:23

Description

Currently the transactions system test does a transactional copy while bouncing brokers and clients, and then does a verifying read on the output topic to ensure that it exactly matches the input.

We should also have a transactional consumer reading the tail of the output topic as the writes are happening, and then assert that the values it reads also exactly match the values in the source topics.

This test really exercises the abort index, and we don't have any of them in the system or integration tests right now.

Issue Links

• links to: GitHub Pull Request #3217