Known Issues
5166 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-139520Backlog
Documentation Updates
This ticket is to update all types of documentation API Guide,
Programming Guide, and Architecture Guide related to the project.
SERVER-139430In Code Review
Allow cutback at ORP staged read bounds
Add a callback between successful ORP read stages so the standby can decide whether to continue reading from ORP or return for LS cutback. Return the last successfully enqueued LSN and ensure we can tell apart cutback from a fully read stream.
SERVER-101716ClosedFixed
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].
Affected Versions
7.0.08.1.0-rc08.0.0
Fixed Versions
8.2.0-rc08.0.107.0.22
SERVER-119413ClosedFixed
configTerm is expected as an int32 but can be an int64
In repl_set_config.idl the [configTerm|https://github.com/10gen/mongo/blob/master/src/mongo/db/repl/repl_set_config.idl#L174] field has a max value of int max but is derived from the term field of the original primary. If the term that is used here were to ever be above int::max and below int64::max that would cause a parsing crash. configTerm should be parsed as a long long like other uses of term in the code.
This also requires changes to repl_set_heartbeat_response.h/cpp since we store the
Fixed Versions
8.3.0-rc08.2.78.0.217.0.32
SERVER-134166Investigating
Complete TODO listed in SERVER-121823
There is a TODO in the codebase referencing a resolved ticket which is assigned to you.
Please follow this link to see the lines of code referencing this resolved ticket:
https://github.com/10gen/mongo/search?q=SERVER-121823&type=Code
The next steps for this ticket are to either remove the outdated TODO or follow the steps in the TODO if it is correct. If the latter, please update the summary and description of this ticket to represent the work you're actually doing.
SERVER-130386Open
Try disagg measure startup tasks with retry on crash
We run into a variety of issues when we try startup with larger number of tables (>200k). We should see what happens if we simply try to restart from where we left off if we had crashed. This allows us to uncover potentially more issues and get signal on what happens in these cases
SERVER-138011ClosedFixed
Don't rely on counting log messages in the initial sync fuzzer
Fixed Versions
9.1.0-rc09.1.0-rc1025
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-137274In Progress
Replace dummy indexes with schema constraints in JS tests
In the JS tests for JOO, we often create dummy indexes for arrayness information. Once the type inference project is ready to infer arrayness from schema constraints, these indexes should be replaced with schema constraints.
SERVER-139516Backlog
Use efficient result materialization for streaming SBE group roots
Allow root {{STAGE_STREAMING_GROUP}} plans to request ResultInfo under {{featureFlagSbeEfficientBoundaryMaterialization}}, matching hash aggregation and avoiding whole-result object materialization in the SBE plan.
* Reuse shared group finalization and preserve compound {{_id}} objects and null versus missing keys.
* Add plan-shape and BSON/Document result-materialization regression tests.
SERVER-137757In Code Review
Tag Server Integration tasks as release_critical
The ask for each team:
- Insert the “Team Plan Template” into your team’s Infinite Burndown plans in its own tab
- Audit your list of tasks under your assigned_to_jira_team_<name> tag. See mongodb-mongo-master config: https://github.com/10gen/mongo/blob/master/etc/evergreen.yml, mongodb-mongo-master-nightly config: https://github.com/10gen/mongo/blob/master/etc/evergreen_nightly.yml, and task definition YAMLs: https://github.com/10gen/mongo/tree/master/etc/evergreen_yml_components/tasks (many
SERVER-136809Open
Server parameters for ORP fallback values
The design has a few numbers that we've handwaved, for eg. loop limit before we check for a newer checkpoint, ORP connect retry backoff, ORP stream retry limit, no progress timeout etc.
Make these values runtime settable server parameters with reasonable defaults so we can tune them at runtime
Also consider if we should make ORP behaviour enabled behind a server parameter so we can quickly kill it at runtime if needed.
SERVER-136804Open
Make startup ORP catchup exempt from the secondary lag watchdog
A standby catching up from ORP at startup is by definition definitely more than 2 minutes behind so SecondaryLagWatchdog will crash it mid catchup and we end up in the same restart loop
Either we should exempt the watchdog from running during ORP catchup or we should increase its limit during this time until we cutback to LS. I'm not sure how easy it is to pick a reasonable limit to increase to, so I'd think the less risky option here is to exempt.
Should also check oplogCatchUpForStepUp
SERVER-136471Open
Suppress page server warnings in offline validation
Reconsider page server logging for offline validation.
In the linked validation log, I observed 14,548 of the 20,489 lines (71%) were one repeated warning (logid: 13067400):
"No candidate page server is known to have materialized the requested LSN, continuing with existing routing"
Another warning, (logid: 13295600) "ClosedSegmentCompletionTracker: materialization frontier has not advanced", fires once a minute per cell for the whole run with frontier: "none". StalledMillis begins
SERVER-136866Open
clean observer/provider interfaces for mat tracker
in SERVER-136190 and SERVER-136120 observer interfaces were added but the relative lifetime of the observer/observation are unclear, and we just use smart ptrs/reference wrappers.
We should create proper reusable observer infrastructure to facilitate things like this.
SERVER-138893ClosedFixed
Normalize set types when materializing objects in SBE
Fixed Versions
9.1.0-rc09.1.0-rc1026