[
https://issues.apache.org/jira/browse/IGNITE-25387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-25387:
-------------------------------------
Description:
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:
1. Remove ability to configure storage per DataRegion.
2. Add ability to configure storage per Cache group (CacheConfiguration).
3. Add ability to configure explicit storage for index partition. Because, it
much bigger then any other.
4. Add ability to configure several storages for single Cache group. To spread
data of one big cache over disks.
5. Support control.sh command that will move existing files to the storages
according current IgniteConfiguration.
was:
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.
> 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
> Priority: Major
>
> 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:
> 1. Remove ability to configure storage per DataRegion.
> 2. Add ability to configure storage per Cache group (CacheConfiguration).
> 3. Add ability to configure explicit storage for index partition. Because, it
> much bigger then any other.
> 4. Add ability to configure several storages for single Cache group. To
> spread data of one big cache over disks.
> 5. 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)
