Jelastic Main Process Resource Consumption

Hi there,

With Jelastic now being available as a One-Click app I’m curious as to what would actually be needed to run a few small sites using it. The documentation is pretty unclear as to what is needed. The following questions present themselves to me from reading the documentation so far:

  1. It seems you don’t need to add a second “worker” node to begin deploying applications, if that’s the case how much of the main nodes resources are consumed by Jelastic itself?

  2. Can applications running from Jelastic access other DO resources like Managed Databases?

  3. Do worker nodes have to be the same size as the primary node? I.e. primary Jelastic node is 16 GB of RAM, do all other worker nodes need to be 16 GB as well or could I spin up a few smaller nodes to run alongside it?

Any help in understanding this would be appreciated.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

The current package of MongoDB in the marketplace is a standard replica set with 2 member nodes only. This package is going to be replaced soon by the new version which is in the testing phase now. The improved implementation provides 3 replica set members by default and automatically connects new nodes during horizontal scaling. In general, auto-clustering offers a standard setup of a cluster. If you need anything custom feel free to fork and customize the package, or alternatively you can [request related professional services] ( from our team. Please try the new package out and let us know your feedback.


Thank you for your interest in Jelastic.

You will find answers to your questions below:

  1. During the testing period, it’s ok to host applications on a single orchestrator node. When moving to production, we recommend adding user (worker) nodes.
    Jelastic orchestrator + OS uses about:
  • 4-4,5 GB RAM which will increase with the load
  • 36 GB HDD after the installation and will increase depending on your usage
  • CPU usage depends on the load
  1. The applications running inside Jelastic on DO can have access to other DO resources. You need to configure this access in the security settings of the Managed Database [(screenshot)] (

  2. The size of other worker nodes doesn’t depend on the size of the orchestrator node. You can attach one or several nodes/droplets of different sizes (4/8/16/32+ GB) to your cluster. The instructions on how to add additional node/droplet can be found at the link

It should be mentioned that all Jelastic environment configuration tutorials, deployment guides and application settings instructions that can be found at are also applied to Jelastic installation on DigitalOcean.

We could assist more if you describe your use case in more detail. What’s your application topology? What are the software stacks used inside your applications?

Please feel free to post any additional questions you might have.