4.6 Clustering changes

Description

1. Change the default HA mode not to be "minority" mode [Fixes the quorum problem]
2. Modify the Postgres configuration to use synchronous replication.

Need to handle
1. A patch on top of 4.6 [using patchify]
2. Document upgrade flow for 4.6 users, earlier version users, and from scratch 4.6 deployment

Activity

Show:
Barak Azulay
September 16, 2019, 10:11 AM

from the description above:

“2. Document upgrade flow for 4.6 users, earlier version users, and from scratch 4.6 deployment”

This should only b handled for 4.6 (either on clean install or running 4.6 that just got this patch through patchify)

earlier version users should upgrade to 4.6

Ofer Yarom
September 18, 2019, 5:58 AM

The point about earlier versions is that we are clear about the path. e.g. if I have 4.4, I should (for example, I am not sure if this is the true procedure)

  1. Move to 4.6 clean version by snapshot+restore path on 4.6

  2. Apply the latest 4.6 patches

  3. re-create the cluster

Barak Azulay
September 18, 2019, 9:42 AM

IIUC this is the exact procedure , Lukasz please respond in case this is not the cae.

Łukasz Maksymczuk
October 29, 2019, 11:26 AM

The patch was implemented in https://github.com/cloudify-cosmo/patchify/pull/128

However note that for applying the patch to an existing cluster, additional commands must be executed, the summary is in a comment under the PR.

Łukasz Maksymczuk
October 29, 2019, 11:28 AM

As part of this change, not only was the db made to use synchronous replication, but also several smaller changes were introduced, such as:

  • improving logging

  • after 3 minutes of failing the db health check, the manager will attempt to follow again

This is due to additional issues found in testing

Done

Assignee

Łukasz Maksymczuk

Reporter

Ofer Yarom

Labels

Target Version

4.6

QA Owner

Ahmad Musa
Łukasz Maksymczuk

Premium Only

yes

Documentation Required

Yes

Why Blocked?

None

Release Notes

yes

Priority

High

Epic Link

Priority

Critical
Configure