Difference between revisions of "Fail-over Configuration (Primary/Secondary)"
From RifidiWiki
(→Configuration) |
(→Configuration) |
||
Line 15: | Line 15: | ||
*-Dorg.rifidi.failover.failurecount=6- number of consecutive failures | *-Dorg.rifidi.failover.failurecount=6- number of consecutive failures | ||
</pre> | </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 | every 10 seconds. 6 failures in a row will mean the application launch | ||
will continue on. | will continue on. |
Revision as of 08:37, 15 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 - Full ListEdge_Server_Configuration
*-Dorg.rifidi.failover.primary=192.168.0.12:8111 as example -if set then means its secondary if null of not set then primary node Note: port number needs to match Restlet port # on server (-Dorg.rifidi.restlet.port=8111) *-Dorg.rifidi.failover.frequency=10 - how often to call rest ping command in seconds *-Dorg.rifidi.failover.failurecount=6- number of consecutive failures
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.