You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, child nodes are forced to SAME_THREAD execution if the parent has any locks.
If the parent only has READ locks, then it would be valid for the child nodes to execute concurrently. This would also alleviate the issues of #2038 and we partly have this logic already for the isolated execution of #2142
Deliverables
Don't force child nodes to SAME_THREAD execution if only READ locks are acquired
The text was updated successfully, but these errors were encountered:
Currently, child nodes are forced to
SAME_THREAD
execution if the parent has any locks.If the parent only has
READ
locks, then it would be valid for the child nodes to execute concurrently. This would also alleviate the issues of #2038 and we partly have this logic already for the isolated execution of #2142Deliverables
SAME_THREAD
execution if onlyREAD
locks are acquiredThe text was updated successfully, but these errors were encountered: