• New Feature
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • DSO:L1,DSO:L2
  • alex
  • Reporter: jhartley
  • January 08, 2007
  • 0
  • Watchers: 0
  • July 27, 2012
  • February 02, 2007


Motivation: Provide access to cluster events and node data to enable integrations to custom cluster aware features and various projects with multi-node support. For example, some new Tomcat integrations may require this capability.

Requirements: * Make cluster events accessible to developer and/or operator: * Notify when a node joins or leaves the cluster. * Notify L1 to L2 connect timeout * Default handler is to exit * Time is configurable * Notify when L1 to L2 connection established * Notify when L1 to L2 connection closed * Notify when L1 to L2 connection error * User application must have access to a data structure or can request a data structure that represents the cluster members

Optional: * All default handlers can be overridden (depends somewhat on if the implementation has the notion of ‘handlers’). * Make node list and status available via JMX – both viable via management consoles and by developers from their applications. * Allow attaching meta-data (an arbitrary object) for each node. For example, support custom routing based on info like node name or node capacity.

Use Case: An e-commerce company wants to integrate a custom load balancer with Terracotta such that Terracotta will notify the load balancer when an application server leaves the cluster. The load balancer may then take the desired action such as re-booting the application server or paging the appropriate operations personnel.