lsyulong commented on issue #7373: URL: https://github.com/apache/gravitino/issues/7373#issuecomment-3072321315
> > > > > These logs are not useless, but rather indicate that an external client is frequently loading the catalog. If you are not conducting performance testing, you should investigate the source of these requests and verify whether such high-frequency requests are expected. > > > > > > > > > > > > If deploying Trino for data preview, Trino will call load catalog api per 10 seconds , and this will cause massive "Catalog loaded" log message especially catalogs number is increasing in production environment. > > > > > > > > > In practice, the number of catalogs is not very large, and Trino loads them every 10 seconds, which is not very frequent. I think this is acceptable. > > > Perhaps we can divide the log files by log level: `gravitino-server.log.INFO`, `gravitino-server.log.WARNING` and `gravitino-server.log.ERROR`, WDYT? > > > > > > Then should we make this modification first? > > No, you should follow the solution mentioned [there](https://github.com/apache/gravitino/pull/7604#issuecomment-3067594168) [@lsyulong](https://github.com/lsyulong) OKļ¼tks -- 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]
