184.108.40.206.50 ApiOnlineGroup (Opnum 49)
(Protocol Version 2) The ApiOnlineGroup method instructs the server to make all the resources in the designated group active or available on the node that is hosting the group. The persistent state of the group is set to online and is updated in the nonvolatile cluster state.
The server MUST attempt to make all resources in the group active or available as specified in section 220.127.116.11.18.
The server MUST fail this method using the error ERROR_NODE_CANT_HOST_RESOURCE if the node is already hosting a group with one or more resources in the ClusterResourceOnline state, and the group has the same anti-affinity setting as the designated group. For information about anti-affinity, see section 18.104.22.168.4.
The server MUST fail this method using the error ERROR_SHARING_PAUSED if the node hosting the group is in the paused state.
The server MUST accept an ApiOnlineGroup request for processing only if it is in the read/write state, as specified in section 3.1.1.
error_status_t ApiOnlineGroup( [in] HGROUP_RPC hGroup );
Return Values: The method MUST return the following error codes for the specified conditions.
Return value/code Description
The hGroup parameter does not represent a valid HGROUP_RPC context handle.
The node hosting the group is in the paused state.
The server is in the process of making the group's resources active or available.
Cannot perform this operation on this built-in special group (section 22.214.171.124.4).
The group represented by the hGroup parameter no longer exists in the nonvolatile cluster state.
The group is already in the ClusterGroupPending state, or the group is in the process of being deleted but is still in the cluster state.
The node is already hosting a group with one or more resources in the ClusterResourceOnline state and the group has the same anti-affinity setting as the designated group.
For any other condition, this method MUST return a value that is not one of the values listed in the preceding table. The client MUST behave in one consistent, identical manner for all values that are not listed in the preceding table. The client SHOULD treat errors specified in section 126.96.36.199 as recoverable errors and initiate the reconnect procedure as specified in section 188.8.131.52.