jerryshao commented on PR #7604: URL: https://github.com/apache/gravitino/pull/7604#issuecomment-3067594168
> > Do we have a better consensus on this, this kind of log is useful at some scenarios, but also quite verbose. If we can have a better solution to balance the both sides, that would be great. @FANNG1 @yuqi1129 @mchades > > There is my proposal for the balance: We can modify the default configuration of Gravitino `log4j2.properties` to log the reset package's logs into a separate log file (such as `gravitino-rest.log`), which can avoid frequent log printing in `gravitino-server.log` during high concurrency requests, and also save the request logs into a separate log file for future problem investigation and tracing. > > WDYT? @jerryshao @FANNG1 @danhuawang Using another log seems overlapping with audit log. In Spark, we have a special logger configuration to disable verbose log for such class by default, then users can enable that manually (https://github.com/apache/spark/blob/a76be7686d264f33a8a2d0a24e291f7952e689b6/conf/log4j2.properties.template#L39). How about using that solution? -- 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]
