DLM Administration
Also available as:
loading table of contents...

Update replication policy

You can edit some settings in your policies to better align with changing requirements. For example, you might want to change the frequency of a policy depending on the data size and importance of the data being replicated.

The Edit Replication Policy page is not available prior to DLM version 1.1.1.
  • You can edit an existing policy, with the following restrictions:
    • Only non-expired policies in active or suspended state can be edited.
    • The start time cannot be modified if the policy has already started.
    • You cannot modify the policy name or the source or destination cluster.
  • DLM does not support update of any cluster endpoints (HDFS, Hive, Ranger, or DLM Engine). If an endpoint must be modified, contact Hortonworks support for assistance.
You must use the DLM Infrastructure Admin role to perform this task.
  1. In the DLM navigation pane, click Policies.
    The Replication Policies page displays a list of any existing policies.
  2. Locate the policy you want to edit and click (Actions).
  3. Select Edit and then modify and save the policy.
    The following options are available to edit:
    • Frequency
    • Start Date (if the policy has not yet run an initial job instance)
    • End Date
    • Start Time
    • Queue Name
    • Maximum Bandwidth
    • Maximum Maps
    If the Edit option does not display, verify that the policy status is active or suspended. Expired policies cannot be edited.
  4. To edit policy description and key selection, on the Policies Page, click the policy name.
    The Policy Settings display.
    Key selection is only available for policies that are replicating TDE-enabled data.
  5. Click the Edit icon next to Description or Source & Destination Encrypted With.
    Clicking the Edit icon next to other items in Policy Settings opens the Edit Replication Policy wizard.
  6. Click the checkmark to save the change and close the edit option.

View job status to verify that the replication job is running as intended.