On 13 Jun 2014, at 7:51 pm, Johan Huysmans wrote:
> I tested with a custom build libqb rpm
> (libqb-0.17.0-1.15.f8b4.dirty.el6.x86_64) however that didn't solved the
> issue.
> So for now I will add the export of the PCMK_ipc_buffer to my bash_profile.
Did you rebuild pacemaker once you had t
I tested with a custom build libqb rpm
(libqb-0.17.0-1.15.f8b4.dirty.el6.x86_64) however that didn't solved the
issue.
So for now I will add the export of the PCMK_ipc_buffer to my bash_profile.
thx
Johan
On 13-06-14 11:23, Johan Huysmans wrote:
I exported the PCMK_ipc_buffer in my console be
I exported the PCMK_ipc_buffer in my console before running the crm_mon
and everything worked.
But I see this more as a workaround (could set this in my bash_profile).
I currently have libqb-0.16.0-2.el6.x86_64 installed,
which version should fix this ?
Thanks!
Johan H.
On 13-06-14 10:41, And
On 13 Jun 2014, at 5:35 pm, Johan Huysmans wrote:
> Hi,
>
> The PCMK_ipc_buffer was already set to 1000 (10M).
Try setting that in your environment too (otherwise the CLI tools wont know
about the new value).
Or grab a newer libqb which _should_ do the right thing anyway
>
> For testing
Hi,
I performed some extra testing.
I cleared my complete cib (cibadmin -E) and my crm_mon showed again some
information.
I gradually started adding resources and monitored the cib.xml size
(cibadmin -Ql > cib.xml; ll -h cib.xml).
This grew to about 430K. When adding another bunch of resourc
Hi,
The PCMK_ipc_buffer was already set to 1000 (10M).
For testing I increased to buffer to 1000 (100M), without results.
I decreased the buffer to the default 20480 (20K) as it then shows the
suggested value.
If I leave it running for a couple of minutes I got these suggested values:
On 12 Jun 2014, at 10:53 pm, Johan Huysmans wrote:
> Hi All,
>
> I deployed Pacemaker 1.1.12-rc2 on our platform to test the cib changes.
> This was needed on our setup as it contains 6 nodes, 150 resources and the
> cib process was using lots of cpu.
>
> With a limited set of resources (6 no
