Hello, and since it is a month since the preceding attempt to gather
some feedback, welcome to yet another simple set of questions that
I will be glad to have answered by as many of you as possible,
as an auxiliary indicator what's generally acceptable and what's not
within the userbase.
This
On Thu, 2018-06-28 at 09:09 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 27.06.2018 um
> > > > 16:18 in Nachricht
>
> <1530109097.6452.1.ca...@redhat.com>:
> > On Wed, 2018-06-27 at 07:41 +0200, Ulrich Windl wrote:
> > > > > > Ken Gaillot schrieb am 26.06.2018 um
> > > > > > 18:22
On Thu, 2018-06-28 at 09:13 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 27.06.2018 um
> > > > 16:32 in Nachricht
>
> <1530109926.6452.3.ca...@redhat.com>:
> > On Wed, 2018-06-27 at 09:18 -0500, Ken Gaillot wrote:
> > > On Wed, 2018-06-27 at 07:41 +0200, Ulrich Windl wrote:
> > > >
On Thu, 2018-06-28 at 19:58 +0300, Andrei Borzenkov wrote:
> 28.06.2018 18:35, Dileep V Nair пишет:
> >
> >
> > Hi,
> >
> > I have a cluster with DB2 running in HADR mode. I have used the
> > db2
> > resource agent. My problem is whenever DB2 fails on primary it is
> > migrating
> > to the
On Thu, 2018-06-28 at 17:17 +0200, Salvatore D'angelo wrote:
> Hi All,
>
> I am here again. I am still fighting against upgrade problems but now
> I am trying to change the approach.
> I want now to try to install fresh a new version Corosync and
> Postgres to have it working.
> For the moment I
28.06.2018 18:35, Dileep V Nair пишет:
>
>
> Hi,
>
> I have a cluster with DB2 running in HADR mode. I have used the db2
> resource agent. My problem is whenever DB2 fails on primary it is migrating
> to the secondary node. Ideally it should restart thrice (Migration
> Threshold set to 3)
Hi,
I have a cluster with DB2 running in HADR mode. I have used the db2
resource agent. My problem is whenever DB2 fails on primary it is migrating
to the secondary node. Ideally it should restart thrice (Migration
Threshold set to 3) but not happening. This is causing extra downtime
Hi All,
I am here again. I am still fighting against upgrade problems but now I am
trying to change the approach.
I want now to try to install fresh a new version Corosync and Postgres to have
it working.
For the moment I am not interested to a specific configuration, just three
nodes where I
>>> Ken Gaillot schrieb am 27.06.2018 um 16:32 in
>>> Nachricht
<1530109926.6452.3.ca...@redhat.com>:
> On Wed, 2018-06-27 at 09:18 -0500, Ken Gaillot wrote:
>> On Wed, 2018-06-27 at 07:41 +0200, Ulrich Windl wrote:
>> > > > > Ken Gaillot schrieb am 26.06.2018 um
>> > > > > 18:22 in Nachricht
>>> Ken Gaillot schrieb am 27.06.2018 um 16:18 in
>>> Nachricht
<1530109097.6452.1.ca...@redhat.com>:
> On Wed, 2018-06-27 at 07:41 +0200, Ulrich Windl wrote:
>> > > > Ken Gaillot schrieb am 26.06.2018 um
>> > > > 18:22 in Nachricht
>>
>> <1530030128.5202.5.ca...@redhat.com>:
>> > On Tue,
10 matches
Mail list logo
