Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6405

Evergreen task teardown should stop mongo-orchestration

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.11.0
    • Affects Version/s: None
    • Component/s: None
    • 2
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      In DRIVERS-2991 we fixed "Address already in use" when starting mongo-orchestration but the underlying cause is that the node driver is mistakenly not shutting down the MO server in Evergreen task teardown.

      For example, the python driver does this:

        "stop mongo-orchestration":
    - command: shell.exec
      params:
        script: |
          . src/.evergreen/scripts/env.sh
          set -o xtrace
          bash ${DRIVERS_TOOLS}/.evergreen/stop-orchestration.sh
...


post:
...
  - func: "stop mongo-orchestration"

            Assignee:
            durran.jordan@mongodb.com Durran Jordan
            Reporter:
            shane.harvey@mongodb.com Shane Harvey
            Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: