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

Storage Error: More than one request trying to add/update/delete one edge/vertex at the same time. #3539

Closed
sunkararp opened this issue Dec 22, 2021 · 4 comments
Assignees
Labels
community Source: who proposed the issue need info Solution: need more information (ex. can't reproduce) type/bug Type: something is unexpected

Comments

@sunkararp
Copy link

Nebula:2.6.1.
Kubernetes: 1.20.7
Azure

Nebula Cluster Info:
graphd: 1
storaged: 2
metad: 1

We're getting below error when ingesting data:

Storage Error: More than one request trying to add/update/delete one edge/vertex at the same time.

Any idea how to fix this error?

Using Python library to ingest data.

`
config = Config()
config.max_connection_pool_size = 1

ok = connection_pool.init([('10.155.51.233', 9669)], config)        
 session = connection_pool.get_session('root', 'nebula')

`

@sunkararp sunkararp added the type/bug Type: something is unexpected label Dec 22, 2021
@Aiee
Copy link
Contributor

Aiee commented Dec 23, 2021

Did you use the same session instance with multiple threads? The session is not thread-safe.

@sunkararp
Copy link
Author

@Aiee
Copy link
Contributor

Aiee commented Jan 13, 2022

Screen Shot 2022-01-13 at 10 20 11 AM
It seems you are inserting the same edge with 2 different sessions. Is this intended? Please check the data input source if this is not.

@Sophie-Xie Sophie-Xie added the need info Solution: need more information (ex. can't reproduce) label Feb 8, 2022
@Sophie-Xie Sophie-Xie added the community Source: who proposed the issue label Apr 24, 2022
@Sophie-Xie
Copy link
Contributor

There is no more info about this issue. I will close it first, and you can reopen anytime it if needed. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Source: who proposed the issue need info Solution: need more information (ex. can't reproduce) type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

3 participants