[IOTDB-1019] [Distributed] Memory control of the cluster engine

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Core/Cluster, Core/Engine
• Assignee: Unassigned
• Reporter: Houliang Qi
• Created: 19/Nov/20 04:25
• Updated: 19/Nov/20 04:50

Description

We are glad to see that robust memory control is provided in a stand-alone engine to prevent OOM. However, this memory control only considers the memory occupied by the single engine, and does not consider the memory occupied by the distributed engine (such as the raft logs kept in the memory), which may cause OOM in a distributed cluster.

 

There are two possible solutions to this problem:

1. Set a configuration parameter to control the maximum memory in the view of a single engine (not the maximum memory of the JVM)

2. Consider the memory occupied by the cluster engine.

I think the first one would easier and helpful enough.

Any ideas?

 

Issue Links

• is a child of: IOTDB-68 IoTDB supports distributed version