No, I don’t think we have any orphaned process. Can you please bit elaborate what you are trying to explain and what would be the solution?
Thanks Achintya -----Original Message----- From: Jon Yeargers [mailto:jon.yearg...@cedexis.com] Sent: Tuesday, January 24, 2017 11:07 AM To: users@kafka.apache.org Subject: Re: Messages are lost Make sure you don't have an orphaned process holding onto the various kafka/zk folders. If it won't respond and you can't kill it then this might have happened. On Tue, Jan 24, 2017 at 6:46 AM, Ghosh, Achintya (Contractor) < achintya_gh...@comcast.com> wrote: > Can anyone please answer this? > > Thanks > Achintya > > -----Original Message----- > From: Ghosh, Achintya (Contractor) [mailto:achintya_gh...@comcast.com] > Sent: Monday, January 23, 2017 1:51 PM > To: users@kafka.apache.org > Subject: RE: Messages are lost > > Version 0.10 and I don’t have the thread dump but have the KafkaServer > log where the error is there. > > Thanks > Achintya > > -----Original Message----- > From: Apurva Mehta [mailto:apu...@confluent.io] > Sent: Monday, January 23, 2017 12:49 PM > To: users@kafka.apache.org > Subject: Re: Messages are lost > > What version of kafka have you deployed? Can you post a thread dump of > the hung broker? > > On Fri, Jan 20, 2017 at 12:14 PM, Ghosh, Achintya (Contractor) < > achintya_gh...@comcast.com> wrote: > > > Hi there, > > > > I see the below exception in one of my node's log( cluster with 3 > > nodes) and then the node is stopped to responding(it's hung state , > > I mean if I do > > ps-ef|grep kafka , I see the Kafka process but it is not responding) > > ps-ef|and we > > lost around 100 messages: > > > > > > 1. What could be the reason for this exception ? My broker ID is > > unique so what is the solution for this issue? > > > > [2017-01-19 15:56:23,644] ERROR Error handling event ZkEvent[New > > session event sent to > > kafka.server.KafkaHealthcheck$SessionExpireListener@2d74e7af] > > (org.I0Itec.zkclient.ZkEventThread) > > java.lang.RuntimeException: A broker is already registered on the > > path /brokers/ids/2. This probably indicates that you either have > > configured a brokerid that is already in use, or else you have > > shutdown this broker and restarted it faster than the zookeeper > > timeout so it appears to be re-registering. > > at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils. > > scala:305) > > at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils. > > scala:291) > > at kafka.server.KafkaHealthcheck. > > register(KafkaHealthcheck.scala:70) > > at kafka.server.KafkaHealthcheck$SessionExpireListener. > > handleNewSession(KafkaHealthcheck.scala:104) > > at org.I0Itec.zkclient.ZkClient$6.run(ZkClient.java:735) > > at org.I0Itec.zkclient.ZkEventThread.run( > > ZkEventThread.java:71) > > > > > > > > 2. As we lost 100 messages for each topic and I don't see any > > exception in our application log, so how we can track the exception > > and will make sure the we'll not loose any data(consumer end). > > > > Thanks > > Achintya > > >
