zanmato1984 commented on PR #45268: URL: https://github.com/apache/arrow/pull/45268#issuecomment-2649597774
> Is it important to avoid taking the mutex in `ScheduleMore`? I see a bunch of atomic variable accesses, which technically pass under TSan, but there is no synchronization otherwise, and it's not ok that the overall state remains consistent. Sorry I'm not sure if I fully understand your question. If your concern is about some variables not being protected by the mutex, the original design, IIUC seems to be a hybrid scheduling of both locking-based and lockless. In particular, the metadata, namely the "task groups", (before this change the `aborted_` flag too) is protected by the mutex, whereas the rest are lockless. Does this answer your question? Thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
