You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2025/06/24 07:41:00 UTC

[jira] [Resolved] (IGNITE-25387) Spread data across several physical devices

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

Nikolay Izhikov resolved IGNITE-25387.
--------------------------------------
    Resolution: Fixed

> Spread data across several physical devices
> -------------------------------------------
>
>                 Key: IGNITE-25387
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25387
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: ise
>             Fix For: 2.18
>
>
> IGNITE-25305 allow to the user to configure separate storage (physical disk) for each cache. 
> But, in many scenarious user have one big cache group and all others significantly smaller.
> So, it will be convinient to the user to spread partitions of single cache group to several physical devices.
> This will allow to spread load more evenly.
> Note, we don't want to break existing big clusters and want to allow to update them step by step.
> So, In case config updated for several disks, but existing deployment store files on the one disk Ignite must continue to work correctly.
> We want to do several changes:
>   # Remove ability to configure storage per DataRegion. 
>   # Add ability to configure storage per Cache group (CacheConfiguration).
>   # Add ability to configure several storages for single Cache group. To spread data of one big cache over disks.
>   # Add ability to configure explicit storage for index partition. Because, it much bigger then any other.
>   # Support control.sh command that will move existing files to the storages according current IgniteConfiguration.



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