31.05.2018 01:30, Casey & Gina пишет:
>> In this case, the agent is returning "master (failed)", which does not
>> mean that it previously failed when it was master -- it means it is
>> currently running as master, in a failed condition.
>
> Well, it surely is NOT running. So the likely problem
> In this case, the agent is returning "master (failed)", which does not
> mean that it previously failed when it was master -- it means it is
> currently running as master, in a failed condition.
Well, it surely is NOT running. So the likely problem is the way it's doing
this check? I see a
On Wed, 2018-05-30 at 09:31 +0200, Salvatore D'angelo wrote:
> Hi,
>
> Last question. In order to migrate pacemaker with minimum downtime
> the option I see are Rolling (node by node) and Disconnect Reattach
> http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Pacemak
>
Hi,
Last question. In order to migrate pacemaker with minimum downtime the option I
see are Rolling (node by node) and Disconnect Reattach
http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ap-upgrade.html
Hi,
That's related to a thing I'm fighting for.
An option to skip X lost monitoring attempts is planned, but not
implemented yet, as far as I know.
Regards,
Klecho
On 30/05/18 06:08, 范国腾 wrote:
Hi,
The cluster uses the PAF to manage the postgres db, and it use the GFS2 to
manage the
