0 — OK

OK — MongoDB error code 0

Source code references

ErrorCodes::OK found in 56 locations in the MongoDB server source.

Detailed investigation data (common causes, diagnostic steps) is not yet available for this error code. The information above comes from the official MongoDB error code reference.

Related Issues

SERVER-101716Closed
read_through_cache.h function throws exception on noexcept method
_doLookupWhileNotValid [throws|https://github.com/mongodb/mongo/blob/0a68308f0d39a928ed551f285ba72ca560c38576/src/mongo/util/read_through_cache.h#L593-L598] (tassert) but [is noexcept|https://github.com/mongodb/mongo/blob/0a68308f0d39a928ed551f285ba72ca560c38576/src/mongo/util/read_through_cache.h#L556].
SERVER-136061Open
Add connect failure backoff to page reads to avoid hot spinning and using 100% CPU
This was surfaced from HELP-100704 where SLS resolved page server addresses that didn't resolve ("Domain name not found"). This was an SLS bug but while it was broken, mongod burned 100% CPU on every read The sendPageRequestSync loop is while(true) bounded only by the read's totalDeadline and has no sleep in order to keep page reads fast. The exponential backoff that exists is per page server in the writer thread but it fails fast. While a server is in backoff requests are rejected immediatel
SERVER-139513Backlog
Always propagate queryStatus in QueryExecutionContext::checkForInterrupt
The API contract for check_for_contract says this "Populates queryStatus with MONGO_EXTENSION_STATUS_OK unless this operation is in a killed state.", but we currently only populate query status if an interrupt was detected. Update behavior and stale comments to reflect that queryStatus is always populated.
SERVER-84645Closed
OCSP stapling log messages should indicate response validity
After an OCSP response acquisition attempt, several events might have occurred: * A network error * One or more responder errors * A response which failed signature validation * A response which failed to meet policy * A response which indicates the subject certificate was revoked * A response which indicates the subject certificate was valid There are probably a few other edge cases. Currently, the main OCSP stapling loop dispatches requests, then logs message {{577163}} which includes
SERVER-98423Closed
Results differ depending on the order of operands in $sum inside $group with optimizations on
This came up while investigating BF-35904. The minimized query looks like this The explain output for optimizations turned has the operands swapped like so while with optimizations off the operands remain in the same order this change comes from [ExpressionNary::optimize()|https://github.com/10gen/mongo/blob/27d91db841953662a6780bcc4faba34dc257bd5a/src/mongo/db/pipeline/expression.cpp#L3066] as it will hold the ExpressionConstant operand in a [separate array|https://github.com/10gen/mon
SERVER-138647Backlog
Waive quarantined test failure results from resmoke
Resmoke already skips tests that have been quarantined. However, there is a TOCTOU window where something could be quarantined during the run, and the result should be appropriately marked as "waived". This will also allow us to upload test results, specifically to trunk.io for further study of flaky signals.
SERVER-139415Closed
Fix MongoShellProgramSkipExtensionsSignatureVerificationTestCase setup of config defaults
Test case class MongoShellProgramSkipExtensionsSignatureVerificationTestCase directly modifies module level variables in module `buildscripts.resmokelib.config`. The values are not restored at teardown, thus breaking the isolation of each test. The purpose of this ticket is to modify the testcase so that it uses a context manager to modify the value, and to limit the change only to the variables which are actually needed.
SERVER-136023Closed
Prevent interrupt delinquency in $facet and $lookup by checking for interrupt in the sub-pipeline drain loops
$facet and $lookup each run entire sub-pipeline executions inside one {{doGetNext()}} call. Sub-pipeline stages check interrupts every 128 {{getNext()}} calls via {{Stage::getNext}} -> {{{}ExpressionContext::InterruptChecker{}}}, but (a) sub-pipelines processing fewer than 128 docs may never trip the amortized checker (each sub-pipeline has its own {{ExpressionContext}} counter), (b) per-input plan build/optimize/translate cost is check-free, and (c) blocking sub-stages expose their full span in
SERVER-139188In Code Review
Implement type narrowing for the remaining comparisons expressions
Follow up from SERVER-135984. After $eq works, the logic should be expanded to: $lt, $lte, $gt, $gte, $ne. Not $cmp - it will not be supported and it returns a number. $lt:["$a", "string"] constrains 'a' to be of the type string and types that sort before string. Should probably look like 'minKey|missing|null|undefined|number|string'. $ne does nothing unless the type is a singleton type - $ne: ["$a", "string"] cannot tell us the type of "a" but a != null can tell us it's not null.
SERVER-137997Backlog
Join optimization $expr equijoin treats BSON undefined as not equal to a missing field
*Minor* because undefined is a deprecated BSON type. Aggregation $eq considers undefined equal to a missing field, and classic/SBE $lookup return the row. The JOO hash join buckets fillEmpty(path, null), so undefined never meets the null produced for missing; the index probe seeks undefined while the index stores missing as null.