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

Add logging to tenant_migration_concurrent_migrations_stress_test.js to find possible discrepancy in currentOp report

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 5.1 Required
    • Fix Version/s: 5.1.0-rc0
    • Component/s: None
    • Backwards Compatibility:
      Fully Compatible
    • Linked BF Score:
      141

      Description

      The test tenant_migration_concurrent_migrations_stress_test is using 
      currentOp command to wait for all migrations to complete. In every stuck test one or more migrations is in Aborted state fetched from the currentOp output, however from the actual log all migrations completed without error.
       
      The currentOp takes `_durableState.state` value to report on migration state. This investigation may prove that the `_durableState.state` might be in Aborted state for a migration that completed without error.
       
      This bug is to improve diagnostics.

        Attachments

          Activity

            People

            Assignee:
            andrew.shuvalov Andrew Shuvalov
            Reporter:
            andrew.shuvalov Andrew Shuvalov
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: