On 06/19/2015 11:16 AM, Daniel Schneller wrote: > On 2015-06-18 09:53:54 +0000, Joao Eduardo Luis said: > >> Setting 'mon debug = 0/5' should be okay. Unless you see that setting >> '/5' impacts your performance and/or memory consumption, you should >> leave that be. '0/5' means 'output only debug 0 or lower to the logs; >> keep the last 1000 debug level 5 or lower in memory in case of a crash'. >> Your logs will not be as heavily populated but, if for some reason the >> daemon crashes, you get quite a few of debug information to help track >> down the source of the problem. > > Great, will do. > > Just for my understanding re/ memory: If this is a ring > buffer for the last 10000 events, shouldn't that be a somewhat fixed amount > of memory? How would it negatively affect the MON's consumption? Assuming > it works that way, once they have been running for a few days or weeks, > these buffers would be full of events anyway, just more "aged" ones if > the memory level was lower? > > Daniel >From briefly taking a peak at 'src/log/*', this looks like it is a linked list rather than a buffer ring. So, given it will always be capped at 10k events, there's a fixed amount of memory it will consume in the worst case (when you have 10k events). But if you have bare minimum activity in the logs, said memory consumption should be lower, or at most slowly growing as the queue grows. Although I was not obvious, my initial thought was that someone with debug levels set at 0/0 would certainly be surprised if, after setting 0/5, the daemon's memory consumption started to grow. In retrospect, 10k log messages should not take more than a handful of MBs, and should not have any impact at all as long as you're not provisioning your monitor's memory in the dozens of MBs. -Joao _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |