AMQStreams Kafka brokers are able to restart after pvc overload

Solution Unverified - Updated -

Issue

  • After uncontrolled shutdown caused by pvc overload (100% used) out of three, two Kafka brokers are not able to restart.

Error Message in Log:

2020-08-20 12:17:00,450 ERROR [Broker id=1] Received LeaderAndIsrRequest with correlation id 1 from controller 0 epoch 156 for partition connect-cluster-status-3 (last update controller epoch 156) but cannot become follower since the new leader -1 is unavailable. (state.change.logger) [kafka-request-handler-5]

We seem to suspect that the partitions in those two pvcs are not in sync anymore. Is there a possibility to sync it again?
Or how could we manage to get all tree brokers up again ?

Environment

  • Red Hat AMQ Streams
    • 1.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content