Moving core group members

When moving members to a different core group, remember that: each process can only be a member of one core group, and that all members of a given cluster must belong to the same core group.

Before you begin

  • Review the topic, Core groups (high availability domains).
  • Determine which core group members you want to move, and to which core group you want to move them
  • If you move one cluster member, all of the other members of the cluster are automatically relocated to the new core group.

About this task

You might need to move one or more core group members:
  • To populate a newly created core group.
  • To rebalance existing core groups.

The steps you perform to move either an application server, a deployment manager, or a node agent are slightly different. Depending on whether you are moving an application server, a deployment manager, or a node agent, complete one of the following steps.

Avoid trouble Avoid trouble: In general, you should not move a deployment manager.gotcha

Procedure

Results

After all of the restarts complete, all moved application servers, node agents, and deployment managers should belong to their new core group.

What to do next

  • You can verify that the servers are in the correct core groups. For each core group, in the administrative console, click Servers > Core Groups > core_group_name > Core group servers, and look at the list of core group members that displays.
  • You can set up core group bridges if any of the core groups need to communicate with each other. See the Core group communications using the core group bridge service topic for more information.

Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:28
File name: trun_ha_addcgmems.html