Thanks Udo.. that helps ! We did not have disk monitoring enabled and someone had accidentally changed logging to fine. This caused the data volume to fill up and caused all sorts of issues.
We have enabled disk monitoring and configured log/stats disk utilization properties. ~ Nikhil On Sun, Aug 14, 2016 at 11:15 PM, Udo Kohlmeyer <ukohlme...@pivotal.io> wrote: > Hi Nikhil, > > I don't think that there are specific best practices around log and stats > files. > > I've always tried to follow the following: > > - Avoid log files that are too large, as they become cumbersome to > monitor and transfer when too large. > - Limit to the amount of space you have available. i.e Determine how > much space you want your logs and stats files to take up and then set > accordingly. > > Many customers will set the file-size-limit to be between 512Mb and 1Gb > with the total disk-space-limit to be anywhere from 10Gb to unlimited > space. Generally most monitoring tools will monitor diskspace, so > monitoring a directory on available space is crucial. > > --Udo > > On 15/08/2016 12:59 AM, Nikhil Chandrappa wrote: > > Hi, > > Are there any recommendations/best practices around disk utilization for > logs and stats file in Gemfire? > > We are specifically looking recommendations for following properties of > Gemfire, > > --log-file-size-limit > --log-disk-space-limit > --archive-disk-space-limit > --archive-file-size-limit > > Thanks, > Nikhil > > > > > > > -- > > *Nikhil Chandrappa *| Data Engineer | New York > > (315) 396 - 3789 | nchandra...@pivotal.io | Pivotal Software Inc. > <http://www.pivotal.io/> > > > -- *Nikhil Chandrappa *| Data Engineer | New York (315) 396 - 3789 | nchandra...@pivotal.io | Pivotal Software Inc. <http://www.pivotal.io/>
