Uploaded image for project: 'Apache IoTDB'
  1. Apache IoTDB
  2. IOTDB-1925

Fix the modification of max_select_unseq_file_num_in_each_compaction parameter does not take effect

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.12.2
    • 0.12.3
    • None
    • 2021-10-DragonGate

    Description

      1. 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.
      2. 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"

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ThuLiuxuxin Liuxuxin
            ThuLiuxuxin Liuxuxin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1h
                1h
                Remaining:
                Remaining Estimate - 1h
                1h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Agile

                  Completed Sprint:
                  2021-10-DragonGate ended 08/Nov/21
                  View on Board

                  Slack

                    Issue deployment