For parquet files with multiple blocks we schedule the scan ranges across all replicas of the blocks, aiming for local execution on impalads, which are running on the datanodes where the blocks are located. However there seems to be a high number of remote reads in these scenarios.
The scheduler makes local assignments:
However the profile shows remote scans:
Somehow Impala seems to read data from the wrong datanodes, possibly reading everything from the one where it read the footer from.
Sailesh Mukil - We briefly talked about this before in person. Do you have time to look at this? If not feel free to re-assign it to me.