Uploaded image for project: 'Kylin'
  1. Kylin
  2. KYLIN-3718

Segments in volatile range is more than designated value

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: v2.3.0, v2.4.0, v2.5.0
    • Fix Version/s: v2.6.0
    • Component/s: Metadata
    • Labels:
      None

      Description

      I have designated the volatile value of the cube to 1 and the auto merge thresholds is 3, but I found the former 3 segments was not merged when the 4th segment was ready.

      the ready segments are as below:

      1. xxx[20181201000000_20181202000000]
      2. xxx[20181202000000_20181203000000]
      3. xxx[20181203000000_20181204000000]
      4. xxx[20181204000000_20181205000000]

       Besides, I found the log info:

      segment in volatile range: xxx[20181203000000_20181204000000]
      segment in volatile range: xxx[20181204000000_20181205000000]

      I think the expected result should be:

      seg: xxx[20181204000000_20181205000000] should be reserved

      seg: xxx[20181201000000_20181202000000],xxx[20181202000000_20181203000000],xxx[20181203000000_20181204000000] should be merged.

      However, the truth is:

      When the 5th segments was ready, the former 3 segments were automatically merged.

      Although the value of volatile range is 1, there are always 2 segments will be reserved.

        Attachments

        1. KYLIN-3718.master.001.patch
          1 kB
          Temple Zhou

          Activity

            People

            • Assignee:
              temple.zhou Temple Zhou
              Reporter:
              temple.zhou Temple Zhou
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: