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

Graph crash at exit #3609

Closed
SuperYoko opened this issue Dec 30, 2021 · 0 comments · Fixed by #3616
Closed

Graph crash at exit #3609

SuperYoko opened this issue Dec 30, 2021 · 0 comments · Fixed by #3616
Assignees
Labels
priority/hi-pri Priority: high type/bug Type: something is unexpected
Milestone

Comments

@SuperYoko
Copy link
Contributor

SuperYoko commented Dec 30, 2021

Please check the FAQ documentation before raising an issue

Describe the bug (required)

nebula-graphd will crash at exit at master.

image

Your Environments (required)

  • OS: uname -a
    Linux host211-cluster 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  • Compiler: g++ --version or clang++ --version
    (VEsoft Inc. Build) clang version 10.0.0
    Target: x86_64-vesoft-linux
    Thread model: posix
  • CPU: lscpu
  • Commit id: 6849383

How To Reproduce(required)

Steps to reproduce the behavior:

  1. Start nebula: nebula.service start all
  2. Wait a few seconds and stop nebula, nebula.service stop all

Expected behavior

Additional context

@SuperYoko SuperYoko added the type/bug Type: something is unexpected label Dec 30, 2021
@Sophie-Xie Sophie-Xie added this to the v3.0.0 milestone Dec 30, 2021
@Sophie-Xie Sophie-Xie added the priority/hi-pri Priority: high label Dec 30, 2021
@czpmango czpmango mentioned this issue Jan 1, 2022
11 tasks
@Sophie-Xie Sophie-Xie linked a pull request Jan 4, 2022 that will close this issue
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/hi-pri Priority: high type/bug Type: something is unexpected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants