Description

SERVER-51358 adds the "awaitable":"true" field that cleanly identifies the new awaitable isMaster commands that can overwhelm currentOp output on 4.4+ clusters with a large number of connections.

Can we please add to the Current Op documentation something to the effect of:

currentOp output can include awaitable operations on a per-connection basis, which may not be consuming resources on the server side. To suppress these, use the filter {awaitable:{$ne:true}}

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)