See ZookeeperConsumerConnectorTest.
Thanks,
Jun
On Fri, Dec 12, 2014 at 3:59 PM, Shannon Lloyd wrote:
> Hi Jun,
>
> Thanks for that - can you point me to one of your tests that does this?
> i.e. a test which shuts down the consumer and then re-initialises it (or
> rather creates a new consumer
Hi Jun,
Thanks for that - can you point me to one of your tests that does this?
i.e. a test which shuts down the consumer and then re-initialises it (or
rather creates a new consumer with the same config) and then uses it? I'd
be keen to see what settings (properties) you're using. Maybe I've just
Hmm, that's what we do in our unit tests and it seems that we can cleanly
shutdown the consumer.
Thanks,
Jun
On Mon, Dec 8, 2014 at 9:17 PM, Shannon Lloyd wrote:
> Not explicitly. Some additional background might help. I'm running an
> integration test using an embedded Kafka cluster and ZK qu
Not explicitly. Some additional background might help. I'm running an
integration test using an embedded Kafka cluster and ZK quorum (ie all in
process). In my @Before method I fire up the cluster. In my @After method I
shut the cluster down. When I call shutdown on the connector during my
test, th
kafka.network.Processor is on the broker. Are you killing the brokers as
well?
Thanks,
Jun
On Thu, Dec 4, 2014 at 5:33 PM, Shannon Lloyd wrote:
> Hi,
>
> I am using the high-level consumer on 0.8.2-beta. I'm attempting to close a
> ConsumerConnector (actually a handful of connectors), but am n
