Did you see the warning "Error connecting to node" on consumer log?
Best,
Lisheng
Hrishikesh Mishra 于2019年8月29日周四 下午2:45写道：
> Please find my reply in blue colour:
>
>
>
> On Thu, Aug 29, 2019 at 11:32 AM Lisheng Wang
> wrote:
>
> > Hi
> >
> > about question 1, it's dosen't matter that how man
Please find my reply in blue colour:
On Thu, Aug 29, 2019 at 11:32 AM Lisheng Wang
wrote:
> Hi
>
> about question 1, it's dosen't matter that how many consumers in same
> consumer group.
>
> So you means the broker which is coordinator did not crashed at all before?
>
We didn't see any shutd
Hi
about question 1, it's dosen't matter that how many consumers in same
consumer group.
So you means the broker which is coordinator did not crashed at all before?
May i know if only exact one broker(coordinator) is unavailable or many
are? if only exact one, you can try to transfer leader of _
Hi,
We are facing following issues with Kafka cluster.
- Kafka Version: 2.0.0
- We following cluster configuration:
- Number of Broker: 14
- Per Broker: 37GB Memory and 14 Cores.
- Topics: 40 - 50
- Partitions per topic: 32
- Replicas: 3
- Min In Sync Replica: 2
- __con
