Re: Best practice for publishing byte messages to Kafka

Oops, I was mistaken. I meant serialization of an object as a byte array from the first place! On Wed, Jan 10, 2018 at 3:20 PM, Thunder Stumpges < thunder.stump...@gmail.com> wrote: > Byte Array is essentially "serialized" already isn't it? I mean the message > itself is sent as a byte array, so

Re: map operator on KeyedStream

You might want to ask at the Flink mailing list. Or use Kafka Streams instead of Flink :D -Matthias On 1/10/18 3:45 AM, Moein Hosseini wrote: > Hi. > This is Moein, a newbie in Apache Flink. > > I got confused when I saw that KeyedStream class extend DataStream without > overriding the map

map operator on KeyedStream

Hi. This is Moein, a newbie in Apache Flink. I got confused when I saw that KeyedStream class extend DataStream without overriding the map method. what is the reason behind it? How is it possible to keep KeyedStream after transformation without lossing the key? something like: newMap(fn):

RE: KAFKA_50 - Error writing data to the Kafka broker

Forgot to mention the JIRA that we have raised - https://issues.apache.org/jira/browse/KAFKA-6439 Regards, Jayashree Sanyal jayashree.san...@aricent.com Office:+91 80 41067520| Mobile +91 9900236687 From: Jayashree Sanyal Sent: Wednesday, January 10, 2018

KAFKA_50 - Error writing data to the Kafka broker

Hi , We have raised this bug while facing issues on the customer deployment. Can some pls provide a workaround resolution asap as it is causing impact on customer traffic. Regards, Jayashree Sanyal jayashree.san...@aricent.com Office:+91 80 41067520|

Re: Broker won't exit...

Skip:Can you pastebin the stack trace of the stuck broker ? Will try to later, when the system is quiescent. I forgot to save the gstack output yesterday. S

Re: Broker won't exit...

HI brokers still try todo a gracefull shutdown I supose? It would only shut down if it is not the leader of any partition anymore. Can you verify: there are other brokers alive that took over leadership? and the broker in question stepped down as a leader for all partitions? Best Jan On

Re: Broker won't exit...

if you really want all the brokers to die, try change server.properties controlled.shutdown.enable=false I had a similar problem on dev laptop with a single broker. It refused to die on system shutdowns (or took a very long time). 2018-01-10 12:57 GMT+01:00 Ted Yu : >

Re: Broker won't exit...

Skip:Can you pastebin the stack trace of the stuck broker ? Thanks Original message From: Skip Montanaro Date: 1/10/18 3:52 AM (GMT-08:00) To: users@kafka.apache.org Subject: Re: Broker won't exit... Did you stop the broker before stoping zookeeper?

Re: Broker won't exit...

Did you stop the broker before stoping zookeeper? Yes. My stop script executes the server stop scripts in reverse order from my start script. Should I have stuck in a couple second sleep between stopping the brokers and stopping zookeeper? I was actually running two brokers. The one my stop

Re: Broker won't exit...

Have you tried a normal kill (sigterm) against the java process? Yes. Nothing worked until kill -9. Skip

Re: Broker won't exit...

Did you stop the broker before stoping zookeeper? On Wed, 10 Jan 2018 at 10:38 Ted Yu wrote: > I think that is the default signal. > From the script: > > SIGNAL=${SIGNAL:-TERM} > > FYI > > On Wed, Jan 10, 2018 at 2:35 AM, Sam Pegler < > sam.peg...@infectiousmedia.com> >

Re: Broker won't exit...

I think that is the default signal. >From the script: SIGNAL=${SIGNAL:-TERM} FYI On Wed, Jan 10, 2018 at 2:35 AM, Sam Pegler wrote: > Have you tried a normal kill (sigterm) against the java process? > > __ > > Sam Pegler > > PRODUCTION ENGINEER > > T. +44(0) 07

Re: Broker won't exit...

Have you tried a normal kill (sigterm) against the java process? __ Sam Pegler PRODUCTION ENGINEER T. +44(0) 07 562 867 486 3-7 Herbal Hill / London / EC1R 5EJ www.infectiousmedia.com This email and any attachments are confidential and may also be

Re: Need feedbacks to consumer if hangs due to some __consumer_offsets partitions failed

Hey, I think you can do it in two ways: 1. Manually increase the replication factor 2. In the server.config file, change the default.replication.factor Best, Xin On 09.01.18, 07:46, "1095193...@qq.com" <1095193...@qq.com> wrote: hi My kafka cluster has two brokers( 0 and 1) and