Please check your ISR using describe command and see if there is leader
available when one of the broker is down .
Thanks and Regards,
Rohit
On Tue, Aug 25, 2020, 20:20 Prateek Rajput
<prateek.rajput@flipkart.com.invalid> wrote:
> Hi, please if anyone can help, will be a huge favor.
>
> *Regards,*
> *Prateek Rajput* <prateek.rajput@flipkart.com>
>
>
> On Tue, Aug 25, 2020 at 12:06 AM Prateek Rajput <
> prateek.rajput@flipkart.com>
> wrote:
>
> > Hi everyone,
> > I am new to Kafka, and recently started working on kafka in my company.
> We
> > recently migrated our client and cluster from the *0.10.x* version to
> > *2.3.0*. I am facing this issue quite often.
> > I have provided all brokers in *bootstrap.servers* config to instantiate
> > the producer client but while using this client for batch publishing,
> > sometimes some of my mappers get stuck.
> > I debugged and found that one broker was down (for some maintenance
> > activity). Now it was getting stuck because the mapper's client was
> trying
> > to connect to that node only for the very first time. And it was failing
> > with NoRouteToHost Exception.
> > I have read that the very first time the client will select a random
> > broker and will try to connect with that broker to get the meta-data of
> the
> > whole cluster. Is there any way so that on such exceptions it can switch
> to
> > another node dynamically and should not try to connect to the same box
> > again and again.
> >
> > *Regards,*
> > *Prateek Rajput* <prateek.rajput@flipkart.com>
> >
>
> --
>
>
>
>
> *-----------------------------------------------------------------------------------------*
>
>
> *This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this email in error, please notify the
> system manager. This message contains confidential information and is
> intended only for the individual named. If you are not the named
> addressee,
> you should not disseminate, distribute or copy this email. Please notify
> the sender immediately by email if you have received this email by mistake
> and delete this email from your system. If you are not the intended
> recipient, you are notified that disclosing, copying, distributing or
> taking any action in reliance on the contents of this information is
> strictly prohibited.*****
>
> ****
>
> *Any views or opinions presented in this
> email are solely those of the author and do not necessarily represent
> those
> of the organization. Any information on shares, debentures or similar
> instruments, recommended product pricing, valuations and the like are for
> information purposes only. It is not meant to be an instruction or
> recommendation, as the case may be, to buy or to sell securities,
> products,
> services nor an offer to buy or sell securities, products or services
> unless specifically stated to be so on behalf of the Flipkart group.
> Employees of the Flipkart group of companies are expressly required not to
> make defamatory statements and not to infringe or authorise any
> infringement of copyright or any other legal right by email
> communications.
> Any such communication is contrary to organizational policy and outside
> the
> scope of the employment of the individual concerned. The organization will
> not accept any liability in respect of such communication, and the
> employee
> responsible will be personally liable for any damages or other liability
> arising.*****
>
> ****
>
> *Our organization accepts no liability for the
> content of this email, or for the consequences of any actions taken on the
> basis of the information *provided,* unless that information is
> subsequently confirmed in writing. If you are not the intended recipient,
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.*
>
>
>
> _-----------------------------------------------------------------------------------------_
>
>
available when one of the broker is down .
Thanks and Regards,
Rohit
On Tue, Aug 25, 2020, 20:20 Prateek Rajput
<prateek.rajput@flipkart.com.invalid> wrote:
> Hi, please if anyone can help, will be a huge favor.
>
> *Regards,*
> *Prateek Rajput* <prateek.rajput@flipkart.com>
>
>
> On Tue, Aug 25, 2020 at 12:06 AM Prateek Rajput <
> prateek.rajput@flipkart.com>
> wrote:
>
> > Hi everyone,
> > I am new to Kafka, and recently started working on kafka in my company.
> We
> > recently migrated our client and cluster from the *0.10.x* version to
> > *2.3.0*. I am facing this issue quite often.
> > I have provided all brokers in *bootstrap.servers* config to instantiate
> > the producer client but while using this client for batch publishing,
> > sometimes some of my mappers get stuck.
> > I debugged and found that one broker was down (for some maintenance
> > activity). Now it was getting stuck because the mapper's client was
> trying
> > to connect to that node only for the very first time. And it was failing
> > with NoRouteToHost Exception.
> > I have read that the very first time the client will select a random
> > broker and will try to connect with that broker to get the meta-data of
> the
> > whole cluster. Is there any way so that on such exceptions it can switch
> to
> > another node dynamically and should not try to connect to the same box
> > again and again.
> >
> > *Regards,*
> > *Prateek Rajput* <prateek.rajput@flipkart.com>
> >
>
> --
>
>
>
>
> *-----------------------------------------------------------------------------------------*
>
>
> *This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this email in error, please notify the
> system manager. This message contains confidential information and is
> intended only for the individual named. If you are not the named
> addressee,
> you should not disseminate, distribute or copy this email. Please notify
> the sender immediately by email if you have received this email by mistake
> and delete this email from your system. If you are not the intended
> recipient, you are notified that disclosing, copying, distributing or
> taking any action in reliance on the contents of this information is
> strictly prohibited.*****
>
> ****
>
> *Any views or opinions presented in this
> email are solely those of the author and do not necessarily represent
> those
> of the organization. Any information on shares, debentures or similar
> instruments, recommended product pricing, valuations and the like are for
> information purposes only. It is not meant to be an instruction or
> recommendation, as the case may be, to buy or to sell securities,
> products,
> services nor an offer to buy or sell securities, products or services
> unless specifically stated to be so on behalf of the Flipkart group.
> Employees of the Flipkart group of companies are expressly required not to
> make defamatory statements and not to infringe or authorise any
> infringement of copyright or any other legal right by email
> communications.
> Any such communication is contrary to organizational policy and outside
> the
> scope of the employment of the individual concerned. The organization will
> not accept any liability in respect of such communication, and the
> employee
> responsible will be personally liable for any damages or other liability
> arising.*****
>
> ****
>
> *Our organization accepts no liability for the
> content of this email, or for the consequences of any actions taken on the
> basis of the information *provided,* unless that information is
> subsequently confirmed in writing. If you are not the intended recipient,
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.*
>
>
>
> _-----------------------------------------------------------------------------------------_
>
>
Comments
Post a Comment