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

Can the corresponding session be released after the Nebula service restarts abnormally? #529

Closed
soul-gin opened this issue Jul 13, 2023 · 1 comment
Labels
type/question Type: question about the product

Comments

@soul-gin
Copy link

Introduction

  1. Obtain the session from the session pool and query normally
  2. nebula.service restart graphd
  3. If the corresponding session query is not released, it will continue to fail

Contents

1689218637768

image

@QingZ11 QingZ11 added the type/question Type: question about the product label Sep 18, 2023
@Nicole00
Copy link
Contributor

Nicole00 commented Dec 7, 2023

After nebula.graphd server restarted, the session's connection will be unavailable, so the session can not be released by client, only wait to to released until it expires in nebula.metad.

For SessionPool, we do not to migrate the session between different graphd servers.

@QingZ11 QingZ11 closed this as completed Dec 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question Type: question about the product
Projects
None yet
Development

No branches or pull requests

3 participants