Re: Kafka Stream App Rolling Restarts - Too Many Rebalances Per Partition

Restarts - Too Many Rebalances Per Partition Hey, Just skimming the config list, there are two things that immediately jumped out at me: 1. The default session timeout was bumped up to 45 seconds a little while ago. Not sure if you're overriding this or just using an older version,

Re: Kafka Stream App Rolling Restarts - Too Many Rebalances Per Partition

are wondering: > > > (1) is this expected, especially since cooperative rebalancing should > ensure that not a lot of partitions get rebalanced > > > (2) why would any partition undergo so many rebalances across several app > instances? > > > (3) is there some co

Kafka Stream App Rolling Restarts - Too Many Rebalances Per Partition

reduce the total rebalances and partition movements during rolling restarts? We cannot consider static membership due to other technical constraints. The runtime and network is extremely stable — no heartbeat misses, session timeouts etc. DETAILS --- * Kafka Broker Version = 2.6

Kafka shuts down abnormally and restarts, always taking more than a few hours to load

- Kafka shuts down abnormally and restarts, always taking more than a few hours to load. - We used Kafka-2.0.0,we tried to turn it up num.recovery.threads.per.data.dir,but the startup process is always limited by the slow loading of partitions.We observed a partition that

Kafka shuts down abnormally and restarts, always taking more than a few hours to load

- - - - - Kafka shuts down abnormally and restarts, always taking more than a few hours to load. - We used Kafka-2.0.0,we tried to turn it up num.recovery.threads.per.data.dir,but the startup

Re: Kafka Group coordinator discovery failing for subsequent restarts

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

Re: Kafka Group coordinator discovery failing for subsequent restarts

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

Re: Kafka Group coordinator discovery failing for subsequent restarts

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 _

Kafka Group coordinator discovery failing for subsequent restarts

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

Re: Kafka Connect restarts while creating nw

n I create new connector > through Rest API, It restarts all the connectors. > > I don't know It's normal behavior or I have to configure something so It > will not restarts all the connectors when I create new connector. > > Thanks. > -- > CHINTAN PATEL > *SR. SOFTW

Kafka Connect restarts while creating nw

Hello, I'm using Kafka connect in distributed mode. When I create new connector through Rest API, It restarts all the connectors. I don't know It's normal behavior or I have to configure something so It will not restarts all the connectors when I create new connector. Thanks. --

Re: Restarts

Hi Peter, Kafka 1.0 certainly survives restarts, we have lots of tests verifying that. :) Are you running Kafka on Windows? There is a known issue affecting Windows (which is not a supported platform at this point). Ismael On Fri, Dec 29, 2017 at 3:24 PM, peter holm wrote: > Hi, kafka

Restarts

Hi, kafka 1.0 does not survive restart. The server.log has many - cannot delete file - is this a known bug ?