You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Stanislav Kozlovski (JIRA)" <ji...@apache.org> on 2018/12/31 17:53:00 UTC
[jira] [Resolved] (KAFKA-7564) Trogdor - Expose single task details
from Trogdor Coordinator
[ https://issues.apache.org/jira/browse/KAFKA-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stanislav Kozlovski resolved KAFKA-7564.
----------------------------------------
Resolution: Fixed
> Trogdor - Expose single task details from Trogdor Coordinator
> -------------------------------------------------------------
>
> Key: KAFKA-7564
> URL: https://issues.apache.org/jira/browse/KAFKA-7564
> Project: Kafka
> Issue Type: Improvement
> Reporter: Stanislav Kozlovski
> Assignee: Stanislav Kozlovski
> Priority: Minor
>
> The only way to currently get the results from tasks ran in Trogdor is through listing all of them via the "--show-tasks" CLI command
> {code:java}
> ./bin/trogdor.sh client --show-tasks localhost:8889 Got coordinator tasks:
> { "tasks":{ "produce_bench_20462":{ "state":"DONE", "spec":{ "class":"org.apache.kafka.trogdor.workload.ProduceBenchSpec", "startMs":0, "durationMs":10000000, "producerNode":"node0", "bootstrapServers":"localhost:9092", "targetMessagesPerSec":10, "maxMessages":100, "keyGenerator":{ "type":"sequential", "size":4, "startOffset":0 }, "valueGenerator":{ "type":"constant", "size":512, "value":"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=" }, "totalTopics":10, "activeTopics":5, "topicPrefix":"foo", "replicationFactor":1, "classLoader":{ }, "numPartitions":1 }, "startedMs":1523552769850, "doneMs":1523552780878, "cancelled":false, "status":{ "totalSent":500, "averageLatencyMs":4.972, "p50LatencyMs":4, "p95LatencyMs":6, "p99LatencyMs":12 } } } }
> {code}
> This can prove inefficient and annoying if the Trogdor Coordinator is long-running and we only want to get the results from a specific task.
> The current REST endpoint ("/tasks") for listing tasks enables filtering through StartTimeMs/EndTimeMs and supplying specific TaskIDs, but it would be cleaner if we had a specific endpoint for fetching a single task. That endpoint would also return a 404 in the case where no task was found instead of an empty response as the /tasks endpoint would.
> I propose we expose a new "/tasks/:id" endpoint and a new cli command "--show-task TASK_ID"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)