Closed niklasvincent closed 8 years ago
:+1:
Re prebaking the binaries into the ami - they are around 90MB, that could add a non negligible amount of time to the packer build time, and maybe have an impact on the amount of time it takes to start up an instance from the ami, I'm not sure. Maybe a better solution would be to put them in an S3 bucket somewhere? That would be faster than downloading them from mongo each time.
@philmcmahon I've changed the the script to try a public S3 bucket first and then use the official internet mirror if it can't find the version in the bucket.
:+1:
We've noticed during our disaster recovery simulations that a step that is stealing precious time getting back up and running is to get the MongoDB binaries in order to reset the OpLog and setting up the cluster again.
The way we've set up the fully Ops Manager orchestrated instances is that they download their binaries from Ops Manager, so by default there are no binaries available on the machine when they have just booted up.
This PR adds a small script
/opt/features/mongo24/scripts/install-binaries-only.sh
that downloads and unpacks the binaries for a specific MongoDB release.Future usage might be to add the version(s) of MongoDB we know we need to the AMI so that they are readily available during a recovery situation.