[ 
https://issues.apache.org/jira/browse/IGNITE-19762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841870#comment-17841870
 ] 

Aleksandr Polovtsev commented on IGNITE-19762:
----------------------------------------------

I'm going to close this issue and remove this TODO along with removal of any 
mentions of data regions in the storage. This ticket is old and we should 
probably create a new one if we find out that current profile configuration is 
not sufficient.

> 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)

Reply via email to