[
https://issues.apache.org/jira/browse/IOTDB-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735529#comment-17735529
]
周沛辰 commented on IOTDB-5589:
----------------------------
*Description*
* There are too many merged scheduled threads, in which each {{dataRegion}}
has a scheduled scheduling thread.
* After the {{StorageGroup}} is deleted, the compaction scheduled threads of
each {{dataRegion}} corresponding to it are not released, resulting in thread
leakage.
*Solution*
* Put the compaction scheduled threads in the {{CompactionTaskManager}} class
for global management, and the global default number of threads is 2.
* When creating a {{{}DataRegion{}}}, it will register with the
{{{}CompactionTaskManager{}}}, so that the files under the
{{{}dataRegion{}}}can be selected by the scheduled thread and submit the task.
When deleting the {{StorageGroup}} or when the system exits or meets an
exception, it is necessary to unregister with the {{{}CompactionTaskManager{}}}.
> [ compaction ] The "IoTDB-Compaction_Schedule" thread count needs to be
> controlled
> ------------------------------------------------------------------------------------
>
> Key: IOTDB-5589
> URL: https://issues.apache.org/jira/browse/IOTDB-5589
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: mpp-cluster
> Reporter: 刘珍
> Assignee: 周沛辰
> Priority: Major
> Labels: pull-request-available
> Attachments: comp1.conf, comp2.conf, dn_stack.out
>
>
> master_a3869ec_opt
> Each time partition opens a "IoTDB-Compaction_Schedule" thread，it's not a
> good design.
> 示例：
> 在192.168.10.68 （72CPU) ,
> start-standalone.sh启动单节点集群，运行附件中的脚本，生成72个dataregion，每个dataregion
> 下目前只有1个时间分区，所以当前"IoTDB-Compaction_Schedule"线程数有72个，随着时间分区的增加，这个线程也会增大，需要控制，它的主要作用是用来选择合并文件，是比较快的操作，没必要开这么多。
> 纠正：是每个dataregion 有1个 "IoTDB-Compaction_Schedule"
> thread，是否解决，可以讨论。如果dataregion多，是否有必要开这么多选文件的线程。
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
