Toggle lockless code deploys on or off
Use the toggle_lockless_deploys
plan to turn lockless code deploys
on or off across all compiler nodes, including the primary server and the
replica.
Before you begin:
For the toggle plan to run successfully, all compiler nodes (including the primary server and the replica) must have the same lockless code deploys status: the feature must be enabled on all or disabled on all. The plan cannot proceed if some nodes have the feature enabled while others have it disabled. To bring your compiler nodes into alignment, you can Disable lockless code deploys on individual compiler nodes.
For the toggle plan to run successfully, all compiler nodes (including the primary server and the replica) must have the same lockless code deploys status: the feature must be enabled on all or disabled on all. The plan cannot proceed if some nodes have the feature enabled while others have it disabled. To bring your compiler nodes into alignment, you can Disable lockless code deploys on individual compiler nodes.
You can use the toggle_lockless_deploys
plan by running these
commands on the primary server:
- To enable lockless code
deploys:
puppet infra run toggle_lockless_deploys enable=true
- To disable lockless code
deploys:
puppet infra run toggle_lockless_deploys enable=false
If you do not specify
true
orfalse
,true
is the default. - Optionally, you can use the
old_code_directory
parameter with either thesave
ordelete
values, to specify whether you want to save old code directories to${codedir}_backup
. For example:puppet infra run toggle_lockless_deploys enable=true old_code_directory=save
If you do not specify the
old_code_directory
parameter,save
is set by default.
You can optimize file sync performance for lockless code deploys
by configuring the
versioned_sync_pool
and copy_method
settings in the puppet_enterprise::profile::master::file_sync
class. See Code Manager settings .