<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="mysql-cluster-ndbinfo-processes">
      </a>
      25.6.17.51 The ndbinfo processes Table
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045088252656">
  </a>
  <p>
   This table contains information about NDB Cluster node
        processes; each node is represented by the row in the table.
        Only nodes that are connected to the cluster are shown in this
        table. You can obtain information about nodes that are
        configured but not connected to the cluster from the
   <a class="link" href="mysql-cluster-ndbinfo-nodes.html" title="25.6.17.48 The ndbinfo nodes Table">
    <code class="literal">
     nodes
    </code>
   </a>
   and
   <a class="link" href="mysql-cluster-ndbinfo-config-nodes.html" title="25.6.17.10 The ndbinfo config_nodes Table">
    <code class="literal">
     config_nodes
    </code>
   </a>
   tables.
  </p>
  <p>
   The
   <code class="literal">
    processes
   </code>
   table contains the following
        columns:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       node_id
      </code>
     </p>
     <p>
      The node's unique node ID in the cluster
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       node_type
      </code>
     </p>
     <p>
      Type of node (management, data, or API node; see text)
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       node_version
      </code>
     </p>
     <p>
      Version of the
      <code class="literal">
       NDB
      </code>
      software program
            running on this node.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       process_id
      </code>
     </p>
     <p>
      This node's process ID
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       angel_process_id
      </code>
     </p>
     <p>
      Process ID of this node's angel process
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       process_name
      </code>
     </p>
     <p>
      Name of the executable
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       service_URI
      </code>
     </p>
     <p>
      Service URI of this node (see text)
     </p>
    </li>
   </ul>
  </div>
  <h5>
   <a name="idm46045088232096">
   </a>
   Notes
  </h5>
  <p>
   <code class="literal">
    node_id
   </code>
   is the ID assigned to this node in
        the cluster.
  </p>
  <p>
   The
   <code class="literal">
    node_type
   </code>
   column displays one of the
        following three values:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       MGM
      </code>
      : Management node.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       NDB
      </code>
      : Data node.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       API
      </code>
      : API or SQL node.
     </p>
    </li>
   </ul>
  </div>
  <p>
   For an executable shipped with the NDB Cluster distribution,
   <code class="literal">
    node_version
   </code>
   shows the software Cluster
        version string, such as
   <code class="literal">
    8.4.0-ndb-8.4.0
   </code>
   .
  </p>
  <p>
   <code class="literal">
    process_id
   </code>
   is the node executable's
        process ID as shown by the host operating system using a process
        display application such as
   <span class="command">
    <strong>
     top
    </strong>
   </span>
   on Linux, or
        the Task Manager on Windows platforms.
  </p>
  <p>
   <code class="literal">
    angel_process_id
   </code>
   is the system process ID for
        the node's angel process, which ensures that a data node or
        SQL is automatically restarted in cases of failures. For
        management nodes and API nodes other than SQL nodes, the value
        of this column is
   <code class="literal">
    NULL
   </code>
   .
  </p>
  <p>
   The
   <code class="literal">
    process_name
   </code>
   column shows the name of the
        running executable. For management nodes, this is
   <code class="literal">
    ndb_mgmd
   </code>
   . For data nodes, this is
   <code class="literal">
    ndbd
   </code>
   (single-threaded) or
   <code class="literal">
    ndbmtd
   </code>
   (multithreaded). For SQL nodes, this
        is
   <code class="literal">
    mysqld
   </code>
   . For other types of API nodes, it
        is the name of the executable program connected to the cluster;
        NDB API applications can set a custom value for this using
   <a class="ulink" href="/doc/ndbapi/en/ndb-ndb-cluster-connection.html#ndb-ndb-cluster-connection-set-name" target="_top">
    <code class="literal">
     Ndb_cluster_connection::set_name()
    </code>
   </a>
   .
  </p>
  <p>
   <code class="literal">
    service_URI
   </code>
   shows the service network
        address. For management nodes and data nodes, the scheme used is
   <code class="literal">
    ndb://
   </code>
   . For SQL nodes, this is
   <code class="literal">
    mysql://
   </code>
   . By default, API nodes other than
        SQL nodes use
   <code class="literal">
    ndb://
   </code>
   for the scheme; NDB API
        applications can set this to a custom value using
   <code class="literal">
    Ndb_cluster_connection::set_service_uri()
   </code>
   .
        regardless of the node type, the scheme is followed by the IP
        address used by the NDB transporter for the node in question.
        For management nodes and SQL nodes, this address includes the
        port number (usually 1186 for management nodes and 3306 for SQL
        nodes). If the SQL node was started with the
   <a class="link" href="server-system-variables.html#sysvar_bind_address">
    <code class="literal">
     bind_address
    </code>
   </a>
   system variable
        set, this address is used instead of the transporter address,
        unless the bind address is set to
   <code class="literal">
    *
   </code>
   ,
   <code class="literal">
    0.0.0.0
   </code>
   , or
   <code class="literal">
    ::
   </code>
   .
  </p>
  <p>
   Additional path information may be included in the
   <code class="literal">
    service_URI
   </code>
   value for an SQL node reflecting
        various configuration options. For example,
   <code class="literal">
    mysql://198.51.100.3/tmp/mysql.sock
   </code>
   indicates
        that the SQL node was started with the
   <a class="link" href="server-system-variables.html#sysvar_skip_networking">
    <code class="literal">
     skip_networking
    </code>
   </a>
   system variable
        enabled, and
   <code class="literal">
    mysql://198.51.100.3:3306/?server-id=1
   </code>
   shows
        that replication is enabled for this SQL node.
  </p>
 </div>
 <br/>
</div>
