-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
what can i do if a CLI session times out? #1763
Comments
I don't think it's session expire.
|
That's wired. The connect was idle for someday and I came back to reuse the CLI. And then that warning was raised. The server is OK. Quit CLI and reconnect will be connected successfully. What else the problem can be. Any guess. |
Good quetstion. I encountered the same problem as you. |
I think maybe it caused by the thrift idle timeout (although we set infinity default, maybe it just drop connection when timeout but not keep alive the connection according the source code, so the infinity idle timeout is overlap by the tcp protocol connection timeout :). |
The clients will do retry in latest version. |
* Fix the dependency of argument plan node * Add test features * make ps * Rename feature and scenario * Fix tck tests Co-authored-by: Sophie <[email protected]> Co-authored-by: Yee <[email protected]> Co-authored-by: Sophie <[email protected]>
the console's session times out, and a scary warning is raised.
I know the reason and restart the CLI. But the message is a bit confusing and hard to guess the solution for other users.
I suggest to write a more friendly suggestion or no reconnect again by the CLI itself.
The text was updated successfully, but these errors were encountered: