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

Regression: Auth enabled arbiter cannot be shutdown using command

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.3, 3.1.3
    • Component/s: Admin, Security
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Security 2 04/24/15, Security 3 05/15/15

      Description

      Issue Status as of Apr 29, 2015

      ISSUE SUMMARY
      Because arbiters do not replicate data, they do not have a copy of a replica set's credentials, and therefore refuse all authentication attempts when auth is required. As a result certain operations required for basic maintenance and for integration with MMS, that were previousily available via the localhost exception, are no longer possible.

      This change makes following operations available to clients that have access to an arbiter via the localhost exception:

      • getCmdLineOpts
      • serverStatus
      • getParameter
      • shutdown

      WORKAROUNDS

      None.

      AFFECTED VERSIONS

      3.0.0, 3.0.1, and 3.0.2

      FIX VERSION
      The fix is included in the 3.0.3 production release.

      Original description

      In 2.6, it was possible to shutdown an arbiter that was part of auth enabled replica-set. In 3.0 this is no longer possible due to access restriction and the only possible way to stop an arbiter is by performing a kill <pid>.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: