Scalable Services Sticky Load-Balancing Policy

Currently, you might encounter a problem if you run a scalable data service that uses the sticky load-balancing policy. The problem can occur if the service runs with stickiness established relative to a particular node, and later you start another instance of the same service on a different node. Starting another instance of the same service might cause the first instance to lose its stickiness.

The result that the sticky algorithm returns when the second instance starts determines whether the first instance loses its stickiness. The algorithm should not change the sticky affinity in this case, but sometimes the algorithm does change the sticky affinity.

Refer to Sun Cluster 3.0 Concepts for more information on the sticky load-balancing policy.