Add a Node to Runtime Fabric (Linux 7.8 localhost)
In this article, see how to add a node to Runtime Fabric.
Join the DZone community and get the full member experience.
Join For FreeAdd Node in the specific controller in MuleSoft Runtime Fabric
Here are subsequent steps to add worker (MuleSoft runtime) once the controller is ready to operate...
Prerequisites
- The controller should be up and available. In below screen, controller
- Prepare worker node with prerequisite recommended by MuleSoft
- Runtime fabric will create a standard worker on each node server. Furthermore, each node required a minimum of 15 GB Memory/ temp with a minimum of 20 GB. Will suggest assigning some extra space as based on operation some time it throws space validation error.
- A minimum of 250 GB dedicated disk.
Follow MuleSoft doc:
Here is a sample server which is ready to add in a specific controller...
Fdisk details for the worker node as below:
[root runtimefabric]# fdisk -l
Disk /dev/sda: 21.5 GB, 21474836480 bytes, 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0002997d
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 2099199 1048576 83 Linux
/dev/sda2 2099200 41943039 19921920 8e Linux LVM
Disk /dev/mapper/rhel-root: 18.2 GB, 18249416704 bytes, 35643392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/rhel-swap: 2147 MB, 2147483648 bytes, 4194304 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sdb: 107.4 GB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x7d66bb91
Device Boot Start End Blocks Id System
/dev/sdb1 2048 209715199 104856576 83 Linux
Disk /dev/sdc: 107.4 GB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x4ce3c5d6
Device Boot Start End Blocks Id System
/dev/sdc1 2048 209715199 104856576 83 Linux
[root runtimefabric]#
- As in my previous article mentioned about chrony service error.. like below snippet.
xxxxxxxxxx
chrony-3.4-1.el7.x86_64
Checking chrony sync status...Retrying in 30 seconds...
Retrying in 30 seconds...
Error: chrony sync check failed 3 times, giving up.
Better install it before installing node..follow the below steps:
xxxxxxxxxx
[root runtimefabric]# yum install chrony
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
Package chrony-3.4-1.el7.x86_64 already installed and latest version
Nothing to do
[root runtimefabric]# systemctl start chronyd
[root runtimefabric]# systemctl enable chronyd
Created symlink from /etc/systemd/system/multi-user.target.wants/chronyd.service to /usr/lib/systemd/system/chronyd.service.
Once the above steps are done:
- Execute output command prepared by generate-configs.sh for a specific node.
The above script was prepared by Runtime Fabric hence not required to add or modify any value into it...
Few logs as below while the script was executing to install and create a node.
Final few lines output of script...
Note: It takes few extra moments to complete script execution, do not interfere until the script stopped itself if any occurs.
Now the node is installed and added in the controller.
Now you can use node to deploy the application.
Opinions expressed by DZone contributors are their own.
Trending
-
Step Into Serverless Computing
-
Top Six React Development Tools
-
Adding Mermaid Diagrams to Markdown Documents
-
Decoding eBPF Observability: How eBPF Transforms Observability as We Know It
Comments