The maximum number of the same-type servers within a single environment layer depends on a particular hosting provider settings (usually this limit stands for 16 nodes). You can check the exact value within the Quotas & Pricing > Account Limits information frame.
All newly added servers are created at different hardware nodes, providing advanced reliability and high-availability.
Each environment node group (layer) is provided with the dedicated name, which, if needed, can be manually adjusted. In case there are several instances inside, layer name will be complemented with the xN label (where N is the actual nodes number).
Having several same-type nodes within a layer enables their synchronous management. Thus, all comprised containers can be simultaneously configured
, inspected for logs and statistics, restarted or redeployed
through the corresponding icons.
In order to operate with a particular container separately, expand the layer’s string to see the full list of its nodes. Each of these containers is an isolated instance, which has a unique Node ID
and can be accessed/configured apart from others. Herewith, the layer master node can be easily located due to the dedicated icon.
To facilitate interaction with numerous servers of the same type, Jelastic also allows marking a particular node with the appropriate label, e.g. to define master and slave instances in a DB cluster.
Just double-click at the default Node ID: xxx
value (or hover over it to reveal a special pencil icon) and specify the desired alternative name.
More information on this labeling feature can be found in the Environment Aliases document.
While scaling different types of stacks, consider the following specifics:
Now, you know how easy it is to horizontally scale instances in Jelastic PaaS and aware of the operation specifics. Also, feel free to configure an automatic nodes scaling
to smoothly overcome high load spikes without overpaying for unused resources.