Resolution:
Description:
===========

In TIBCO BusinessEvents, what configuration is required  to avoid the delay in redistribution of data when a new member joins or leaves a cluster?

Environment:
===========
TIBCO BusinessEvents 4.0.1
All Operating Systems

Symptoms:
=========

The Inference agent could hang when the CacheServer is restarted and joins the cluster. The time could vary depending on the load and the current Cache size.

Cause:
======

When a new Coherence node joins or leaves a cluster, the cluster redistributes the data to balance the load. While performing the redistribution, it will acquire a lock on the grid which causes the delay.


Resolution:
=========

1). Make sure the following properties are configured on all nodes of the cluster. These properties contains detailed identity information that is useful for defining the location and role of the cluster member.

java.property.tangosol.coherence.cluster
java.property.tangosol.coherence.site
java.property.tangosol.coherence.rack
java.property.tangosol.coherence.machine

Reference:
========
http://wiki.tangosol.com/display/COH32UG/member-identity

Configuration requiredto avoid the delay in redistribution of data when a new TIBCO BusinessEvents Cache member joins or leaves a cluster.