-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
I meet some issue (Bug) when I traverse vertex causing the nebula-graphd crashed #4302
Comments
Interesting, so this pattern was to match vertices with/out any edges connected to them? PS. here is the runnable query and plan for it
|
I think yes. and I will try my best to reproduce this problem again, but if you guys have any idea about source code. pls let me konw how to get the details about this. thx indeed. |
Hello, what's the version of nebula-graphd reporting the error? |
3.0.1, I think this problem cause by concurrently alter schema, which cause the meta schema data mess. |
But I don't see you mention concurrently alter schema in issue description, could you attach the whole operations? |
Closed it first, if you have some new info, you can open the issue again. |
Describe the bug (required)
When I concurrent run some tests. some just like these:
the nebula-graphd service crashed and i pull the backtrace the below, I see the source code then guess the vector access out of index.
then I put some new log into here, print some message about
tagPropNameList
andpropList.values
. the pair message can not matched: you can see the follow logs:I think the above logs can prove our program, there have some logic can not match the PropIndex's colIdx. sorry for my bad english.
If you have any idea about this problem, pls help me located this. thx.
How To Reproduce(required)
because I run the concurrent tests, at now, I can not give the reproduce steps, but if you have idea, pls tell me how to do this.(because if i run test one by one, the service is normal, but i run concurrently, the service will be down)
thanks for your supporting.
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: