keith-turner commented on code in PR #33: URL: https://github.com/apache/accumulo-classloaders/pull/33#discussion_r2696082330
########## modules/local-caching-classloader/README.md: ########## @@ -170,20 +177,28 @@ constructed at that time. ## Cleanup + Because the cache directory is shared among multiple processes, and one process can't know what the other processes are doing, this class cannot clean up the shared cache directory of unused resources. It is left to the user to remove unused files from the cache. While the context definition JSON files are always safe to delete, it is not recommended to do so for any that are still in use, because they can be useful for troubleshooting. +To aid in this task a JMX MXBean has been created to expose the files that are still referenced Review Comment: > We might be able to create a tool that works in one deployment scenario, but it might be hard to make it work in many of them Do you know if different JMX connections could require different java code? Or can the java JMX client APIs connect to any endpoint given correct config? If the user may have to write different java code for different JMX scenarios then the best we could probably do in the project is provide a good example of the java cleanup code. -- 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]
