[Improvement] Fine-grained lock for MutableShuffleHandle when reassign happens #2721
Description
Code of Conduct
- I agree to follow this project's Code of Conduct
Search before asking
- I have searched in the issues and found no similar issues.
What would you like to be improved?
Now, the lock scope of MutableShuffleHandleInfo is still big although we have made this as a read-write lock by #2706 . Maybe we could make MutableShuffleHandleInfo thread safe and then abort the upper lock.
How should we improve?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!