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

[Bug]: [CI] integration test failed due to DATA RACE detected in internal/datacoord/server.go #33203

Open
1 task done
jiangyinzuo opened this issue May 20, 2024 · 1 comment
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@jiangyinzuo
Copy link
Contributor

jiangyinzuo commented May 20, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: commit ab1652029e77a226f70b143322be7ac9e63063f5 (see #33141), which is based on c35eaaa3581b2a4e00e49a8517e846d4f2479daa
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

There is a data race detected in integration test, see

2024-05-20T14:39:48.1649082Z WARNING: DATA RACE
2024-05-20T14:39:48.1649201Z Read at 0x00c0049fe960 by goroutine 15612:
2024-05-20T14:39:48.1649507Z   github.com/milvus-io/milvus/internal/datacoord.(*Server).GetServerID()
2024-05-20T14:39:48.1649837Z       /go/src/github.com/milvus-io/milvus/internal/datacoord/server.go:469 +0x86

...

2024-05-20T14:39:48.1659650Z Previous write at 0x00c0049fe960 by goroutine 163:
2024-05-20T14:39:48.1659945Z   github.com/milvus-io/milvus/internal/datacoord.(*Server).initSession()
2024-05-20T14:39:48.1660258Z       /go/src/github.com/milvus-io/milvus/internal/datacoord/server.go:302 +0x2aa

...

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@jiangyinzuo jiangyinzuo added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 20, 2024
@yanliang567
Copy link
Contributor

/assign @czs007
/unassign

@sre-ci-robot sre-ci-robot assigned czs007 and unassigned yanliang567 May 21, 2024
@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants