Difference between revisions of "Fail-over Configuration (Primary/Secondary)"
From RifidiWiki
(→Introduction) |
|||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
Starting in 3.1 Failover Configuration (Primary/Secondary) feature is available. | Starting in 3.1 Failover Configuration (Primary/Secondary) feature is available. | ||
| + | |||
| + | This enables a Rifidi Edge server to be defined as a secondary node based on configuration described below. The secondary server will start and load the basic libraries. In the event a failure is detected based on thresholds configured the server will continue to load the necessary Rifidi Apps and connecting to the required sensors/readers to continue processing events. | ||
| + | |||
| + | Note: Many RFID readers only allow for one connection hence the reason for a primary and secondary node configuration to ensure only one connection by a Rifidi server node configuration . | ||
=Configuration= | =Configuration= | ||
| − | + | rifidiserver.ini in windows and rifidi-server in linux/unix -- A full list of Rifidi Edge configuartion parameters can be found [[Edge_Server_Configuration]] | |
| + | |||
| − | + | Example Edge Sever Configuration required to support Failover | |
| + | <pre> | ||
| + | -Dorg.rifidi.failover.primary=192.168.0.12:8111 IP and Port of the Primary Edge Server | ||
| + | -Dorg.rifidi.failover.frequency=10 how often to call The Primary Server's rest ping command in seconds | ||
| + | -Dorg.rifidi.failover.failurecount=6 number of consecutive failures before secondary determines the primary has failed | ||
| − | + | Note: The Port number (8111 in this example which is also the default Restlet port) needs to match Restlet port # on primary server found in the [[Edge_Server_Configuration|Edge_Server_Configuration]] | |
| − | + | </pre> | |
| − | + | These settings will cause the server to act as a secondary node and try to connect to the primary, getting the "readers" command | |
| − | + | every 10 seconds. 6 failures in a row will mean the application launch | |
| + | will continue on. | ||
Latest revision as of 18:48, 14 February 2018
Introduction
Starting in 3.1 Failover Configuration (Primary/Secondary) feature is available.
This enables a Rifidi Edge server to be defined as a secondary node based on configuration described below. The secondary server will start and load the basic libraries. In the event a failure is detected based on thresholds configured the server will continue to load the necessary Rifidi Apps and connecting to the required sensors/readers to continue processing events.
Note: Many RFID readers only allow for one connection hence the reason for a primary and secondary node configuration to ensure only one connection by a Rifidi server node configuration .
Configuration
rifidiserver.ini in windows and rifidi-server in linux/unix -- A full list of Rifidi Edge configuartion parameters can be found Edge_Server_Configuration
Example Edge Sever Configuration required to support Failover
-Dorg.rifidi.failover.primary=192.168.0.12:8111 IP and Port of the Primary Edge Server -Dorg.rifidi.failover.frequency=10 how often to call The Primary Server's rest ping command in seconds -Dorg.rifidi.failover.failurecount=6 number of consecutive failures before secondary determines the primary has failed Note: The Port number (8111 in this example which is also the default Restlet port) needs to match Restlet port # on primary server found in the [[Edge_Server_Configuration|Edge_Server_Configuration]]
These settings will cause the server to act as a secondary node and try to connect to the primary, getting the "readers" command every 10 seconds. 6 failures in a row will mean the application launch will continue on.
