924060929 commented on PR #4061:
URL: https://github.com/apache/doris-website/pull/4061#issuecomment-5448160305
The guide already covers the quota hierarchy, admission/eviction behavior,
configuration, and entry-level observability well. Could we also add a
Catalog-level summary query? This is likely the first query operators will use:
```sql
SELECT
fe_host,
catalog_name,
MAX(catalog_max_weight) AS catalog_max_weight,
MAX(catalog_estimated_weight) AS catalog_estimated_weight,
MAX(global_max_weight) AS global_max_weight,
MAX(global_estimated_weight) AS global_estimated_weight
FROM information_schema.catalog_meta_cache_statistics
WHERE catalog_estimated_weight >= 0
GROUP BY fe_host, catalog_name
ORDER BY fe_host, catalog_name;
```
`CATALOG_MAX_WEIGHT` and `CATALOG_ESTIMATED_WEIGHT` are repeated on every
weighted-entry row of the same Catalog, so the example should explicitly use
`MAX`; using `SUM` would double-count them.
It would also help to clarify the time semantics: `ESTIMATED_WEIGHT`,
`CATALOG_ESTIMATED_WEIGHT`, and `GLOBAL_ESTIMATED_WEIGHT` are current
reservation gauges at query time, while eviction/rejection fields are
cumulative counters for the current cache instance. The system table itself
does not retain historical samples.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
