Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-56882

unable to complete full validation on collection after failed hashed index insert

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2021-10-04, Storage - Ra 2021-09-06
    • 18
    • 0

      Add regression tests for WT-8126 to jstests/noPassthrough.

      The validation warnings reported previously in this ticket have been resolved in the storage engine in this commit containing WT-8126. The work remaining for this ticket is to provide regression coverage at the server level.


      OLD DESCRIPTION

      A failed insert into a collection with a hashed index cause the server to end up in a state where validate({full: true}) fails to complete and returns "Could not complete validation of table:index-NNN. This is a transient issue as the collection was actively in use by other operations." warnings.

      This state seems to persist for an extended period in spite of checkpointing activity observed in the server logs.

      It would be useful to understand if this is an issue in the storage engine or at the integration layer above it.

        1. validate_empty_collection.js
          1 kB
          Benety Goh
        2. validate_hashed_index.js
          2 kB
          Benety Goh

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: