--On August 5, 2009 7:17:43 PM +0000 masarati@aero.polimi.it wrote:
This may be specific to glued databases (databases rooted at "").
The problem could be partially addressed by telling back-bdb (who's maintaining this data in the monitor backend) to check subordinates as soon as it discovers it's a glue instance. However, this poses two different problems:
- is the aggregate information resulting from adding all glued databases
cache usage still useful?
- what happens if heterogeneous databases are glued? Significantly, what
if the superior database is not bdb/hdb?
Probably, the monitor database should also present subordinate databases as separate entries.
Interestingly, in my case, there's only one real database in play for the glue as it is, since it's rooted at "". All other database definitions come before it (cn=config, cn=accesslog, cn=monitor).
I'm also curious why back-monitor develops stats for the other caches but specifically not for entry cache.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration