Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-11686

MVCC: Create separate test for vacuum checks.

    XMLWordPrintableJSON

    Details

    • Type: Test
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: mvcc
    • Ignite Flags:
      Docs Required

      Description

      Most of tests (inherited from CacheMvccAbstractTest) run vacuum synchronously on afterTest() method and check if vacuum is ok. This hits performance, can cause false negative results and
      vacuum issues can be hidden if afterTest method will overriden at once.

      For now we have CacheMvccVacuumTest that just check vacuum workers state, but there is no check if vacuum really cleans all old versions correctly. I'd expect to find it in this class.

      So, let's mode vacuum verification from afterTest method into CacheMvccVacuumTest as a new separate test.

       

        Attachments

          Activity

            People

            • Assignee:
              Diana Diana Iakovleva
              Reporter:
              amashenkov Andrey Mashenkov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: