You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2023/10/19 22:53:00 UTC

[jira] [Resolved] (IMPALA-12115) Must rebuild minicluster to switch filesystems

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

Michael Smith resolved IMPALA-12115.
------------------------------------
    Fix Version/s: Impala 4.4.0
       Resolution: Fixed

> Must rebuild minicluster to switch filesystems
> ----------------------------------------------
>
>                 Key: IMPALA-12115
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12115
>             Project: IMPALA
>          Issue Type: Task
>          Components: Infrastructure
>            Reporter: Michael Smith
>            Assignee: Michael Smith
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> When switching between HDFS, Ozone, S3, and erasure-coded variants, Impala's minicluster uses the same directory for config and data. That means any time you want to test a different one, you need to replace the current minicluster config/data (particularly data load) which can take awhile. When switching from erasure-coding, you usually need to wipe out the directory because it has too many nodes configured and build scripts don't know to clean them up.
> It would be useful to be able to switch between these configurations more quickly in a dev environment by preserving each. You can manually do that by setting {{IMPALA_CLUSTER_NODES_DIR}}, but that's an extra step to remember to do every time. We should set the directory based on {{TARGET_FILESYSTEM}} and {{ERASURE_CODING}} so they're automatically preserved.



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