Open gshimansky opened 2 years ago
I've reproduced this problem on windows 10 too.
@sven1977 @rshin @robertnishihara - why is this issue marked as P2 priority? If there are no plans for supporting Ray as a first-class platform, please let me know. If there are, then please, let us know the adjusted priority and release plan. Thanks.
What happened + What you expected to happen
I have a strong suspicion that this bug is specific to Windows 11 because before I upgraded my workstation to Windows 11 I could execute the same workload just fine on windows 10. The problem is reproducible on 40 cores Intel Cascade Lake system and 64 cores AMD Threadripper systems, both win11 22H2 build 22621.819.
Most often I get no exception or stack traces that are reduced to just few stack trace elements, but I was lucky and here is a full exception stack trace:
Versions / Dependencies
Python 3.9.13 Modin 0.17.0 Ray 2.0.1, 2.1.0 Modin 0.17.0 is currently incompatible the latest version of Ray 2.1.0 (the reason is not that Modin doesn't work with most recent version of Ray, it is some conflict over redis version dependency), so to test 2.1.0 I used the following commands:
It works because pip doesn't check for version conflict with already installed Modin version. But the same behavior is observed with version 2.0.1 and I think some older versions as well.
Reproduction script
Workload is a benchmark script that uses Modin. Please clone it from my repo https://github.com/gshimansky/data-science-processing-workload . Execute it like this:
python launcher.py -m census
orpython launcher.py -m taxi
. Access violation happens in random moments of code execution.Issue Severity
High: It blocks me from completing my task.