Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
ghx-label-10
Description
Currently Impala treats Ozone as a remote filesystem, similar to S3A, ADLS etc. Ozone provides block location info in its Hadoop-compatible FS implementations. Also, Ozone can be colocated with Impala daemons. It would be nice if Impala could be improved to use Ozone's location info to support locality of execution.
Look into unit tests to validate that reads in the mini-cluster are DISK_LOCAL rather than REMOTE.
Attachments
Issue Links
- causes
-
IMPALA-11614 TestValidateMetrics.test_metrics_are_zero fails with num-missing-volume-id for Ozone
- Resolved
- is depended upon by
-
IMPALA-11541 Test getStorageIds for block location with Ozone
- Open
- relates to
-
IMPALA-11457 Ozone parallelism reduced when backends are co-located
- Resolved
-
HDDS-7065 BlockStorage interface should return IDs for getStorageIds
- Open