Hi Val, As for the REST API, I don't have a particular favouritism towards it. I started to look at it because the Ignite Web Console agent uses it to collect statistics. It looks to me that the Ignite Web Console monitoring places too much overhead to the application, the CPU and memory wise according to JVisualVM statistics.
Thanks for the suggestion. Yes, it is a good idea to create a client node for the management. Wonder if there is any available tool like this? I think this is a common use case, similar to what the Ignite Web Console monitoring does over the REST API. Thanks, Yuci -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cannot-get-cache-through-the-REST-API-tp6806p6965.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
