[
https://issues.apache.org/jira/browse/KAFKA-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256574#comment-14256574
]
Joe Stein commented on KAFKA-1822:
----------------------------------
Can we utilize the ClusterMetadataRequest and ClusterMetadataResponse in the
new command line patch https://issues.apache.org/jira/browse/KAFKA-1694 for
this? The use there is to contact any broker to find the controller for then
admin use. You could just use it also as a ping to make sure you get response
from every broker like you are saying. This controller is thin since everything
for the new admin interface will then go to the broker that is the controller
through the adminHandler post this call.
> Add "echo" request
> ------------------
>
> Key: KAFKA-1822
> URL: https://issues.apache.org/jira/browse/KAFKA-1822
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Gwen Shapira
> Assignee: Gwen Shapira
> Fix For: 0.8.3
>
>
> Currently there is no simple way to generate a request and validate we
> receive a response without adding a lot of dependencies for the test.
> Kafka request classes have quite a few dependencies, so they are not really
> usable when testing infrastructure components or clients.
> Generating a byte-array with meaningless request key id as it is done in
> SocketServerTest results in unknown request exception that must be handled.
> I suggest adding an EchoRequest, EchoResponse and EchoHandler. The Request
> will be the usual header and a bytearray. The Response will be a response
> header and the same bytearray echoed back.
> Should be useful for client developers and when testing infrastructure
> changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
