diff options
| author |   Jiri Stransky <jistr@redhat.com> | 2016-01-26 18:23:00 +0100 |
|---|---|---|
| committer | Jiri Stransky <jistr@redhat.com> | 2016-01-26 18:25:08 +0100 |
| commit | e4fb068a7b3a27cd03459a6df8a2e2c26b08bb89 (patch) | |
| tree | 3a3a7d2f653ae56dcf5b42d6612c456737afa703 /extraconfig/tasks | |
| parent | 48c93ee87f8c874e68b4c688c8f267d514a2599a (diff) | |
Increase galera sync timeout in yum_update.sh
We've seen the 360 second threshold broken and a failed update because
of that, even though Galera eventually synced fine, clusterchecks OK and
pcs status clean. This will give Galera more time to perform the sync.
Change-Id: I17207ec9b4038fb9540582c9b0b717f9b85a78b9
Closes-Bug: #1538218
Diffstat (limited to 'extraconfig/tasks')
| -rwxr-xr-x | extraconfig/tasks/yum_update.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/extraconfig/tasks/yum_update.sh b/extraconfig/tasks/yum_update.sh index 39179024..364d7343 100755 --- a/extraconfig/tasks/yum_update.sh +++ b/extraconfig/tasks/yum_update.sh @@ -23,7 +23,7 @@ update_identifier=${update_identifier//[^a-zA-Z0-9-_]/} # seconds to wait for this node to rejoin the cluster after update cluster_start_timeout=600 -galera_sync_timeout=360 +galera_sync_timeout=1800 cluster_settle_timeout=1800 timestamp_file="$timestamp_dir/$update_identifier" |