Attached are the valgrind outputs from two separate runs of lrmd with the
suggested variables set. Do they help narrow the issue down?
Thanks
Greg
On 02/05/2014 03:01, "Andrew Beekhof" wrote:
>
>On 30 Apr 2014, at 9:01 pm, Greg Murphy
>wrote:
>
>> Hi
>>
>> I¹m running a two-node Pacemaker
On 6 May 2014, at 6:05 pm, Greg Murphy wrote:
> Attached are the valgrind outputs from two separate runs of lrmd with the
> suggested variables set. Do they help narrow the issue down?
They do somewhat. I'll investigate. But much of the memory is still reachable:
==26203==indirectly lost
Oh, any any chance you could install the debug packages? It will make the
output even more useful :-)
On 6 May 2014, at 7:06 pm, Andrew Beekhof wrote:
>
> On 6 May 2014, at 6:05 pm, Greg Murphy wrote:
>
>> Attached are the valgrind outputs from two separate runs of lrmd with the
>> suggested
On Mon, May 5, 2014 at 7:32 PM, Andrew Beekhof wrote:
>
> On 3 May 2014, at 6:20 am, Radoslaw Garbacz <
> radoslaw.garb...@xtremedatainc.com> wrote:
>
> > Hi,
> >
> > I have a strange situation, which I would like to ask about, whether it
> is a bug, misconfiguration or an intended behavior.
>
>
Hi,
I have question about colocation constraints – are they symmetrical
(commutative) or not?
What I mean is the following.
If we have the colocation constraint like
Does it produces the same behavior as the constraint
Thank you,
Jacob Nikom
On 7 May 2014, at 10:03 am, Jacob Nikom wrote:
> Hi,
>
> I have question about colocation constraints – are they symmetrical
> (commutative) or not?
>
> What I mean is the following.
>
> If we have the colocation constraint like
>with-rsc="reource2" score="-INFINITY"/>
>
> Does it produ
On 6 May 2014, at 7:47 pm, Greg Murphy wrote:
> Here you go - I’ve only run lrmd for 30 minutes since installing the debug
> package, but hopefully that’s enough - if not, let me know and I’ll do a
> longer capture.
>
I'll keep looking, but almost everything so far seems to be from or related
Hi David,
Sorry for the long delay - I missed your reply. Yes, we're using 1.1.10
with upstart. We'll upgrade to 1.1.11 and see if the issue occurs again.
Iain
On 25 April 2014 19:13, David Vossel wrote:
>
>
>
>
> - Original Message -
> > From: "Iain Buchanan"
> > To: "Pacemaker"
As promised, this announcement brings the first release candidate for Pacemaker
1.1.12
https://github.com/ClusterLabs/pacemaker/releases/Pacemaker-1.1.12-rc1
This release primarily focuses on important but mostly invisible changes
under-the-hood:
- The CIB is now O(2) faster. Thats 100x fo
