-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Open
Description
Search before asking
- I had searched in the issues and found no similar issues.
Version
2.1.8
What's Wrong?
The Backend was added as 127.0.0.1:9030, and it couldn't used for data transport on a other machine.
So, the same Backend was added as internal real IP:9030, and use ALTER SYSTEM DECOMMISSION BACKEND '127.0.0.1:9030', but it stoped at some table, and all query went error at that time.
So, I use ALTER SYSTEM DROPP BACKEND to drop the local ip backend, and added the same backend with real IP:9030. and reimport all data from begin.
but it still has warnlog, it shows like the log file.
Query runs as well as every thing alright. only some planer run in error.
What You Expected?
I hope this can be fixed, and some one can told me if some thing is still in danger.
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
No labels