Jelastic Main Process Resource Consumption

Posted March 25, 2020 633 views
DigitalOcean 1-Click Apps Marketplace

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.

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.

Submit an Answer
2 answers


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:
  2. 4-4,5 GB RAM which will increase with the load
  3. 36 GB HDD after the installation and will increase depending on your usage
  4. CPU usage depends on the load

  5. 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)

  6. 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.

  • @JelasticSupport thanks for jumping in here! Really appreciate you sharing this advice in the community.

    In the Marketplace, we just added a new feature in the Vendor Portal so Marketplace Vendors can customize what links show up on the side of their App Listing page.

    For example, here’s an app where the Marketplace Vendor has updated the default links with their own links:

    Thought this might help you showcase your app and the resources associated with it.

    Stay healthy!

    John (Product Manager for Marketplace)

  • Thanks for the answers!

    I had read through most of the documentation, I just didn’t find it overly clear on these specific points.

    Personally my stack is fairly simple, I’m only just starting to develop some stuff on my own for my personal company and I’m mainly using Rails and Node. Its all fairly small, and while I’d love to just use Kubernetes, I don’t know if it’s worth the devops time at the moment.

    From reading things over I think I might actually fit in as someone who could run a production setup on an 8GB server and then spin up a couple smaller nodes to run my actual applications along side it. That leaves me with a higher bill than I would like, but at this point I think I need to test deploying to Kubernetes to get an idea of how much time it would be for me to compare time to cost.

    Also, I see Jelastic offers the spin up of MongoDB, is this a normal replica set or some sort of custom replication?

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.