[SERVER-18169] Regression: Auth enabled arbiter cannot be shutdown using command Created: 22/Apr/15  Updated: 22/Jun/15  Resolved: 28/Apr/15

Status: Closed
Project: Core Server
Component/s: Admin, Security
Affects Version/s: 3.0.0
Fix Version/s: 3.0.3, 3.1.3

Type: Bug Priority: Major - P3
Reporter: Anil Kumar Assignee: Amalia Hawkins
Resolution: Done Votes: 0
Labels: ET
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-18140 Allow getParameter to be executed loc... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Security 2 04/24/15, Security 3 05/15/15
Participants:

 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>.



 Comments   
Comment by Amalia Hawkins [ 28/Apr/15 ]

The fix for this ticket will be pushed as part of SERVER-18140.

Generated at Thu Feb 08 03:46:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.