The The Community is live! Post new content or topics so our teams can assist.

Please contact your support team if you have a question or need assistance for any Rackspace products, services, or articles.

migrating to parse post - disable object-rocket

Hi, This is a question for Amanda Clark. 

Thank you for the post about migrating. I'm wondering how easy it is to decouple the object-rocket from the stack and just use a local mongodb instance? If I use that orchestration will that be difficult?



No Data
  • Hello Jim,

    Many thanks for the question. I'll try to cover all the aspects related to running a MongoDB instance locally.

    Doing this is, for sure, possible.

    If you request this from us, we can provide the backup of the instance. You can then install mongodb locally, import the dump and it shouldn't be a big issue.

    Before proceeding with this however, please consider a few aspects.

    With OR Mongo you have access to DBA services. Basically if you are having issues with performance, indexes, queries, you now have a dedicated team of DBAs and CDEs that are there to support and help you out. This is only happening with this product in Rackspace so that you can mind your code and not Mongo. If you run MongoDB locally, you will have a lot of new things to manage.

    Mongo by default doesn't offer any security or redundancy.

    Running a single instance of Mongodb is not recommended and it's recommended to at least run a replicaset. In order to make sure you're not running into issues with electing a new primary, you will have to have at least a Primary, a Secondary and an Arbiter(which is not a data bearing node). With OR Mongo you are getting 3 data nodes as our replicasets are made out of a PRIMARY and two SECONDARIES.

    By default MongoDB doesn't offer authentication so you will have to configure this.

    We're offering backups included with OR Mongo so this will also need to be sorted out.

    MongoDB, at least on MMAP has issues reclaiming disk space so you will have to manage the fragmentation that is, on the OR Mongo side handled by the weekly compactions. WiredTiger is better at handling fragmentation but requires additional tuning and takes way more resources.

    Also, the replicaset will have to have the Firewall configured that was handled by our ACLs.

    You will have to be informed of issues with the instance. For instance, if one of your nodes goes down, you will lose some of the redundancy so you will need to sort the issue out as soon as possible and this can be a mongo issue, like an OOM not a host issue. If you will face this, our other support teams will not really be able to help a lot. Right now, using OR Mongo, our Operations team is handling any issue with the infrastructure and are pulling DBAs or Data Engineers to assist if it's a Mongo issue. In case for instance a node goes down, someone is paged and will sort things out so that you will have a fully functioning replicaset before any new issue arises.

    Last but not least you will see a difference in performance. We're running MongoDB on SSDs with FusionIO cards and the instances are optimized for performance. Once you move away from this, you might experience performance issues.

    As mentioned, Jim, we believe that MongoDB on ObjectRocket has a lot of advantages and these are making it possible for you to focus on your code and not on Mongo. I'm sure that if you are not happy with us our Technical Account Managers would like to hear from you to see what we can do to make it better.

    Of course, If your mind is made up, we will try and make the transition as smooth as possible so please submit a ticket to and we will be able to discuss this further.

    Of course, if you have any additional questions, we'll be glad to answer them.

    Thank you.

    Alex Cercel

    Customer Data Engineer III

    Datastores Support - Rackspace

    MongoDB Certified DBA, RHCE, RHCSA, VCA-DCV, ITIL V3 Certified

No Data