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

Posted to notifications@iotdb.apache.org by "Liuxuxin (Jira)" <ji...@apache.org> on 2021/11/04 05:57:00 UTC

[jira] [Created] (IOTDB-1925) Fix the modification of max_select_unseq_file_num_in_each_compaction parameter does not take effect

Liuxuxin created IOTDB-1925:
-------------------------------

             Summary: Fix the modification of max_select_unseq_file_num_in_each_compaction parameter does not take effect
                 Key: IOTDB-1925
                 URL: https://issues.apache.org/jira/browse/IOTDB-1925
             Project: Apache IoTDB
          Issue Type: Bug
    Affects Versions: 0.12.2
            Reporter: Liuxuxin
            Assignee: Liuxuxin
             Fix For: 0.12.3
         Attachments: 1.png

# Description
No matter how much we modify the value of parameter max_select_unseq_file_num_in_each_unseq_compaction in the configuration file, its value is always 2000 (default value) when IoTDB starts.
# Cause
When IoTDBDescriptor parsing the configuration file, it uses a wrong key "max_open_file_num_in_each_unseq_compaction" to get the value of this parameter. But the key of this parameter should be "max_select_unseq_file_num_in_each_unseq_compaction"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)