You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Tian Jiang (Jira)" <ji...@apache.org> on 2020/10/23 02:12:00 UTC
[jira] [Assigned] (IOTDB-854) [Distributed] Limit the memory
foorprint of the committed log cache
[ https://issues.apache.org/jira/browse/IOTDB-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tian Jiang reassigned IOTDB-854:
--------------------------------
Assignee: Tan xinyu
> [Distributed] Limit the memory foorprint of the committed log cache
> -------------------------------------------------------------------
>
> Key: IOTDB-854
> URL: https://issues.apache.org/jira/browse/IOTDB-854
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/Cluster
> Reporter: Tian Jiang
> Assignee: Tan xinyu
> Priority: Major
> Labels: distributed, log-management
>
> Different from other K-V systems using the raft algorithm, Distributed IoTDB store significantly larger amounts of data in a raft log (as data ingestion of IoTDB is usually suggested in a batched manner). As a result, normal log management which concerns the number of log entries may not work very well, and risks in OOM.
> So, it is important that we calculate the memory occupation of committed logs and put a limit on them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)