[Pacemaker] pengine self-maintenance
Dejan Muhamedagic
dejanmm at fastmail.fm
Wed May 19 17:26:07 UTC 2010
Hi,
On Wed, May 19, 2010 at 09:13:28AM -0400, Vadym Chepkov wrote:
>
> On May 17, 2010, at 11:38 AM, Dejan Muhamedagic wrote:
> >
> > You don't want to set it that low. PE input files are part of
> > your cluster history. Set it to a few thousand.
> >
>
> What could be the side-backs of having it too low?
> How are these files being used?
They could be used by you as audit records, if you want to review
what has happened in the cluster sometimes in the past. The
filesystem should be able to handle a few thousand files and they
are quite small.
> And shouldn't be some reasonable default be in place? I just
> happened to notice 90% inode utilization on my /var, some could
> be not so lucky.
Yes, that could be a problem. Perhaps that default could be
changed to say 10000 which would be close enough to unlimited for
clusters in normal use :)
Thanks,
Dejan
> >> # ls /var/lib/pengine/|wc -l
> >> 123500
> >>
> >>>
> >>>> /var/lib/heartbeat/crm/ seems also growing unattended.
> >>>
> >>> Unless there is a bug somewhere, it should be storing only the last
> >>> 100 configurations.
> >>
> >> you are right, they are being "reused"
>
>
> I found another bug/feature :)
> When it's time to reutilize cib-/pe-xxx the process starts with 1, but initial start creates files with 0 suffix
> So you have your pe-warn-0.bz2 frozen in time, for example :)
>
>
>
> >>
> >>>
> >>>> Does pacemaker do any self-maintenance or it will cause system to crash
> >>>> eventually by utilizing all inodes?
> >>>>
> >>>> Also, why "cluster-recheck-interval" not in "pengine metadata" output? Is it
> >>>> deprecated?
> >>>
> >>> Its controlled by the crmd, so its in the "crmd metadata" output.
> >>
> >> Ah, then crm cli has a bug?
> >>
> >> When you click <TAB> metadata of crmd is not shown:
> >>
> >> crm(live)configure# property
> >> batch-limit= no-quorum-policy= pe-input-series-max= stonith-enabled=
> >> cluster-delay= node-health-green= pe-warn-series-max= stonith-timeout=
> >> default-action-timeout= node-health-red= remove-after-stop= stop-all-resources=
> >> default-resource-stickiness= node-health-strategy= start-failure-is-fatal= stop-orphan-actions=
> >> is-managed-default= node-health-yellow= startup-fencing= stop-orphan-resources=
> >> maintenance-mode= pe-error-series-max= stonith-action= symmetric-cluster=
> >
> > Yes, you can file a bugzilla for that. Note that the property
> > will still be set if you type it.
> >
>
> Done, Bug 2419
>
> Thanks,
> Vadym
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
More information about the Pacemaker
mailing list