Edge lost under high load of concurrent clients inserting a lot of same edges.

[kikimo]

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)

Edge lost under high load of concurrent clients inserting a lot of same edges.

Your Environments (must be provided)

• OS: uname -a
• Compliler: g++ --version or clang++ --version
• CPU: lscpu
• Commit id (e.g. a3ffc7d8)
  https://github.com/liuyu85cn/nebula.git 730a39d

How To Reproduce(must be provided)

Steps to reproduce the behavior:

1. Create a cluster with 3storage + 3graph + 1meta, a space with 3partition + 3replicas
2. Create high load of concurrent clients inserting a lot of same edges

During our test, we start 64 clients and each insert same set of 16384 edges, in the end we find only 12772 edges:

12772 edges in total
props mismatch in edge (12->76), forward: ["15-1484"], backward: ["33-1484"]
lost edges:
8->12
16->87
25->63
49->78
80->36
29->51
65->12
5->30
106->60
58->9
25->96

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.

[liuyu85cn]

Some request not return correctly. (actually error but return succeed, let client thought that edge missed)

fixed in PR #2525