MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Completed
Created by Guest
Created on Sep 21, 2021

RELATED FEEDBACK

k8s operator - Support different different size shard configuration

We would like to implement the Hot-cold shard strategy to move the cold data to a shard which has more disk usage and less compute power and not frequently used and Hot data in a shard with more compute power. This strategy is described here: https://docs.mongodb.com/manual/tutorial/sharding-tiered-hardware-for-varying-slas/ Currently the enterprise operator does not support different size shards, this request is to allow operator to create different size shards.
  • ADMIN RESPONSE
    Aug 1, 2025
    We have recently released the ability to support different sized shards and that enables the scenario described in this idea. This is supported in 1.19.1 of the Operator, the release notes can be found here ( https://www.mongodb.com/docs/kubernetes-operator/stable/release-notes/#improvements ) and the relevant section is as follows: * Allows you to configure podSpec per shard in a MongoDB sharded cluster by specifying an array of podSpecs under the spec.shardSpecificPodSpec setting for each shard.
  • Attach files