John Spray
John Spray
I amended the title to be a bit more succinct. Did you mean to mark this as `Fixes` https://github.com/redpanda-data/redpanda/issues/6902, or are you still looking at the root cause of how...
@joejulian @dotnwat is this ticket still relvant?
It sounds like there is still work to do here: checking cluster health before proceeding with upgrades is important for robustness. ## Scenario A: unexpected bug Hypothetical Redpanda version has...
> just curious if a viable alternatively would have been to assign non-data batches a timestamp equal to its neighbor batch rather than trying to actually remove them from indexing?...
This is in a passing state now. Will do a ci-repeat once the issue with CI test runners running out of disk is resolved (that was the release-clang-amd64 failure)
> For B: What signal should we be looking for? When node 1 is rolled, comes back, takes itself out of maintenance mode - what signal does Redpanda give that...
> A: Press-on! I don't recommend this. On a major version upgrade, if you give up on a rolling upgrade and flash forward to updating all the nodes, then new...
Repeats had one failure, which looks like this existing issue: https://github.com/redpanda-data/redpanda/issues/6745
Force pushed for merge conflict