You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr Polovtsev (Jira)" <ji...@apache.org> on 2024/04/29 07:16:00 UTC

[jira] [Updated] (IGNITE-19762) Revisit data region management in rocksdb

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

Aleksandr Polovtsev updated IGNITE-19762:
-----------------------------------------
    Reviewer: Roman Puchkovskiy

> Revisit data region management in rocksdb
> -----------------------------------------
>
>                 Key: IGNITE-19762
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19762
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Bessonov
>            Assignee: Aleksandr Polovtsev
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Right now it's not really straightforward, what these regions mean.
> After https://issues.apache.org/jira/browse/IGNITE-19591, they are associated wit a separate rocksdb instance each, in which case it's unfair to call them regions anymore. More like storages.
> But we still use the same non-configurable path, so there are no immediate advantages over it. We must provide an adequate design for regions and storages, basicacaly, and clean the mess that we currently have.



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