Feedback

Support DB2 on Z (the mainframe)

Since, most of enterprise data, still is on the Z platform, the mainframe, it is sub-optimal, that MongoDB, has decided not to support integrating with this product. An alternative would be to do it via a distributed DB2 which could work almost eq...

Guest over 1 year ago in Relational Migrator 0 Submitted

1 VOTE

Complete information on Review Summary

I suggest that all selected configurations and information be displayed on the ‘Review Summary’ screen before starting the migration job. For example, if the user selects the ‘Drop destination collections before migration’ and ‘Verify migrated dat...

Guest about 1 year ago in Relational Migrator 0 Submitted

1 VOTE

deleteMany() execution automatically disable the balancer on sharded clusters

Marco Barbierato about 1 year ago in Replication & Sharding 0 Submitted

2 VOTE

Migrate with GitHub

No description provided

Guest almost 3 years ago in Relational Migrator 1 Submitted

1 VOTE

Scheduled stepdown for smoother primary election

Stepdown is a great tool that allows us to keep clusters operating smoothly. We use it for example when we want to perform some maintenance work on the host where the primary is currently running, to perform a rolling upgrade, and in many other ca...

Guest almost 2 years ago in Replication & Sharding 0 Submitted

2 VOTE

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

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

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