ctdb memory usage

[Stefan (metze) Metzmacher]

Hi Ronnie,

> Ok, i can make it a command line setting to control how big the log
> area should be.

Yes, please and please make the default something like 10000.

Thanks!

metze

> 
> The purpose of this ringbuffer for logging is to be able to extract
> useful log information from a system semi-immediately after an
> incident has triggered.
> (Since logging continously at level 10 to a log file may be unrealistic).
> 
> So it kind of allows you to log with a reasonable level to disk, but
> once an abnormal incident has triggered, you can extract basically a
> full level 10 log from memory.
> This is MUCH nicer than "increase the log level to 10 and see if it
> happens again" which is a suboptimal troubleshooting approach for
> critical production systems. :-)

Yes, that's nice:-)

> 
> It would be _VERY_ nice to have something similar for samba.
> 
> 
> regards
> ronnie
> 
> 
> On Fri, Jan 8, 2010 at 3:48 AM, Stefan (metze) Metzmacher
> <metze at samba.org> wrote:
>> Hi Ronnie,
>>
>> I noticed that versions > 1.0.108 use about 68MB ram,
>> where 1.0.108 only used ~ 1MB.
>>
>> This is because of the large log ring buffer.
>>
>> This really a pain as my virtual machines start to swap badly.
>>
>> I think we should make this MAX_LOG_ENTRIES configureable.
>> and change the default from 500000 to 10000 or so, which is
>> ~ 4MB on my systems.
>>
>> metze
>>
>>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20100108/24e9c700/attachment.pgp>