Langsung ke konten utama

The Main Difference Between Unicast and Multicast is as Follows

Unicast:
Say you have three servers (MS-1,MS-2,MS-3) in a cluster now if they have to communicate with each other they have to ping (i.e. heartbeats ) the cluster master for informing him that he is alive.

If MS-1 is the master then MS-2 and MS-3 would send the ping to MS-1

Multicast:
Here there is no cluster master each server has to ping each other to inform everyone that I am alive.

So MS-1 would send the ping to MS-2 & MS-3 same way MS-2 would send the ping to MS-1 & MS-3 and MS-3 would ping MS-1 & MS-3.

Thus if you see in multicast the congestion in sending the pings are more compared to unicast which makes multicast much heavier, thus WLS recommends using Unicast of less congestion in the network.

Komentar

Postingan populer dari blog ini

Mounting USB drives in Windows Subsystem for Linux

Windows Subsystem for Linux can use (mount): SD card USB drives CD drives (CDFS) Network drives UNC paths Local storage / drives Drives formatted as FAT, ExFAT or NTFS can be mounted in WSL. For this example, we assume the drive shows in Windows as F:\ If Windows changes the USB drive letter on a subsequent session, you need to repeat this process. The commands are typed into the Windows Subsystem for Linux Terminal. Create a mount location in WSL: $ sudo mkdir /mnt/f Mount the drive in WSL: $ sudo mount -t drvfs f: /mnt/f After this one-time setup, one can create and manipulate files from both Windows and WSL on the same drive. network storage Here we assume: networked storage is already showing in Windows under \\server\share we want to access this network storage from WSL as /mnt/share Create a mount location in WSL: $ sudo mkdir /mnt/share Mount the network share in WSL: $ sudo mount -t drvfs '\\server\share' /mnt/share

FMW 12.2.1.3.0: "ONS configuration failed" or "oracle.ons.NoServersAvailable: Subscription time out"

FMW 12.2.1.3.0: "ONS configuration failed" or "oracle.ons.NoServersAvailable: Subscription time out" Solving To implement the workaround in the Configuration Wizard(config.sh) set the following environment variable before launching config.sh. $ export CONFIG_JVM_ARGS=-Doracle.jdbc.fanEnabled=false

ERROR ORACLE DB: The version 12.2.0.1.0 of the database that you are using is not a supported version

ERROR ORACLE DB: The version 12.2.0.1.0 of the database that you are using is not a supported version or The specified user may not have sufficient privileges to perform this operation. User should have sysdba or dba privileges. Solution SQL> alter system set db_32k_cache_size = 512M scope=both;