Re: [Gluster-devel] How long should metrics collection on a cluster take?

On Thu, Jul 26, 2018 at 8:30 PM, John Strunk wrote: > It is configurable. Use the default as a notion of scale... 5s may become > 30s; It won't be 5m. > Also remember, this is the maximum, not minimum. A change to a watched > kube resource will cause an immediate reconcile. The periodic,

Re: [Gluster-devel] How long should metrics collection on a cluster take?

It is configurable. Use the default as a notion of scale... 5s may become 30s; It won't be 5m. Also remember, this is the maximum, not minimum. A change to a watched kube resource will cause an immediate reconcile. The periodic, timer-based loop is just a fallback to catch state changes not

[Gluster-devel] Coverity covscan for 2018-07-26-2836e158 (master branch)

GlusterFS Coverity covscan results for the master branch are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-07-26-2836e158/ Coverity covscan results for other active branches are also available at

Re: [Gluster-devel] Maintainer's Meeting on 23rd July, 2018: Meeting minutes

BJ Link - Bridge: https://bluejeans.com/217609845 - Download: https://bluejeans.com/s/qGMqd Attendance - Amar, Kaleb, Nigel, Ravi, Vijay, Shyam, Rafi, Nithya, Kaushal, Pranith