Add compound indexes support for Ops Manager managed Sharding
What is the problem that needs to be solved? Ops Manager Automation does not take into account compound indexes (https://docs.mongodb.com/manual/core/index-compound/), e.g. if we have { a: 1, b: 1 } index already exist Ops Manager will still create { a: 1 } index for a Shard Key.
Why is it a problem? (the pain) This creates unnecessary indexes with performance impact on the MongoDB Server process.
2
votes
Alexey
shared this idea