You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@karaf.apache.org by jb...@apache.org on 2013/12/12 10:33:55 UTC
svn commit: r1550386 -
/karaf/trunk/manual/src/main/webapp/users-guide/failover.conf
Author: jbonofre
Date: Thu Dec 12 09:33:54 2013
New Revision: 1550386
URL: http://svn.apache.org/r1550386
Log:
[KARAF-2511] Fix failover section in the user guide
Modified:
karaf/trunk/manual/src/main/webapp/users-guide/failover.conf
Modified: karaf/trunk/manual/src/main/webapp/users-guide/failover.conf
URL: http://svn.apache.org/viewvc/karaf/trunk/manual/src/main/webapp/users-guide/failover.conf?rev=1550386&r1=1550385&r2=1550386&view=diff
==============================================================================
--- karaf/trunk/manual/src/main/webapp/users-guide/failover.conf (original)
+++ karaf/trunk/manual/src/main/webapp/users-guide/failover.conf Thu Dec 12 09:33:54 2013
@@ -203,7 +203,7 @@ The container-level locking is supported
The container-level locking uses the {{karaf.lock.level}} property:
{code}
-karaf.lock.level=80
+karaf.lock.level=50
{code}
The {{karaf.lock.level}} property tells the Karaf instance how far up the boot process to bring the OSGi container.
@@ -213,8 +213,8 @@ As reminder, the bundles start levels ar
|| Level || Behavior ||
| 1 | A 'cold' standby instance. Core bundles are not loaded into container. Slaves will wait until lock acquired to start server. |
-| <80 | A 'hot' standby instance. Core bundles are loaded into the container. Slaves will wait until lock acquired to start user level bundles. The console will be accessible for each slave instance at this level. |
-| >80 | This setting is not recommended as user bundles will end up being started. |
+| <50 | A 'hot' standby instance. Core bundles are loaded into the container. Slaves will wait until lock acquired to start user level bundles. The console will be accessible for each slave instance at this level. |
+| >50 | This setting is not recommended as user bundles will end up being started. |
{warning}
Using 'hot' standby means that the slave instances are running and bind some ports. So, if you use master and slave instances on the same machine, you have