Difference between revisions of "Fail-over Configuration (Primary/Secondary)"
From RifidiWiki
(→Introduction) |
(→Introduction) |
||
| 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 even a failure is detected based on thresholds configured the server will continue loading starting the necessary Rifidi Apps and connecting to the required sensors/readers to continue processing events. | ||
=Configuration= | =Configuration= | ||
Revision as of 18:21, 1 October 2014
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 even a failure is detected based on thresholds configured the server will continue loading starting the necessary Rifidi Apps and connecting to the required sensors/readers to continue processing events.
Configuration
In rifidiserver.ini - In rifidiserver.ini - A full list of Rifidi Edge configuartion parameters can be found Edge_Server_Configuration
JVM settings
- -Dorg.rifidi.failover.primary=192.168.x.x. as example -if set then means its secondary if null of not set then primary
node
- -Dorg.rifidi.failover.frequency=1 - how often to call rest ping command in seconds
- -Dorg.rifidi.failover.failurecount = 5 - number of consecutive failures
