[jira] [Resolved] (IMPALA-11457) Ozone parallelism reduced when backends are co-located

["Michael Smith (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-11457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Smith resolved IMPALA-11457.
------------------------------------
    Fix Version/s: Impala 4.2.0
       Resolution: Fixed

> Ozone parallelism reduced when backends are co-located
> ------------------------------------------------------
>
>                 Key: IMPALA-11457
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11457
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 4.1.0
>            Reporter: Michael Smith
>            Assignee: Michael Smith
>            Priority: Critical
>             Fix For: Impala 4.2.0
>
>
> When Impala and Ozone backends are co-located (at the same IP address), access to Ozone will use a local filesystem access path. It's supposed to assign each backend a separate disk ID so access happens in parallel, but a bug in assigning queues when storage ID is unknown results in all Ozone backends sharing the same queue. This results in reduced parallelism as the queue uses a single I/O thread.
> To make Impala see Ozone as co-located in a dev environment, start Impala with {{--hostname=localhost}} (which is already the default for Ozone).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)