[DOCS-6652] Update use cases for the noop scheduler recommendations Created: 25/Nov/15  Updated: 30/Oct/23  Resolved: 23/Aug/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Critical - P2
Reporter: Luke Prochazka Assignee: Ian Fogelman
Resolution: Done Votes: 0
Labels: reopened, server-docs-bug-bash, triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All virtualised Linux builds running on VMware hypervisors


Issue Links:
Related
is related to DOCS-4577 Filesystem elevator recommendations Closed
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago

 Description   

In the current docs located at https://docs.mongodb.org/manual/administration/production-notes/#scheduling-for-virtual-devices, we make a blanket assertion that the noop scheduler is recommended in virtualised environments. However, this was derived from the VMWare KB located at: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2011861 which states preconditions that apply to only a minority of use cases.

I would like the docs to replace the recommendation for noop for virtual devices to be replaced with the "cfq" scheduler. The noop scheduler is only recommended when the following conditions are met:

  1. A replica set topolog or sharded cluster is used
  2. The VM are located on the same virtual host
  3. The underlying storage containing the DBpaths is a common blockstore (LUN)
  4. The hypervisor is VMware based (ESXi etc)

Please note that AWS does not meet these conditions.



 Comments   
Comment by Luke Prochazka [ 01/Nov/22 ]

Inappropriately closed by the bot, request is still looking for an update from the DOCS team.

Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:52:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.