Yes Muthu. We also tried to set the advertised.host.name but it didn’t solved the problem. Still trying to find a solution.
Regards, Ashiq. On 20/03/16, 7:17 PM, "Muthukumaran K" <muthukumara...@ericsson.com> wrote: >Hi Ashiq, > >I am going through the same trouble with 0.9.0.0 and 0.9.0.1 for entirely >new installation on remote VM. > >But from search across mailing lists and other sources, many seem to have >had success when they have set the advertised.host.name with proper >broker host name and using the same in the client. I was not able to get >this solution working in my setup. May be you can try this. > >Regards >Muthu > >-----Original Message----- >From: Mohamed Ashiq [mailto:mohamed_as...@trimble.com] >Sent: Sunday, March 20, 2016 1:17 PM >To: users@kafka.apache.org >Subject: Re: Reg : Unable to produce message > >Sorry I miss to mention the topics which I was trying are already >existing and worked before. >When I try to list topics and try to get topic information I was able to >get all the details including leader selected. >But if I try to produce I am getting this problem. And this happened to >few topics and most of the topics in the same cluster are working >properly. > >Regards, >Ashiq. > >On 20/03/16, 11:58 AM, "Manikumar Reddy" <manikumar.re...@gmail.com> >wrote: > >>We may get few warning exceptions, on first produce to unknown topic , >>with default server config property auto.create.topics.enable = true. >>If this is the case, then it is harmless exception. >> >>On Sun, Mar 20, 2016 at 11:19 AM, Mohamed Ashiq >><mohamed_as...@trimble.com> >>wrote: >> >>> All, >>> >>> I am getting this error for few topics WARN Error while fetching >>> metadata with correlation id 4802 : >>> {next=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient) >>> WARN Error while fetching metadata with correlation id 4803 : >>> {next=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient) >>> >>> I am using Kafka 0.9.0.0 and getting this error for few topics while >>> trying to produce messages. After googling I got answers to delete >>> those topics and to recreate. >>> But I can¹t take that option since I would like to have the data and >>> the state of available. >>> >>> We got this problem in our integration environment. We are very close >>>to moving to production. It would be great if someone can help to >>>understand this problem better. >>> >>> Regards, >>> Ashiq. >>> >>> >>> >
