Analytics node tier prorating
Parent: Atlas Cluster Topology and Tier Economics · Published reference · snapshot 2026-10-24 · skill mongodb-cohort-047d3a5eff67
↓ Facts as markdownall context files
Source-anchored research for Analytics node tier prorating. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Definitions
- Analytics nodes add to the bill; prorating is not a promise of lower total spend. Studio 3T identifies workload-isolated analytics nodes as optional costs, and MongoDB's announcement describes them as additional read-only nodes. (medium confidence) [source]
How it works
- A substantially lower analytics tier can cause replication lag and loss of oplog coverage. Node-level savings therefore require checking replication feasibility. (low confidence) (verified as of 2026-10-23) [source]
- Patrick McLain's September 28, 2022 incident account reports that secondaryPreferred with analytics tags fell back to the primary when analytics reads failed, degrading operations; changing to secondary restored isolation. Paying for an analytics tier alone did not deliver isolation in that incident. (low confidence) [source]
Comparisons and alternatives
- PointFive's FinOps guidance identifies pricing the entire operational cluster for occasional analytics as waste and recommends separate analytics tiers; this echoes MongoDB's stated cost rationale, rather than independently measuring prorating. (medium confidence) [source]
Facts and statements
- Atlas prices a selected analytics tier like the same base tier, then adjusts a differing analytics tier on a prorated per-node basis; the create/edit UI displays the price. (low confidence) (verified as of 2026-10-23) [source]
- Dedicated M10+ clusters can use an analytics tier above or below the operational tier, so analytics compute can change without resizing every operational node. (high confidence) (verified as of 2026-10-23) [source]
- MongoDB announced independent analytics tiers on August 3, 2022, updated August 23; previously analytics nodes used the same tier as other cluster nodes. (low confidence) [source]
- On Atlas Core, disk size and IOPS must match across node types; a lower analytics compute tier does not imply separately reduced storage or IOPS. (low confidence) (verified as of 2026-10-23) [source]
- Atlas Core Local NVMe SSD requires matching base and analytics tier levels, limiting the use of a cheaper analytics tier. (low confidence) (verified as of 2026-10-23) [source]
- Atlas Operator 2.13.1 release notes removed its same-instance-size restriction for analytics nodes. Operator users should distinguish an integration's validation restriction from Atlas's independently selectable analytics tier capability. (medium confidence) [source]
Children
- No children recorded.