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.
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
[Python][C++] posix_madvise error on Debian in pyarrow 1.0.0 #25642
Comments
Wes McKinney / @wesm: |
Joris Van den Bossche / @jorisvandenbossche: |
Wes McKinney / @wesm: |
Antoine Pitrou / @pitrou: |
Jim Pivarski / @jpivarski: |
Antoine Pitrou / @pitrou: |
I have no idea, which is why I am trying to reproduce to get some insight. |
Antoine Pitrou / @pitrou: |
Antoine Pitrou / @pitrou: |
Antoine Pitrou / @pitrou: |
Jim Pivarski / @jpivarski: I've attached the stuff.parquet file that the Chromebook made (in case it's the writing step that's affected?) as well as an strace from just before I pressed on I don't know how to read an strace, but I see the posix_madvise in there after a lot of "No such file or directory" when trying to open files like _dataset.pyx and error.pxi. I've also attached the locations of all my .pxi files: /home/jpivarski/miniconda3/lib/python3.8/site-packages/pyarrow/error.pxi is definitely there...
|
Antoine Pitrou / @pitrou: Can I ask you to compile and run this small C file on your Chromebook? (also, if it fails, can you run strace on it?) |
Jim Pivarski / @jpivarski:
and the output of
It seems to be searching for libc.so.6; in case it's relevant, that's located here:
|
Antoine Pitrou / @pitrou: |
Antoine Pitrou / @pitrou:
|
Jim Pivarski / @jpivarski:
(Maybe because the disk is so small?) Is it within scope for Parquet-reading to support operating systems compiled without swap? I don't know how unusual this situation is. I don't plan to use this computer for big data, but it did force me to turn off some tests in my testing suite. |
Antoine Pitrou / @pitrou: |
Jim Pivarski / @jpivarski: |
Antoine Pitrou / @pitrou: |
The following writes and reads back from a Parquet file in both pyarrow 0.17.0 and 1.0.0 on Ubuntu 18.04:
However, the same thing raises the following exception on Debian 9 (stretch) in pyarrow 1.0.0 but not in pyarrow 0.17.0:
It's a little odd that the error says that it failed with "detail: success". That suggests to me that an "if" predicate is backward (missing "not"), which might only be triggered on some OS/distributions.
Environment: Installed with Miniconda (for Debian; used pip for the Ubuntu test)
Reporter: Jim Pivarski / @jpivarski
Assignee: Antoine Pitrou / @pitrou
Original Issue Attachments:
PRs and other links:
Note: This issue was originally created as ARROW-9577. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: