{{announcement.body}}
{{announcement.title}}

Add a Node to Runtime Fabric (Linux 7.8 localhost)

DZone 's Guide to

Add a Node to Runtime Fabric (Linux 7.8 localhost)

In this article, see how to add a node to Runtime Fabric.

· Integration Zone ·
Free Resource

Add 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:

MuleSoft doc

Here is a sample server which is ready to add in a specific controller...

Fdisk details for the worker node as below: 

Java
 




x
45


 
1
[root@workerone runtimefabric]# fdisk -l 
2
  
3
Disk /dev/sda: 21.5 GB, 21474836480 bytes, 41943040 sectors 
4
Units = sectors of 1 * 512 = 512 bytes 
5
Sector size (logical/physical): 512 bytes / 512 bytes 
6
I/O size (minimum/optimal): 512 bytes / 512 bytes 
7
Disk label type: dos 
8
Disk identifier: 0x0002997d 
9
  
10
   Device Boot      Start         End      Blocks   Id  System 
11
/dev/sda1   *        2048     2099199     1048576   83  Linux 
12
/dev/sda2         2099200    41943039    19921920   8e  Linux LVM 
13
  
14
Disk /dev/mapper/rhel-root: 18.2 GB, 18249416704 bytes, 35643392 sectors 
15
Units = sectors of 1 * 512 = 512 bytes 
16
Sector size (logical/physical): 512 bytes / 512 bytes 
17
I/O size (minimum/optimal): 512 bytes / 512 bytes 
18
  
19
  
20
Disk /dev/mapper/rhel-swap: 2147 MB, 2147483648 bytes, 4194304 sectors 
21
Units = sectors of 1 * 512 = 512 bytes 
22
Sector size (logical/physical): 512 bytes / 512 bytes 
23
I/O size (minimum/optimal): 512 bytes / 512 bytes 
24
  
25
  
26
Disk /dev/sdb: 107.4 GB, 107374182400 bytes, 209715200 sectors 
27
Units = sectors of 1 * 512 = 512 bytes 
28
Sector size (logical/physical): 512 bytes / 512 bytes 
29
I/O size (minimum/optimal): 512 bytes / 512 bytes 
30
Disk label type: dos 
31
Disk identifier: 0x7d66bb91 
32
  
33
   Device Boot      Start         End      Blocks   Id  System 
34
/dev/sdb1            2048   209715199   104856576   83  Linux 
35
  
36
Disk /dev/sdc: 107.4 GB, 107374182400 bytes, 209715200 sectors 
37
Units = sectors of 1 * 512 = 512 bytes 
38
Sector size (logical/physical): 512 bytes / 512 bytes 
39
I/O size (minimum/optimal): 512 bytes / 512 bytes 
40
Disk label type: dos 
41
Disk identifier: 0x4ce3c5d6 
42
  
43
   Device Boot      Start         End      Blocks   Id  System 
44
/dev/sdc1            2048   209715199   104856576   83  Linux 
45
[root@workerone runtimefabric]#




  • As in my previous article mentioned about chrony service error.. like below snippet.
Plain Text
 




xxxxxxxxxx
1


 
1
chrony-3.4-1.el7.x86_64
2
Checking chrony sync status...Retrying in 30 seconds...
3
Retrying in 30 seconds...
4
Error: chrony sync check failed 3 times, giving up.



Better install it before installing node..follow the below steps:

Plain Text
 




xxxxxxxxxx
1


 
1
[root@workerone runtimefabric]# yum install chrony
2
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
3
Package chrony-3.4-1.el7.x86_64 already installed and latest version
4
Nothing to do
5
[root@workerone runtimefabric]# systemctl start chronyd
6
[root@workerone runtimefabric]# systemctl enable chronyd
7
Created symlink from /etc/systemd/system/multi-user.target.wants/chronyd.service to /usr/lib/systemd/system/chronyd.service.
8
 
          


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.

Topics:
bestpractice, containerization, docker, ingress controller, integration, mule, mulesoft, mulesoft anypoint, runtime fabric, tutorial

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}