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
![](https://secure.gravatar.com/avatar/780232e12b5c41adc3bc37e6438624b8?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)