Re: [infinispan-dev] Health check use cases

Hey Tristan! Comments inlined. Thanks Sebastian On Tue, Jul 26, 2016 at 9:50 AM, Tristan Tarrant <ttarrant(a)redhat.com&gt; wrote: Yes, I think it's a good idea. We could even use tools like Jolokia [1] to expose MBeans through REST interface (it can be added to standalone.conf to the bootstrap classpath). Alternatively we could use JDK embedded HTTP Server [2]. The only restriction that comes into my mind is that we shouldn't allow duplicated domains when exposing MBeans through REST interface. Otherwise it will be very hard to construct proper paths for the endpoint. [1] https://jolokia.org/ [2] https://docs.oracle.com/javase/8/docs/jre/api/net/httpserver/spec/com/sun... Could you please elaborate more on that? How do we expose this information? Are you referring to Infinispan Stats [3]? I also though about supporting queries somehow. An imaginary example from the top of my head could look like the following: http://$ISPN/_health?cluster.nodes=3&MyCacheManager.MyCache.status=DEGRADED //<-- This would return 200 OK if we have 3 nodes and given cache is in degraded mode. http://$ISPN/_health?cluster.nodes=3&MyCacheManager.rebalance=IN_PROGRESS //<-- Checks if we have 3 nodes and rebalance is in proress [3] https://github.com/infinispan/infinispan/tree/8.2.x/core/src/main/java/or... I think we will need at least a 3rd state - yellow or something like this. This would mean that a rebalance is in progress of a node is joining/leaving. In other words - the cluster accepts requests but don't touch the nodes!