.. _man3-PMIx_Group_join: PMIx_Group_join =============== .. include_body ``PMIx_Group_join``, ``PMIx_Group_join_nb`` |mdash| Respond to an invitation to join an asynchronously-constructed PMIx group. SYNOPSIS -------- .. code-block:: c #include pmix_status_t PMIx_Group_join(const char grp[], const pmix_proc_t *leader, pmix_group_opt_t opt, const pmix_info_t info[], size_t ninfo, pmix_info_t **results, size_t *nresult); pmix_status_t PMIx_Group_join_nb(const char grp[], const pmix_proc_t *leader, pmix_group_opt_t opt, const pmix_info_t info[], size_t ninfo, pmix_info_cbfunc_t cbfunc, void *cbdata); Python Syntax ^^^^^^^^^^^^^ .. code-block:: python3 from pmix import * foo = PMIxClient() # the leader is a Python ``pmix_proc_t`` dictionary leader = {'nspace': "testnspace", 'rank': 0} # opt is PMIX_GROUP_ACCEPT or PMIX_GROUP_DECLINE # the info is a list of Python ``pmix_info_t`` dictionaries pyinfo = [] rc, results = foo.group_join("mygroup", leader, PMIX_GROUP_ACCEPT, pyinfo) INPUT PARAMETERS ---------------- * ``grp``: A NULL-terminated character string identifying the group named in the invitation. The string must be of length less than or equal to ``PMIX_MAX_NSLEN``. * ``leader``: Pointer to a ``pmix_proc_t`` structure identifying the process that issued the invitation (the leader of the asynchronous construction procedure). * ``opt``: A ``pmix_group_opt_t`` value indicating the response |mdash| ``PMIX_GROUP_ACCEPT`` to join the group or ``PMIX_GROUP_DECLINE`` to reject the invitation. * ``info``: Pointer to an array of :ref:`pmix_info_t(5) ` structs conveying user directives that qualify the operation. * ``ninfo``: Number of elements in the ``info`` array. The blocking form returns results directly: * ``results``: Address of a pointer that, upon successful return, is set to an array of :ref:`pmix_info_t(5) ` structs containing any values returned by the operation. May be ``NULL`` if the caller does not want the returned values. The caller is responsible for releasing the array with ``PMIX_INFO_FREE``. * ``nresult``: Address of a ``size_t`` that is set to the number of elements in the returned ``results`` array. The non-blocking form takes two additional parameters in place of ``results`` and ``nresult``: * ``cbfunc``: Callback function of type :ref:`pmix_info_cbfunc_t ` to be executed once the group has been completely constructed or its construction has failed. * ``cbdata``: Opaque pointer that is passed, unmodified, to ``cbfunc``. DESCRIPTION ----------- Respond to an invitation to join a group that is being asynchronously constructed via :ref:`PMIx_Group_invite(3) `. The process must have registered for the ``PMIX_GROUP_INVITED`` event in order to have been notified of the invitation. Calling this function causes the group leader to be notified that the process has either accepted or declined the request (the ``opt`` argument) |mdash| via a ``PMIX_GROUP_INVITE_ACCEPTED`` or ``PMIX_GROUP_INVITE_DECLINED`` event, respectively. The blocking form returns once the group has been completely constructed or its construction has failed (as determined by the leader); likewise, the callback function of the non-blocking form is executed upon the same conditions. As with all non-blocking PMIx APIs, callers of ``PMIx_Group_join_nb`` **must** keep the ``grp``, ``leader``, and ``info`` arrays valid until ``cbfunc`` is invoked. The invite/join handshake is described in full in :ref:`Group Construction, Destruction, and Fault Tolerance `. .. caution:: Because the process is alerted to the invitation in a PMIx event handler, it **must not** use the blocking form of this call unless it first "thread shifts" out of the handler and into its own thread context. Likewise, while it is safe to call the non-blocking form from the event handler, the process must not block in the handler while waiting for the callback function to be invoked. Leadership ^^^^^^^^^^ Failure of the leader at any time causes a ``PMIX_GROUP_LEADER_FAILED`` event to be delivered to all participants so they can optionally declare a new leader. A new leader is identified by providing the ``PMIX_GROUP_LEADER`` attribute in the results array returned from the event handler; only one process is permitted to do so. The outcome of leader selection is communicated to all participants via a ``PMIX_GROUP_LEADER_SELECTED`` event. If no leader was selected, the status code in that event carries an error value so participants can take appropriate action. Any participant that returns ``PMIX_GROUP_CONSTRUCT_ABORT`` from the leader-failed event handler causes all participants to receive an event notifying them of that status. Similarly, the leader may elect to abort the procedure |mdash| either by returning ``PMIX_GROUP_CONSTRUCT_ABORT`` from the handler assigned to the ``PMIX_GROUP_INVITE_ACCEPTED`` or ``PMIX_GROUP_INVITE_DECLINED`` codes, or by generating an event for the abort code. Abort events are sent to all invited participants. RETURN VALUE ------------ For the blocking form, ``PMIX_SUCCESS`` indicates that the group was successfully constructed and any returned values are available in ``results``. For the non-blocking form, a return of ``PMIX_SUCCESS`` indicates only that the request was successfully accepted for processing; the final status is delivered to ``cbfunc``, and the callback is not invoked if any other value is returned. * ``PMIX_SUCCESS`` |mdash| the group was successfully constructed. * ``PMIX_GROUP_CONSTRUCT_ABORT`` |mdash| construction of the group was aborted. * ``PMIX_ERR_BAD_PARAM`` |mdash| a required argument was invalid (e.g., a ``NULL`` or over-length group identifier). * ``PMIX_ERR_NOT_SUPPORTED`` |mdash| the host environment does not support group operations. * ``PMIX_ERR_INIT`` |mdash| the PMIx library has not been initialized. Any other value indicates an appropriate error condition. .. seealso:: :ref:`PMIx_Group_construct(3) `, :ref:`PMIx_Group_invite(3) `, :ref:`PMIx_Group_leave(3) `, :ref:`PMIx_Group_destruct(3) `, :ref:`pmix_info_t(5) `, :ref:`pmix_status_t(5) `, :ref:`pmix_group_opt_t(5) `, :ref:`pmix_proc_t(5) `