Reload: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
Line 5: Line 5:
=Overview=
=Overview=


Available on the root of the management model. Reloads the server by shutting down all its services and starting again. The JVM itself is not restarted.
The <tt>:reload</tt> management model operation is available on the root of the management model. Reloads the server by shutting down all its services and starting again. The JVM itself is not restarted.


In domain mode, it can reloads the configuration on a per-host basis and restarts the servers.
In domain mode, it can reload the configuration on a per-host basis and then restart the servers.
 
The CLI <tt>reload</tt> command sends the <tt>:reload</tt> operation request to the server/domain controller and waits for the controller to close the connection. Then it returns the control back to the client. It does not put the CLI client into the disconnected state. Instead, for the next entered command or operation it will try to automatically re-connect to the controller.


=Standalone=
=Standalone=
Management model command:


<pre>
<pre>
cd /
cd /
:reload
:reload
</pre>
CLI wrapper:
<pre>
reload [--admin-only=true|false] [--use-current-server-config=true|false]
</pre>
</pre>


Line 30: Line 40:
</pre>
</pre>


Domain mode syntax:


 
<pre>
 
[standalone@localhost:9999 /] reload --help
SYNOPSIS
 
  Standalone mode:
 
      reload [--admin-only=true|false] [--use-current-server-config=true|false]
 
  Domain mode:
 
       reload --host=host_name [--admin-only=true|false]
       reload --host=host_name [--admin-only=true|false]
             [--restart-servers=true|false]
             [--restart-servers=true|false]
             [--user-current-domain-config=true|false]
             [--user-current-domain-config=true|false]
             [--user-current-host-config=true|false]
             [--user-current-host-config=true|false]
</pre>


DESCRIPTION
=Behavior on Error=
 
    Sends the :reload operation request to the server/domain controller
    and waits for the controller to close the connection and then
    it returns the control back to the client. It does not put
    the CLI client into the disconnected state. Instead, for the
    next entered command or operation it will try to automatically
    re-connect to the controller.
 
    If there was an i/o error while sending the request or receiving
    the response, the reload handler will disconnect from the controller.
 
    If the reload operation failed, i.e. the response received successfully
    indicated a failure, the handler will log the failure message and
    will not disconnect from the controller.
 
    NOTE: this command cannot be used in a batch because the handler
    is waiting for the controller to shutdown before returning the
    control back to the client which would not possible if the
    command was executed as a step in a composite operation.
    So, if there is a need to reload the controller from a batch,
    :reload operation must be used instead (and should be the last
    operation in the batch).
 
ARGUMENTS


--admin-only  - whether the controller should start in running mode ADMIN_ONLY
If there was an i/o error while sending the request or receiving he response, the reload handler will disconnect from the controller.
                when it restarts. An ADMIN_ONLY controller will start any
                configured management interfaces and accept management
                requests, but will not start servers or, if this host
                controller is the master for the domain, accept incoming
                connections from slave host controllers. If not present, false
                value is assumed.


--host        - is allowed and required only in the domain mode, specifies
If the reload operation failed, i.e. the response received successfully indicated a failure, the handler will log the failure message and will not disconnect from the controller.
                the host name to reload.


--restart-servers  - optional, allowed only in the domain mode. If true the
=Batch=
                      servers will be restarted, and if false the servers will
                be left running and reconnect to the Host Controller when
                started again. If not present, true value is assumed.


--use-current-domain-config  - optional, allowed only in the domain mode. Only
This command cannot be used in a batch because the handler is waiting for the controller to shutdown before returning the control back to the client which would not possible if the command was executed as a step in a composite operation. So, if there is a need to reload the controller from a batch, <tt>:reload</tt> operation must be used instead (and should be the last operation in the batch).
                                has an effect if --read-only-domain-config was
                specified when starting the controller. In that case, if this
                parameter is set to false the reloaded controller loads the
                original configuration version; if null or true the current
                runtime version of the model is used.
                If not present, true value is assumed.


--use-current-host-config  - optional, allowed only in the domain mode. Only
=Command Arguments=
                              has an effect if --read-only-host-config was
                specified when starting the controller. In that case, if this
                parameter is set to false the reloaded controller loads the
                original configuration version; if null or true the current
                runtime version of the model is used.
                If not present, true value is assumed.


--use-current-server-config - optional, allowed only in the standalone mode.
==<tt>--admin-only</tt>==
                                Only has an effect if --read-only-server-config
==<tt>--host</tt>==
                was specified when starting the server. In that case, if this
==<tt>--restart-servers</tt>==
                parameter is set to false the reloaded server loads the
==<tt>--use-current-domain-config</tt>==
                original configuration version; if null or true the current
==<tt>--use-current-host-config</tt>==
                runtime version of the model is used.
==<tt>--use-current-server-config</tt>==
                If not present, true value is assumed.

Latest revision as of 19:18, 27 May 2016

Internal

Overview

The :reload management model operation is available on the root of the management model. Reloads the server by shutting down all its services and starting again. The JVM itself is not restarted.

In domain mode, it can reload the configuration on a per-host basis and then restart the servers.

The CLI reload command sends the :reload operation request to the server/domain controller and waits for the controller to close the connection. Then it returns the control back to the client. It does not put the CLI client into the disconnected state. Instead, for the next entered command or operation it will try to automatically re-connect to the controller.

Standalone

Management model command:

cd /
:reload

CLI wrapper:

reload [--admin-only=true|false] [--use-current-server-config=true|false]

Domain Mode

To reload the domain controller configuration, execute on the domain controller:

reload --host=dc1

To reload a subordinate host controller and associated servers:

reload --host=h1 --restart-servers=true

Domain mode syntax:

      reload --host=host_name [--admin-only=true|false]
             [--restart-servers=true|false]
             [--user-current-domain-config=true|false]
             [--user-current-host-config=true|false]

Behavior on Error

If there was an i/o error while sending the request or receiving he response, the reload handler will disconnect from the controller.

If the reload operation failed, i.e. the response received successfully indicated a failure, the handler will log the failure message and will not disconnect from the controller.

Batch

This command cannot be used in a batch because the handler is waiting for the controller to shutdown before returning the control back to the client which would not possible if the command was executed as a step in a composite operation. So, if there is a need to reload the controller from a batch, :reload operation must be used instead (and should be the last operation in the batch).

Command Arguments

--admin-only

--host

--restart-servers

--use-current-domain-config

--use-current-host-config

--use-current-server-config