-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade local cluster freezes topic creation #4162
Comments
Did all process properly shutdown and everything has been properly flushed? where is test failing? |
Yes, on my tested all processes could be closed and started again |
I am not seeing assertion in the test. |
Also, I tried many changes in the fluvio code to try to fix it or at least reduce it failling. One thing that I tried and seems that improved it, it was removing the Not sure if this is really related, I suspect that these metrics slowdown performance on not arm machines and make it easier to get this bug. Btw, I think we could be using more I noticed this test failing less times when I tried to change it to |
what means |
Can you create PR again with upgrade test enabled? |
Yeah, sure! #4173 |
Fixed by #4175 |
The CI
local_upgrade_test
that runsmake FLUVIO_MODE=local FLUVIO_BIN=~/bin/fluvio upgrade-test
created at #4138 was failing a lot.The problem is when the local cluster is upgraded and resumed, and then it tried to create a new topic.
I tested it locally on a Linux machine with a weak cpu (J4125) and the problem happens most of the time.
I also tested it on my macbook m1 pro max only happened once after many tries.
I tried to add more sleeps in the tests does not seem very effective.
The only errors log that I got it was that the watch connection failed, but this not seems the problem.
I suspect that is related to our shutdown command is not really graceful for local clusters because when I try shutdown and resume again, everything works fine. Also, seems that we don't have logs to catch this.
SC logs:
The text was updated successfully, but these errors were encountered: