A Project Runs in the Wrong Cluster

Problem: One or more projects are running on nodes that you thought belonged to another SAP Sybase Event Stream Processor cluster.

Clusters merge when members of two or more clusters on the same network:

Have overlapping lists of manager nodes in their <node-name>.xml files, and
Use the same values for the Name and Password elements (most often the default values) in the Cache section of their <node-name>.xml files. (A cluster is defined by its cache.)

In this Cache section, Name is set to the default value:

<Cache>
  <Host>dino</Host>
  <Port>19001</Port>
  <Name>test-name-1</Name>
  <Password>test-password-1</Password>
  <Managers enabled="true">
    <Manager>dino:19001</Manager>
    <Manager>astro:19002</Manager>
    <Manager>scooby:19003</Manager>
  </Managers>
</Cache>

Solution: Configure a unique name for each cluster. To separate two clusters, give all the nodes in cluster A the same value in the Cache | Name element of their <node-name>.xml files—cluster_A, for example. All the nodes in cluster B must likewise share a Cache | Name value—cluster_B, for example. It can be anything but cluster_A. It is best to also assign a unique Cache | Password value to each cluster, and to ensure that the lists of manager nodes in the Managers section do no overlap across clusters. (The Managers section should include the same manager nodes in every member of a given cluster.)