libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

KEYCLOAK-3064 Configuration option 'lockRecheckTime' is no longer valid

Browse source
This commit is contained in:
mposolda 2016-06-01 17:56:17 +02:00
parent cee471b851
commit 77ec2d3e8d
1 changed files with 3 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
topics/clustering/serialized.adoc
View file

@ -4,18 +4,17 @@
{{book.project.name}} cluster nodes are allowed to boot concurrenty. {{book.project.name}} cluster nodes are allowed to boot concurrenty.
When {{book.project.name}} server instance boots up it may do some database migration, importing, or first time initializations. When {{book.project.name}} server instance boots up it may do some database migration, importing, or first time initializations.
A DB lock is used to prevent start actions from conflicting ith one another when cluster nodes boot up concurrently. A DB lock is used to prevent start actions from conflicting with one another when cluster nodes boot up concurrently.
By default, the maximum timeout for this lock is 900 seconds. If a node is waiting on this lock for more than the timeout By default, the maximum timeout for this lock is 900 seconds. If a node is waiting on this lock for more than the timeout
it will fail to boot. This lock is checked every 2 seconds by default. it will fail to boot.
Typically you won't need to increase/decrease the default value, but just in case it's possible to configure it in `keycloak-server.json`: Typically you won't need to increase/decrease the default value, but just in case it's possible to configure it in `keycloak-server.json`:
[source,json] [source,json]
---- ----
"dblock": { "dblock": {
"jpa": { "jpa": {
"lockWaitTimeout": 900, "lockWaitTimeout": 900
"lockRecheckTime": 2
} }
} }
---- ----