Created attachment 524783 [details] vdsm log attached Description of problem: The thread for getStoragePoolInfo contains about 19 lines each time it runs (which is every 10 seconds) out of these 10 lines about 10 are for ResourceManager. can you please diminish some of these lines from logger to clean the log a bit? it feels like since this runs every 10 seconds that some of these actions might not need to be in the log. Version-Release number of selected component (if applicable): vdsm-4.9-96.1.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. search for getStoragePoolInfo in the vdsm log 2. 3. Actual results: the query runs every 10 seconds and logs about 19 raws each time Expected results: can we please remove some of these raws from vdsm log since it seems like a lot of noise in the log for one query. Additional info:
Specifically, the issue is with the lines from the ResourceManager. They represent 10 lines of logs out of the total 19 of the command. Example: Thread-2000::DEBUG::2011-09-25 13:01:02,104::resourceManager::821::ResourceManager.Owner::(cancelAll) Owner.cancelAll requests {} Thread-2000::DEBUG::2011-09-25 13:01:02,104::resourceManager::517::ResourceManager::(releaseResource) Trying to release resource 'Storage.0b8809e9-1f75-40d7-9d32-8b66969ff552' Thread-2000::DEBUG::2011-09-25 13:01:02,104::resourceManager::532::ResourceManager::(releaseResource) Released resource 'Storage.0b8809e9-1f75-40d7-9d32-8b66969ff552' (0 active users) Thread-2000::DEBUG::2011-09-25 13:01:02,105::resourceManager::537::ResourceManager::(releaseResource) Resource 'Storage.0b8809e9-1f75-40d7-9d32-8b66969ff552' is free, finding out if anyone is waiting for it. Thread-2000::DEBUG::2011-09-25 13:01:02,105::resourceManager::544::ResourceManager::(releaseResource) No one is waiting for resource 'Storage.0b8809e9-1f75-40d7-9d32-8b66969ff552', Clearing records.
I'm very glad that you are confident in our bugless deadlockless resource subsystem. I'm a little less confident, and would like to keep the log lines, just in case a complex deadlock crops up in a customer site. Let's reconsider in 3.1, and use `grep -v ::ResourceManager::` until then.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.