Feedback

Use dedicated interface for replication and balancing

Like many other big database system, MongoDB may support to specify dedicated interfaces for replication and/or for the balancer (sharding) Currently you can configure replication sets and shards members only by single hostname/IP-Address, i.e. *...

Wernfried Domscheit almost 4 years ago in Replication & Sharding 0 Submitted

1 VOTE

allow mongosync to migrate few field from source to destination for collection in database

right now mongosync will migrate all the fields from source to destination based on filter or non filter setting but there is no way to move few field out of all field for all document to migrate few field from source to destination for collect...

Dasharath Dixit almost 2 years ago in Replication & Sharding 0 Submitted

2 VOTE

Ability to replicate the data within a cluster to another cluster

Two different scenarios. One scenario is to have a DR cluster. 2 independant clusters that are one way synced. As of right now, a custom CDC solution (custom code + Kafka) is needed to achieve this. Another is because of latency and the requirem...

Guest over 4 years ago in Replication & Sharding 0 Submitted

1 VOTE

an aggregation stage to load data to DRAM for the fields that are only requested

When we use $project stage, it loads whole document from disk to memory (if not in working set). Because of this, When we create a data model, We have to create separate collection if the field is not required in frequent access of data. Creating ...

Guest over 2 years ago in Performance & Optimization 0 Submitted

1 VOTE

Avoid truncating the query on the Atlas profiler or system.profile collection

Slow running queries that are captured in system.profile collection or on profiler page of Atlas are truncated if the query is too long. As an Application DBA, it would be difficult to analyse the query without figuring out the actual query. The c...

Guest almost 3 years ago in Performance & Optimization 0 Submitted

1 VOTE

Combine reshardCollection+mongosynd idea to support a remote collection on a separate new cluster

Great for prod productivity and 99.999 SLA if mongo could support this, for example, Given "mydb.mycoll" in current cluster being sharded with {zip:1} shard key 1/ New cluster: sh.shardCollection( "mydb.mycoll", {name:1, phone:1} ) 2/ "Mongocopy...

Guest about 3 years ago in Replication & Sharding 0 Submitted

1 VOTE

throttle sessions which use too much resources

We have different types of applications : 1. Writer - to load data into mongodb from different data sources 2. Reader - to read data and display to end user. Normally, there is strict SLA for reader , but no SLA (or less restricted) for writers. ...

Guest about 3 years ago in Performance & Optimization 0 Submitted

1 VOTE

Improve sorting performance

Sorting always ends up doing a collection scan when the selected index for the find/match does meet the sort requirement. The sort effectively makes the performance worse by 15-25 times for the "matched" dataset which runs into 10s of thousands (n...

Guest over 3 years ago in Performance & Optimization 0 Submitted

1 VOTE

Build MongoDB with PGO

I would like to see support for PGO (and even LLVM Bolt) in the upstream. Would be awesome if MongoDB will distribute PGO-optimized binaries, so the users will be able to see an additional performance boost "for free". At least describe to the use...

Guest over 3 years ago in Performance & Optimization 1 Submitted

1 VOTE

Support $documents on shards

The new aggregation operator $documents cannot be used together with $merge in a sharded cluster, you get an error: ``` db.aggregate([ { $documents: [ { _id: ObjectId("6616b08a610fab3e84d2d4ee"), a: 'foo', shardKey: 1 }, ] }, { $merge: { in...

Wernfried Domscheit over 3 years ago in Replication & Sharding 0 Submitted

Please enter your email address

FILTER BY CATEGORY