2016-04-30 04:39:32 +00:00
|
|
|
|
2016-04-28 22:25:54 +00:00
|
|
|
[[_clustering_db_lock]]
|
|
|
|
|
=== Serialized Cluster Startup
|
|
|
|
|
|
2017-08-28 12:50:14 +00:00
|
|
|
{project_name} cluster nodes are allowed to boot concurrenty.
|
|
|
|
|
When {project_name} server instance boots up it may do some database migration, importing, or first time initializations.
|
2016-06-01 15:56:17 +00:00
|
|
|
A DB lock is used to prevent start actions from conflicting with one another when cluster nodes boot up concurrently.
|
2016-04-28 22:25:54 +00:00
|
|
|
|
2016-04-29 20:12:12 +00:00
|
|
|
By default, the maximum timeout for this lock is 900 seconds. If a node is waiting on this lock for more than the timeout
|
2016-06-01 15:56:17 +00:00
|
|
|
it will fail to boot.
|
2016-08-31 17:53:47 +00:00
|
|
|
Typically you won't need to increase/decrease the default value, but just in case it's possible to configure it in
|
|
|
|
|
`standalone.xml`, `standalone-ha.xml`, or `domain.xml` file in your distribution. The location of this file
|
2017-08-28 12:50:14 +00:00
|
|
|
depends on your <<_operating-mode, operating mode>>.
|
2016-04-28 22:25:54 +00:00
|
|
|
|
2016-08-31 17:53:47 +00:00
|
|
|
[source,xml]
|
2016-04-28 22:25:54 +00:00
|
|
|
----
|
2016-08-31 17:53:47 +00:00
|
|
|
<spi name="dblock">
|
|
|
|
|
<provider name="jpa" enabled="true">
|
|
|
|
|
<properties>
|
|
|
|
|
<property name="lockWaitTimeout" value="900"/>
|
|
|
|
|
</properties>
|
|
|
|
|
</provider>
|
|
|
|
|
</spi>
|
2017-02-16 09:55:31 +00:00
|
|
|
----
|
