Waiting for engine...
Skip to main content

Configuring Secure Listen for Runtime cloud Attachments

After enabling Secure Listen for a Runtime cloud, configure the individual attachment settings for the Cloud.

Before you begin​

You must be the account owner of the Cloud to set properties.

Note:

  • You receive a warning on the Listeners panel for the Runtime cloud attachment if you set the Execution workers property to zero, indicating that the Runtime cloud attachment does not have any execution workers.
  • You receive a warning on the Listeners panel for the Runtime cloud attachment if you set the Minimum Execution Workers property to zero, indicating that the attachment does not have the required minimum number of execution workers.
  • You receive a warning on the Listeners panel if you set the Execution Worker Warmup Enabled property to False. If not set properly, the Execution worker and listener may appear to be functioning properly on all nodes, but may be paused or stopped.

Procedure​

  1. Go to Manage > Cloud Management.

  2. On the Clouds tab, select the Runtime cloud.

  3. Click the Attachment Quotas tab.

  4. Click the Runtime.

    The Atom’s property values appear in the right pane. If these values were not set at the runtime cloud clusters level, then the default values are displayed. If any of these values were set at the runtime cloud clusters level, then the runtime cloud clusters’s values are displayed. If any of these values were set at the Atom level, then the Atom’s values are displayed.

  5. Edit the following Atom’s property values:

    1. Set the Execution Workers property value to at least one. To fully utilize the Secure Listen functionality in an attachment of the Runtime cloud, the attachment must have at least one assigned Execution worker. The value provided determines the maximum number of execution workers that can be active for the attachment when required. The Listener will run and execute from any active worker.

    2. Set the Minimum Execution Workers property value to at least one. The value provided determines the number of execution workers that are active and running at any time, regardless of work load. Secure Listen requires at least one to ensure that an Execution worker is always available when deploying or starting listeners on the attachment. To avoid the possibility of no execution workers being available, it is recommended that you specify multiple Minimum Execution Workers so there is never a period where no workers are active.

    3. Set the Execution Worker Warmup Enabled property value to True. This forces new execution workers to start up and become active when any current workers are close to shutting down. For example, if an Execution worker is configured to live for 12 hours and then shut down, a new worker starts up and becomes active before each existing worker is scheduled to be terminated after 12 hours.

  6. Optional: If you make a mistake and want to see the previously saved values, click Reload.

  7. Click Save.

    The property values are saved in a file named after the account ID in the <molecule_install_dir>\conf\limits directory.

On this Page