On Fri, Jul 29, 2016 at 4:09 PM, Ken Gaillot wrote:
> On 07/28/2016 01:48 PM, Nate Clark wrote:
>> On Mon, Jul 25, 2016 at 2:48 PM, Nate Clark wrote:
>>> On Mon, Jul 25, 2016 at 11:20 AM, Ken Gaillot wrote:
On 07/23/2016 10:14 PM,
On 07/28/2016 01:48 PM, Nate Clark wrote:
> On Mon, Jul 25, 2016 at 2:48 PM, Nate Clark wrote:
>> On Mon, Jul 25, 2016 at 11:20 AM, Ken Gaillot wrote:
>>> On 07/23/2016 10:14 PM, Nate Clark wrote:
On Sat, Jul 23, 2016 at 1:06 AM, Andrei Borzenkov
On Mon, Jul 25, 2016 at 2:48 PM, Nate Clark wrote:
> On Mon, Jul 25, 2016 at 11:20 AM, Ken Gaillot wrote:
>> On 07/23/2016 10:14 PM, Nate Clark wrote:
>>> On Sat, Jul 23, 2016 at 1:06 AM, Andrei Borzenkov
>>> wrote:
23.07.2016
On Mon, Jul 25, 2016 at 11:20 AM, Ken Gaillot wrote:
> On 07/23/2016 10:14 PM, Nate Clark wrote:
>> On Sat, Jul 23, 2016 at 1:06 AM, Andrei Borzenkov
>> wrote:
>>> 23.07.2016 01:37, Nate Clark пишет:
Hello,
I am running pacemaker 1.1.13
On Sat, Jul 23, 2016 at 1:06 AM, Andrei Borzenkov wrote:
> 23.07.2016 01:37, Nate Clark пишет:
>> Hello,
>>
>> I am running pacemaker 1.1.13 with corosync and think I may have
>> encountered a start up timing issue on a two node cluster. I didn't
>> notice anything in the
23.07.2016 01:37, Nate Clark пишет:
> Hello,
>
> I am running pacemaker 1.1.13 with corosync and think I may have
> encountered a start up timing issue on a two node cluster. I didn't
> notice anything in the changelog for 14 or 15 that looked similar to
> this or open bugs.
>
> The rough out