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

lot of prop mismatch of in/out edges and edges loss when leader change happends frequently #2893

Closed
kikimo opened this issue Sep 17, 2021 · 0 comments
Assignees
Labels
type/bug Type: something is unexpected
Milestone

Comments

@kikimo
Copy link
Contributor

kikimo commented Sep 17, 2021

Please check the FAQ documentation before raising an issue

Please check the FAQ documentation and old issues before raising an issue in case someone has asked the same question that you are asking.

Describe the bug (must be provided)

lot of prop mismatch of in/out edges and edges loss when leader change happends frequently.

Your Environments (must be provided)

  • OS: uname -a
  • Compliler: g++ --version or clang++ --version
  • CPU: lscpu
  • Commit id (e.g. a3ffc7d8)

How To Reproduce(must be provided)

Steps to reproduce the behavior:

  1. 3storage + 3 graph + 1meta
  2. trigger leader change frequently
  3. insert lot edges

python scripts to trigger nebula leader change:

# coding: utf-8

import os
import time
import random
import signal
from subprocess import check_output

process_name = 'nebula-storaged'
pid_list = check_output(['pidof', process_name])
pids = pid_list.split()
pids = [int(pid) for pid in pids]
print(pids)

while True:
    victim = random.choice(pids)
    print("stopping {}".format(victim))
    # import pdb; pdb.set_trace()
    os.kill(victim, signal.SIGSTOP)
    time.sleep(2)
    os.kill(victim, signal.SIGCONT)
    print('resuming {}'.format(victim))
    time.sleep(2)

During a test we insert 16384 edges, and found 58 in/out edge prop mismatches, and 5248 edge loss.

Expected behavior

A clear and concise description of what you expected to happen.

Additional context

Provide logs and configs, or any other context to trace the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

2 participants