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.

Sign up for GitHub

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

Jump to bottom

BUG? Response执行完先于IssueRPC中的bthread_id_unlock执行完毕的话, unlock会失败吧? #2646

Open
jiangdongzi opened this issue May 21, 2024 · 3 comments
Open

BUG? Response执行完先于IssueRPC中的bthread_id_unlock执行完毕的话, unlock会失败吧? #2646

jiangdongzi opened this issue May 21, 2024 · 3 comments

Comments

@jiangdongzi
Copy link

在写mongo客户端, 遇到了bthread_id_unlock_and_destroy先于bthread_id_unlock执行完毕的情况, 导致unlock失败

image
这句可能会在bthread_id_unlock_and_destroy之前执行完毕, 那么check会失败
@jiangdongzi jiangdongzi changed the title response执行完先于IssueRPC中的bthread_id_unlock执行完毕的话, unlock会失败吧? BUG? Response执行完先于IssueRPC中的bthread_id_unlock执行完毕的话, unlock会失败吧? May 21, 2024
@chenBright
Copy link
Contributor

bthread_id_unlock的返回值是什么？

@jiangdongzi
Copy link
Author

bthread_id_unlock的返回值是什么？

22

@chenBright
Copy link
Contributor

发rpc的时候，已经lock bthread_id了，bthread_id_unlock_and_destroy实际是在bthread_id_unlock里被调的，这在设计的时候已经考虑到了。

bthread_id的使用是不是有改动？或者定位一下这个EINVAL返回值实际是哪里返回的。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chenBright @jiangdongzi