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 Submitted
Categories Database
Created by Guest
Created on Sep 18, 2025

RELATED FEEDBACK

Per-Shard Change Stream and Triggers to improve scalable/performance/resilience

In our geo-sharded cluster, we use Change Streams and Atlas Triggers. Most of our pipelines include a match for the shard key - so we can process the data in the same region where the data resides. However, due to the design of change streams with sharded clusters, the change streams are collected from all shards even if the pipeline matches only a specific match. In addition, if a shard has no changes to report, mongos waits up to 10 seconds (by default) before responding to the driver. This makes the data processing too slow. This suggestion would also greatly improve scalable, performance and resilience of a MongoBD Global Cluster by *not* waisting resources on unrelated shards.