[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: opinions on log rolling defaults for JBoss



I'd rather lose logs than have applications crash.

Also, being able to hook this to a remote syslog server would be a +1 from me.

Trevor


On Mon, Jan 6, 2014 at 2:26 PM, Ben Parees <bparees redhat com> wrote:
Exceeding disk quotas is an occasional issue for OpenShift applications.  At least one culprit in this is the size of historic log files.  Currently the JBoss cartridges do not trim historic log files by default.  I'd like to solicit opinions on changing this default.  On the pro side, it would help mitigate disk quota problems for heavy logging JBoss applications.  The con is that the default behavior would now result in loss of historical data that exceeds the configured file limit (which is TBD but probably around 100megs), though this could be modified by users.

This would have no effect on existing applications as the log rolling behavior is configured within the JBoss application repository and no migration would be included in this change.

(Note that there is a longer term plan[1] to improve logging in OpenShift in general, what I am proposing is a tactical fix for JBoss cartridges only, for now)

[1]https://github.com/openshift/openshift-pep/blob/master/openshift-pep-009-logging.md

Ben Parees | OpenShift

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaughan onyxpoint com

-- This account not approved for unencrypted proprietary information --

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]