Hi Manoj,
Thanks but we caught the issue, it was coming most probably because the
wrong jar was being picked up from hdfs and was being set in oozie
classpath at runtime. In our code, kafka-client is on 2.3 but while running
MR job 0.8.2.0 jar was being picked up. We caught it after seeing the
prod
What error you are getting , can you share the exact error ?
What is version of kafka lib at client side ?
On 8/25/20, 7:50 AM, "Prateek Rajput"
wrote:
[External]
Hi, please if anyone can help, will be a huge favor.
*Regards,*
*Prateek Rajput*
On Tue, Aug 25, 2020 at
Hi Rohit, We checked that ISR was available and all leaders were there. It
was failing during instantiation of the client, while making the very first
connection to a broker. Because randomly it selected only that broker
from *bootstrap.servers
*list which was down and tried to connect to that serv
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
wrote:
> Hi, please if anyone can help, will be a huge favor.
>
> *Regards,*
> *Prateek Rajput*
>
>
> On Tue,
Hi, please if anyone can help, will be a huge favor.
*Regards,*
*Prateek Rajput*
On Tue, Aug 25, 2020 at 12:06 AM Prateek Rajput
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* vers
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
