RE: Kafka producer doesn't produce

Solution: 1. producer.close() needed to be moved out of the for loop. 2. I needed to alter my host file so the IP would resolve. Adaryl "Bob" Wakefield, MBA Principal Mass Street Analytics, LLC 913.938.6685 www.massstreet.net www.linkedin.com/in/bobwakefieldmba Twitter: @BobLovesData -Origina

Re: After upgrading the broker from 0.10.0.1 to 0.10.1.1 SASL is no longer working

Hi Ismael, Thank you for your reply. It is 0.10.0.1. On Tue, Apr 18, 2017 at 12:52 AM Ismael Juma wrote: > Hi Anas, > > > > What is the version of the consumer? > > > > Ismael > > > > On Mon, Apr 17, 2017 at 5:32 PM, Anas Mosaad > > wrote: > > > > > Hi All, > > > > > > We have a customer that

Re: [VOTE] 0.10.2.1 RC1

Dear Kafka Users and Developers, Over the weekend Becket reported a new bug that exists in 0.10.2: https://issues.apache.org/jira/browse/KAFKA-5075 Dong Lin was kind and quick enough to resolve it. While this issue is not a regression, the bug does cause data loss and is therefore a serious one.

Re: Issues upgrading from Kafka 0.8.2.1 to 0.10.2.0

Hi Krishnan, In 0.10.2, there was some consolidation of the message format code and the recompression code path is not as well optimised in the consolidated code (recompression is supposed to be rare now). Not sure if this explains the huge difference you are seeing though. Changing log.message.f

Re: Issues upgrading from Kafka 0.8.2.1 to 0.10.2.0

Hi Ismael, Thanks for the info. If 0.8.2.1 was also uncompressing and recompressing data, do you have any insight as to what would cause higher memory usage on 0.10? On 0.8, we are able to run our brokers with 1GB heap and they work perfectly fine. On 0.10 we are seeing OutOfMemory errors even wi

Re: Issues upgrading from Kafka 0.8.2.1 to 0.10.2.0

Hi Krishnan, 0.8.2.1 brokers also uncompress and recompress data. The ability to avoid recompression was introduced in 0.10.0.0 with a new message format (see KIP-31 and KIP-32). If you change log.message.format.version to 0.10.2, the broker will not uncompress and recompress messages produced by

Re: After upgrading the broker from 0.10.0.1 to 0.10.1.1 SASL is no longer working

Hi Anas, What is the version of the consumer? Ismael On Mon, Apr 17, 2017 at 5:32 PM, Anas Mosaad wrote: > Hi All, > > We have a customer that recently upgraded their brokers to 0.10.1.1. After > upgrade they are unable to consume any messages. Can someone please help > what might be the issue

Re: Kafka streams 0.10.2 Producer throwing exception eventually causing streams shutdown

Thanks! On Tue, Apr 18, 2017, 12:26 AM Eno Thereska wrote: > The RC candidate build is here: > http://home.apache.org/~gwenshap/kafka-0.10.2.1-rc1/ < > http://home.apache.org/~gwenshap/kafka-0.10.2.1-rc1/> > > Eno > > On 17 Apr 2017, at 17:20, Mahendra Kariya > wrote: > > > > Thanks! > > > > In

Re: Kafka streams 0.10.2 Producer throwing exception eventually causing streams shutdown

The RC candidate build is here: http://home.apache.org/~gwenshap/kafka-0.10.2.1-rc1/ Eno > On 17 Apr 2017, at 17:20, Mahendra Kariya wrote: > > Thanks! > > In the meantime, is the jar published somewhere on github or as a part of > build

Re: Kafka Streams - Join synchronization issue

hello Eno, thanks for your support. The two streams are both kstreams. The window is of 1 minute-width until 5 minutes. This is the code: //Other Stream: User Location, is a string with the name of the city the//user is (like "San Francisco") KStreamBuilder builder = new KStreamBuilder(); KStre

After upgrading the broker from 0.10.0.1 to 0.10.1.1 SASL is no longer working

Hi All, We have a customer that recently upgraded their brokers to 0.10.1.1. After upgrade they are unable to consume any messages. Can someone please help what might be the issue? The error being thrown is: Failed to send SSL Close message > [org.apache.kafka.common.network.SslTransportLayer.c

Re: Kafka streams 0.10.2 Producer throwing exception eventually causing streams shutdown

Thanks! In the meantime, is the jar published somewhere on github or as a part of build pipeline? On Mon, Apr 17, 2017 at 9:18 PM, Eno Thereska wrote: > Not yet, but as soon as 0.10.2 is voted it should be. Hopefully this week. > > Eno > > On 17 Apr 2017, at 13:25, Mahendra Kariya > wrote: > >

Re: Kafka streams 0.10.2 Producer throwing exception eventually causing streams shutdown

Not yet, but as soon as 0.10.2 is voted it should be. Hopefully this week. Eno > On 17 Apr 2017, at 13:25, Mahendra Kariya wrote: > > Are the bug fix releases published to Maven central repo? > > On Sat, Apr 1, 2017 at 12:26 PM, Eno Thereska > wrote: > >> Hi Sachin, >> >> In the bug fix rele

Re: [VOTE] 0.10.2.1 RC1

+1 (non-binding) Upgraded KS & KC applications to 0.10.2.1 RC1, successfully ran application-level acceptance tests. Mathieu On Wed, Apr 12, 2017 at 6:25 PM, Gwen Shapira wrote: > Hello Kafka users, developers, client-developers, friends, romans, > citizens, etc, > > This is the second candid

Re: Kafka streams 0.10.2 Producer throwing exception eventually causing streams shutdown

Are the bug fix releases published to Maven central repo? On Sat, Apr 1, 2017 at 12:26 PM, Eno Thereska wrote: > Hi Sachin, > > In the bug fix release for 0.10.2 (and in trunk) we have now set > max.poll.interval to infinite since from our experience with streams this > should not be something t

Kafka producer doesn't produce

Now I’m curious why the below just sits and does nothing. import java.util.Properties; import org.apache.kafka.clients.producer.Producer; import org.apache.kafka.clients.producer.KafkaProducer; import org.apache.kafka.clients.producer.ProducerRecord; public class SimpleProducer { public static

RE: Kafka won't take messages

PLAINTEXT://localhost:6667 Interestingly though, it won't take localhost. It requires the server url. That may have something to do with the way I have the server configured. Adaryl "Bob" Wakefield, MBA Principal Mass Street Analytics, LLC 913.938.6685 www.massstreet.net www.linkedin.com/in/bobw

RE: Kafka won't take messages

Got it. It turns out localhost wouldn't fly. It needed the actual url of the server. Adaryl "Bob" Wakefield, MBA Principal Mass Street Analytics, LLC 913.938.6685 www.massstreet.net www.linkedin.com/in/bobwakefieldmba Twitter: @BobLovesData -Original Message- From: Vinod KC [mailto:v...@

Re: Kafka won't take messages

Can you check the value of ‘listeners’ in server.properties ? Eg: listeners=PLAINTEXT://: Ensure the port you are connecting is correct On 4/17/17, 4:34 PM, "Adaryl Wakefield" wrote: [2017-04-17 07:03:20,183] ERROR Error when sending message to topic test_topic with key: null, value: 22 by

RE: Kafka won't take messages

[2017-04-17 07:03:20,183] ERROR Error when sending message to topic test_topic with key: null, value: 22 bytes with error: ( org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 6 ms. Adaryl "Bob" W

Re: Kafka won't take messages

When you run the producer it will be expecting you to produce some message(s). Run a consumer simultaneously and enter some message in producer console. you should be able to see the same in at console consumer output. On Mon, Apr 17, 2017 at 3:39 PM, Adaryl Wakefield < adaryl.wakefi...@hotmail.co

Kafka won't take messages

My cluster is not accepting connections and messages for some reason. I'm not sure where to start troubleshooting. When I try to test it with: $ bin/kafka-console-producer.sh --broker-list localhost:6667 --topic test_topic It just hangs. When I try to run a Simple Producer, I get the same result.