-
Notifications
You must be signed in to change notification settings - Fork 498
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
[Bug]: fluvio cluster resume
stuck in trying to connect to SC
#3989
Comments
@avikam can you please take a look at this one? |
@ajhunyady can you reproduce it with RUST_LOG=debug? For example, if you had fluvio running, and then restarted your machine and cargo built master before resuming, you might see this:
edit - more context: |
restart logic should check version number and warn user of incompatibility |
indeed it's the same issue.
I would agree with @sehz the solution show be showing a warning to the user, and proceeding with the start/resume process |
I actually tried both variants. % fluvio cluster resume
✅ Local Fluvio is not installed
🎉 All checks passed!
✅ Local Cluster initialized
👤 Profile set
🖥️ Trying to connect to SC: 127.0.0.1:9003 19 seconds elapsed /
^C
% fluvio cluster start
📝 Running pre-flight checks
✅ Local Fluvio is not installed
❌ Check Clean Fluvio Local Installation failed Local Fluvio cluster wasn't deleted. Use 'resume' to resume created cluster or 'delete' before starting
💔 Some pre-flight check failed!
Preflight check failed I was forced to delete to recover. |
Ok, I think I understand what's going on. We are currently updating smartmodules, so I'm constantly upgrading & downgrading to test. Since the smart engine changed, I must restart the cluster every time. Now I realize that we may actually need a The current |
Yup. |
Iv'e been thinking to address it in two PRs:
an alternative for (2) is to remove the entire local-config file before starting the cluster. However, we'd lose configuration like number of SPUs, TLS policy, logs, etc. |
Idea of having First should have anyway as required pre-flight check. Then figure out process of upgrade as this needs to be common across multiple cluster types |
|
here is 1 before seems like there is an alignment so I'll keep pursuing that |
fixed w/ PR #4138 |
I shutdown the machine without closing down the cluster.
After restart, I just
fluvio cluster resume
as instructed by the message influvio cluster start
, but it is stuck in a loop:To remediate this, I needed to delete the cluster and create a new one.
I also got an error during delete:
Environment: Using Mac with Intel CPU.
Note
: The message flashes continuously while the spinner updates.The text was updated successfully, but these errors were encountered: