GitHub user benstopford opened a pull request:
https://github.com/apache/kafka/pull/667
KAFKA-2964: Split Security Rolling Upgrade Test by Client and Broker
Protocols
The core of this test is to ensure we evaluate enabling security in a
running cluster where we have different broker and client protocols.
Also in this PR are some improvements to the validation process in
produce_consume_validate.py:
- Fail fast if producer or consumer stop running.
- If messages go missing, check in the data files to see if the cause was
data loss or the consumer missing messages.
- Remove unnecessary sleeps which hide problem with consumer disconnection.
- Make it possible for the ConsoleConsumer to optionally log both what it
consumed and when it consumed it.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/benstopford/kafka
security-rolling_upgrade-additions
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/667.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #667
----
commit c0ae7f29b8381d83870bb56d4312a4897c77944e
Author: Ben Stopford <benstopf...@gmail.com>
Date: 2015-12-08T21:27:01Z
KAFKA-2964: Parameterise security rolling upgrade so it runs independetly
for broker-broker and broker-client protocols.
commit 03740f9fd21c05eb8eb3492ac3ce35efa1f9428a
Author: Ben Stopford <benstopf...@gmail.com>
Date: 2015-12-10T19:38:44Z
KAFKA-2964: Check for data loss if messages go missing
commit 9640d3efaeb0a0ef549b3a8c5a758bfde60ace30
Author: Ben Stopford <benstopf...@gmail.com>
Date: 2015-12-10T22:34:31Z
KAFKA-2964: Refactored produce_consume_validate
commit bd53895892d7938f17975298f1380739a2f45504
Author: Ben Stopford <benstopf...@gmail.com>
Date: 2015-12-11T09:21:12Z
KAFKA-2964: clean up
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
