3.1.4.1.24 ApiAddResourceNode (Opnum 23)

  • Article

msdn link

(Protocol Version 2) The ApiAddResourceNode method instructs the server to add the designated node to the set of nodes that can host the designated resource, as specified in section 3.1.1.1.1. The non-volatile cluster state associated with this resource is updated.

The server MUST enforce that the resource will only be hosted on a node that is a member of the set. If none of the nodes in the set is active, then the resource SHOULD be hosted on a node that is not a member of the set, but the resource MUST remain in the ClusterResourceOffline state.

The server MUST fail this method using error ERROR_OBJECT_ALREADY_EXISTS if the set is not empty and the node is already a member of the set.

The server MUST accept an ApiAddResourceNode request for processing only if it is in the read/write state, as specified in section 3.1.1.

 error_status_t ApiAddResourceNode(
   [in] HRES_RPC hResource,
   [in] HNODE_RPC hNode
 );

hResource: An HRES_RPC context handle that was obtained in a previous ApiOpenResource or ApiCreateResource method call.

hNode: An HNODE_RPC context handle that was obtained in a previous ApiOpenNode method call.

Return Values: The method MUST return the following error codes for the specified conditions.

Return value/code

Description

0x00000000

ERROR_SUCCESS

Success.

0x00000006

ERROR_INVALID_HANDLE

Either the hResource parameter does not represent a valid HRES_RPC context handle or the hNode parameter does not represent a valid HNODE_RPC context handle.

0x0000138E

ERROR_RESOURCE_NOT_AVAILABLE

The resource represented by the hResource parameter no longer exists in the non-volatile cluster state.

0x00001392

ERROR_OBJECT_ALREADY_EXISTS

See the preceding text for details of when this error can occur.

0x000013D7

ERROR_CLUSTER_RESTYPE_NOT_SUPPORTED

The node represented by hNode is not capable of hosting any resource of this type.

For any other condition, the server MUST set Status to a value that is not one of the values listed in the preceding table. The client MUST treat all values that are not listed in the preceding table the same, except as specified in section 3.2.4.6.