kafka/checkstyle
Colin Patrick McCabe 832b096f4f KAFKA-6696 Trogdor should support destroying tasks (#4759)
Implement destroying tasks and workers.  This means erasing all record of them on the Coordinator and the Agent.

Workers should be identified by unique 64-bit worker IDs, rather than by the names of the tasks they are implementing.  This ensures that when a task is destroyed and re-created with the same task ID, the old workers will be not be treated as part of the new task instance.

Fix some return results from RPCs.  In some cases RPCs were returning values that were never used.  Attempting to re-create the same task ID with different arguments should fail.  Add RequestConflictException to represent HTTP error code 409 (CONFLICT) for this scenario.

If only one worker in a task stops, don't stop all the other workers for that task, unless the worker that stopped had an error.

Reviewers: Anna Povzner <anna@confluent.io>, Rajini Sivaram <rajinisivaram@googlemail.com>
2018-04-16 08:51:33 +01:00
..
checkstyle.xml KAFKA-6058: KIP-222; Add Consumer Group operations to Admin API 2018-04-11 14:17:46 -07:00
import-control-core.xml KAFKA-5520: KIP-171; Extend Consumer Group Reset Offset for Stream Application 2017-12-06 11:38:38 -08:00
import-control.xml KAFKA-6058: KIP-222; Add Consumer Group operations to Admin API 2018-04-11 14:17:46 -07:00
java.header MINOR: improve license header check by providing head file instead of (prefix) header regex 2017-02-28 12:35:04 -08:00
suppressions.xml KAFKA-6696 Trogdor should support destroying tasks (#4759) 2018-04-16 08:51:33 +01:00