Configuring and tuning orchestration

After installing PE, you can change some default settings to further configure the orchestrator and pe-orchestration-services.

Configure the orchestrator and pe-orchestration-services

There are several optional parameters you can add to configure the behavior of the orchestrator and pe-orchestration-services. Because they are profile classes, you can change these in the console in the PE Orchestrator group.

Integer representing the number of simultaneous task or plan actions that can run at the same time in the orchestrator. All task and plan actions are limited by this concurrency limit regardless of transport type (WinRM, SSH, PCP).
Default: "250" (actions)
An integer that determines the maximum number of simultaneous task or plan requests orchestrator can make to bolt-server. Only task or plan executions on nodes with SSH or WinRM transport methods are limited by this setting because only they require requests to bolt-sever.
Default: "100" (requests)
CAUTION: Do not set a concurrency limit that is higher than the bolt-server limit. This can cause timeouts that lead to failed task runs.
Disable or enable the PXP service by setting it to true or false. If you disable this setting you can’t use the orchestrator or the Run Puppet button in the console.
Default: true
An integer that determines how many concurrent compile requests can be outstanding to the master, across all orchestrator jobs.
Default: "8" (requests)
Integer that represents the number of days before job reports are removed.
Default: "30" (days)
An integer that represents how many seconds must pass while an agent attempts to connect to a PCP broker. If the agent can’t connect to the broker in that time frame, the run times out.
Default: "30" (seconds)
Disable or enable orchestration services. Set to true or false.
Default: true
Enable or disable application management. Set to true or false.
Default: false

Configure the PXP agent

Puppet Execution Protocol (PXP) is a messaging system used to request tasks and communicate task statuses. The PXP agent runs the PXP service and you can configure it using Hiera.

Controls how frequently (in seconds) PXP agents will ping PCP brokers. If the brokers don’t respond, the agents try to reconnect.
Default: 120 (seconds)
A string that represents the path to the PXP agent log file and can be used to debug issues with orchestrator.
  • *nix: /var/log/puppetlabs/pxp-agent/pxp-agent.log

  • Windows: C:\Program Data\PuppetLabs\pxp-agent\var\log\pxp-agent.log

The amount of time to keep records of old Puppet or task runs on agents. You can declare time in minutes (30m), hours (2h), and days (14d).
Default: 14d
Controls how long tasks are cached after use. You can declare time in minutes (30m), hours (2h), and days (14d).
Default: 14d

Correct ARP table overflow

In larger deployments that use the PCP broker, you might encounter ARP table overflows and need to adjust some system settings.

Overflows occur when the ARP table—a local cache of IP address to MAC address resolutions—fills and starts evicting old entries. When frequently used entries are evicted, network traffic will increase to restore them, increasing network latency and CPU load on the broker.

A typical log message looks like:

[root@s1 peadmin]# tail -f /var/log/messages
Aug 10 22:42:36 s1 kernel: Neighbour table overflow.
Aug 10 22:42:36 s1 kernel: Neighbour table overflow.
Aug 10 22:42:36 s1 kernel: Neighbour table overflow.

To work around this issue:

Increase sysctl settings related to ARP tables.
For example, the following settings are appropriate for networks hosting up to 2000 agents:
# Set max table size
# Start aggressively clearing the table at this threshold
# Don't clear any entries until this threshold