5 Aug
2009
5 Aug
'09
12:17 p.m.
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.
p.