You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Jialin Qiao (Jira)" <ji...@apache.org> on 2022/07/04 01:47:00 UTC
[jira] [Assigned] (IOTDB-3455) Add partition table in LocalConfigNode
[ https://issues.apache.org/jira/browse/IOTDB-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jialin Qiao reassigned IOTDB-3455:
----------------------------------
Assignee: Liuxuxin
> Add partition table in LocalConfigNode
> --------------------------------------
>
> Key: IOTDB-3455
> URL: https://issues.apache.org/jira/browse/IOTDB-3455
> Project: Apache IoTDB
> Issue Type: Improvement
> Reporter: Jialin Qiao
> Assignee: Liuxuxin
> Priority: Major
>
> ConfigNode is a process used in the new cluster. To make the processing logic clear, we need to fake a ConfigNode in the new standalone version, called LocalConfigNode, which is a module but not a process.
>
> Currently, in the new Standalone version, we just allocate one DataRegion and one SchemaRegion for each Storage Group. This means the virtual_storage_group_num is always 1.
>
> In the future, we'd better support extending a Standalone version to 3 replication in Cluster.
> Thus, we need to do the following things:
>
> (1) Add LocalDataPartitionTable (SeriesPartition -> TimePartition -> DataRegion)
> (2) Add LocalSchemaPartitionTable (SeriesPartition -> SchemaRegion)
> (3) Persist the LocalPartitionTable
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)