You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like this is related with the issue i saw few times in tests and i wasn't able to reproduce, i.e. reader stuck during recovery.
I analyzed the logs again and it looks like the current leader has the follower 0 marked as being recovered (i.e. it delivers missing records to the follower). I will add a timeout to the recovery read with an error log level so that we will be protected and see if the issue occur in tests
Version & Environment
Redpanda version: (use
rpk version
): 22.2.7What went wrong?
Observed in Cloud V1 that a parition was unable to successfully handover leadership from node 2 to node 0.
When node 2 originally became leader, it reported:
On subsequent attempted transfer back to node 0, node 2 reported a loop of:
Node 0 reported:
The text was updated successfully, but these errors were encountered: