ctubbsii commented on issue #3334: URL: https://github.com/apache/accumulo/issues/3334#issuecomment-1809203254
> So, probably the best thing that can be done for this ticket is not to modify the monitor, but rather focus on the number of messages being sent by the tservers. Even if there is a loop that is spamming messages (on the order of 1 per millisecond in that case), we should not be trying to send every single message to the monitor. There needs to be some dedupping of messages done on the tserver side if possible and perhaps the queue size of messages being sent to the logger needs to be restricted in size. I don't know if we can do this given we are using the standard logging infrastructure such as log4j but it should be investigated. This kind of thing can definitely done... I've already linked to the log4j docs on filters above that are capable of customizing the logging in the way you're interested in doing. If an existing filter isn't suitable, the APIs are very simple, and it should be easy to create a custom filter that keeps logs from flooding your systems based on your specific requirements. -- 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]
