Skip to content
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

support dangling handle for each session connection #198

Merged
merged 2 commits into from
Mar 23, 2021

Conversation

lidongze0629
Copy link
Collaborator

@lidongze0629 lidongze0629 commented Mar 23, 2021

What do these changes do?

Support reconnect to the coordinator service in addr mode when session quit accidentally.

# deploy graphscope with HELM
import graphscope
graphscope.set_option(dangling_timeout_seconds=60)
sess = graphscope.session(addr='<ip>:<port>')

# now session quit accidentally.
# after dangling_timeout_seconds=60 s, you can reconnect to the service

# note that resource such as app/graph inside session will not exist.
sess = graphscope.session(addr='<ip>:<port>')

This PR also fix problem of creating interactive_query pod asynchronously after loading graph.

Related issue number

Fixes #195

python/graphscope/client/session.py Outdated Show resolved Hide resolved
coordinator/gscoordinator/coordinator.py Outdated Show resolved Hide resolved
@lidongze0629 lidongze0629 merged commit 509b915 into alibaba:main Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

support reconnect server when client accidentally quit
3 participants