You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Kirill Gusakov (Jira)" <ji...@apache.org> on 2023/08/25 08:07:00 UTC

[jira] [Updated] (IGNITE-20273) Breakdown for zone-based collocation

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

Kirill Gusakov updated IGNITE-20273:
------------------------------------
    Epic Link: IGNITE-19170

> Breakdown for zone-based collocation
> ------------------------------------
>
>                 Key: IGNITE-20273
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20273
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Gusakov
>            Assignee: Kirill Gusakov
>            Priority: Major
>
> Based on the current design goals we need to prepare the tickets' breakdown for the first phase of collocation [design|https://github.com/gridgain/apache-ignite-3/blob/1abb67c8770179d5d3e295876b73893f3845a08e/modules/distribution-zones/tech-notes/zone-collocation.md#L1]:
> Under the first phase we want to implement the following steps:
> - Store the table partitions data inside the one zone partition
> - Change the RAFT servers and clients management to support the separate start of zone partitions and start of table state machine listeners
> - Refactor the structure of our storage layer to support the many tables inside the one logical partition
> - Implement the way to configure available storages in node configs



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