Managing nodes

After you have set up your nodes and their members, you can work with nodes using the following tasks.

For more details, refer to the documentation on commands.

  • Softstop a member. The HTTP and message fabric receiver services configured in that member that can be quiesced are not allowed to take any new requests but allowed to continue with in-progress work.

    If you softstop a member with a specified timeout, and the in-progress work completes before the end of the timeout period, the member will be stopped immediately.

    You also can choose not to specify a timeout period. For example, you might not know how long it takes the services to finish processing. When you do not specify a timeout period, the member does not stop until all of the services finish processing.

    For more information, see member softstop command.

  • Deactivate a stopped member on the node into which you are logged. When you restart the node, the deactivated member will no longer start automatically. You can recreate a member that you deactivate.

    Deactivation also removes the member configuration from the data grid. For catalog members, the grid configuration associated with the catalog server also is removed from the grid.

    CAUTION:
    The deactivation of a catalog member eventually stops every other component that uses that catalog member or makes them not accessible.
  • Force the removal, from the data grid, of the configuration of a member that is no longer accessible. This command works only on remote members, which are members that are not on the node from which the command is being executed.
    This is a cleanup tool for when:
    • The node hosting the member is not available.
    • The member has been corrupted or destroyed and you cannot run the member deactivate command.