Re: Connection to zk shell on Kafka

You need the jline JAR file that ships with ZooKeeper. Chris IBM Tivoli Systems Research Triangle Park, NC (919) 224-2240 Internet: barl...@us.ibm.com From: Prabhjot Bharaj prabhbha...@gmail.com To: users@kafka.apache.org, u...@zookeeper.apache.org Date: 07/29/2015 01:13 PM Subject:

Re: Connection to zk shell on Kafka

0.8.2 does not have the jline jar Regards, prabcs On Wed, Jul 29, 2015 at 10:45 PM, Chris Barlock barl...@us.ibm.com wrote: You need the jline JAR file that ships with ZooKeeper. Chris IBM Tivoli Systems Research Triangle Park, NC (919) 224-2240 Internet: barl...@us.ibm.com From

Re: Invalid Version for API key

rigger this error log? On Wed, Jun 8, 2016 at 9:39 AM, Chris Barlock <barl...@us.ibm.com> wrote: > Anyone? Is there additional tracing that can be turned on to track down > the source of these exceptions? > > Chris > > > > > From: Chris Barlock/Raleigh/IBM@IBMUS > T

Re: Invalid Version for API key

y Sent by:isma...@gmail.com Hi Chris, The error includes the IP address of the client: 172.20.3.0:53901 Would that help identify the client? We are not aware of issues with the built-in clients. Ismael On Wed, Jun 8, 2016 at 4:13 PM, Chris Barlock <barl...@us.ibm.com> wrote: > I

Re: Invalid Version for API key

Chris. Out of curiosity, which Kafka client was being used by this microservice? Ismael On 8 Jun 2016 18:54, "Chris Barlock" <barl...@us.ibm.com> wrote: > Thanks, Ismael. We tracked it down to one of the 11 microservices running > on this system. > > Thank you,

Invalid Version for API key

We are running some tests on upgrading from Kafka 2.10-0.8.2.1 to 2.11-0.10.00. So far, we only upgraded the server. All of the clients that I could verify are still using the Maven kafka-clients version 0.8.2.1. There are a number of exceptions in the server.log: [2016-06-07 16:00:00,266]

Re: Invalid Version for API key

Anyone? Is there additional tracing that can be turned on to track down the source of these exceptions? Chris From: Chris Barlock/Raleigh/IBM@IBMUS To: users@kafka.apache.org Date: 06/07/2016 12:45 PM Subject:Invalid Version for API key We are running some tests

Consumer Question

If you have a consumer listening on a topic and that topic is deleted is the consumer made aware -- perhaps by some exception -- or does it continue listening, blissfully unaware that it will never hear anything more? Thanks, Chris

Re: Consumer Question

Nicole On Sat, Jun 18, 2016 at 1:55 AM, Chris Barlock <barl...@us.ibm.com> wrote: > If you have a consumer listening on a topic and that topic is deleted is > the consumer made aware -- perhaps by some exception -- or does it > continue listening, blissfully unaware that it will never

Re: AdminUtils

he API of `AdminClient` hasn't been discussed yet, but it should be possible to support the methods you mentioned. Maybe you can provide your feedback as the KIP-4 discussions happen in kafka-dev? Ismael On Tue, Jun 21, 2016 at 10:39 PM, Chris Barlock <barl...@us.ibm.com> wrote: > While working on

AdminUtils

While working on upgrading from 0.8.2.1 to 0.10.0.0, I found out that AdminUtils has changed -- and not in a backwards-compatible manner. I gather this is not a public API since I can't find any Javadoc for it. So, in 0.10.0.0 are there public replacements for:

Producer Properties

I started porting our code from Kafka 0.8.2.1 to 0.10.0.0 and found my producer code blowing up because of some changes to the config. For example, metadata.broker.list is now bootstrap.servers. I discovered the ProducerConfig class which has, at least, some of the config keys. Before I

TopicMetadata Question

Starting with Kafka 0.8.2.1, we have some code that call AdminUtils.fetchTopicMetadataFromZk. This returned a kafka.api.TopicMetadata object which provided some useful information about the topic. With 0.10.0.0, fetchTopicMetadataFromZk returns

Re: TopicMetadata Question

Chris IBM Middleware Research Triangle Park, NC (919) 224-2240 Internet: barl...@us.ibm.com From: Radoslaw Gruchalski <ra...@gruchalski.com> To: Chris Barlock/Raleigh/IBM@IBMUS, users@kafka.apache.org Date: 07/26/2016 03:10 PM Subject:Re: TopicMetadata Question Chris, There is a

Re: release of 0.10.1

So this begs the question -- why doesn't Kafka join the mainstream and have a 1.0 release? The 0.x versioning makes one think that this code is, at best, beta. Chris From: Ewen Cheslack-Postava To: "users@kafka.apache.org" Date:

Expose Kafka Server Configuration

Does Kafka expose its server configuration in any way that I can get it programmatically? Specifically, I'm interested in knowing the message.max.bytes value. Chris

Compatibility question

Can the kafka-clients Maven bundle at version 0.8.2.1 be used to communicate with a Kafka 0.10.0.0 server? Chris

Re: Producer Properties

tp://kafka.apache.org/081/documentation.html. Hope that helps From: users@kafka.apache.org At: 06/27/16 09:34:55 To: users@kafka.apache.org Subject: Re: Producer Properties Anybody? Chris From: Chris Barlock/Raleigh/IBM@IBMUS To: users@kafka.apache.org Date: 06/24/2016 04:56 PM Subject:

Re: Producer Properties

Anybody? Chris From: Chris Barlock/Raleigh/IBM@IBMUS To: users@kafka.apache.org Date: 06/24/2016 04:56 PM Subject:Producer Properties I started porting our code from Kafka 0.8.2.1 to 0.10.0.0 and found my producer code blowing up because of some changes to the config

Something Bad Happened

I started getting the following errors on all topics: root@kafka-1-bw3ys:/opt/kafka/bin# ./kafka-console-consumer.sh --topic systemconfig --from-beginning --zookeeper $ZOOKEEPER_URL [2016-06-20 23:43:27,460] WARN Fetching topic metadata with correlation id 0 for topics [Set(systemconfig)] from

kafka.consumers Java Package

I was trying to move some of our Kafka client code from kafka_2.11_0.10.2.2 to kafka_2.11_2.0.0. However, we have some code that uses code in the kafka.consumer package. That appears to be either moved or removed from kafka_2.11_2.0.0. Is it gone or moved? Thanks! Chris

Re: kafka.consumers Java Package

are not public API? What classes specifically are not > available. > > -Harsha > On Nov 9, 2018, 7:47 AM -0800, Chris Barlock , wrote: > > I was trying to move some of our Kafka client code from > > kafka_2.11_0.10.2.2 to kafka_2.11_2.0.0. However, we have some code that &