日志打印太多导致cpu 100%问题解决

alarm服务日志级别修改INFO为WARN后,cpu使用从100%降到不到10%
 
 

curl -k -v -H "Authorization:Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJwYXRoIjoiLzEwMDg2Iiwic3ViIjoiVVNFUiIsImxldmVsIjoxLCJhdXRoIjozLCJyZWZyZXNoIjoxNTg4MjQxNTczNjc0LCJpZCI6NDkxMzgzNzU1MjkyNjcyMDAsInR5cGUiOjIsImV4cCI6MTU4ODI0MTg3MywidGVuYW50Ijo0OTEzODM3NTc4MDkyNTQ0MH0.4syPPJXFtLvih9_aZKrrNu9ufe3SHxh9X0o8PymtjyU, eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJwYXRoIjoiLzEwMDg2Iiwic3ViIjoiVVNFUiIsImxldmVsIjoxLCJhdXRoIjozLCJyZWZyZXNoIjoxNTg4MjQxNTczNjc5LCJpZCI6NDkxMzgzNzU1MjkyNjcyMDAsInR5cGUiOjIsImV4cCI6MTU4ODI0MTg3MywidGVuYW50Ijo0OTEzODM3NTc4MDkyNTQ0MH0.0EeexW5i_g6gTaigsWXxoRA9o5-gl66VmxLKZ4K5zd4" http://192.168.2.30:31121/api/v1/alarm/changeLevel?rootLevel=WARN

今天 18:50
 
 

动态调整日志级别,在测试和正式环境可以默认为WARN,开发环境改成INFO或者DEBUG,调试完再改回去。

日志log一分钟打印120M,12个zip文件,cpu忙于打印日志,不响应请求

动态调整日志级别

猜你喜欢

转载自www.cnblogs.com/yaoyu1983/p/12810711.html