Migrating Ranger Usersync and Tagsync role groups

You can use Host Templates to back up the existing usersync and tagsync role group configurations and migrate them to a new host.

If the host on which your usersync and tagsync role groups run fails and cannot restart, you can migrate the role groups to a new host. You must stop usersync and tagsync and delete them from their original host before using them on the new one. Cloudera Manager > Host Templates supports backing up, stopping, deleting, and migrating usersync and tagsync role groups from one host to another.

  1. Log in to your cluster as administrator, using Cloudera Manager.
  2. Back up you usersync and tagsync configurations.
    1. On Cloudera Manager > Hosts, select Host Templates.
    2. On Host Templates, click Create.
    3. In Template Name, type a template name.
      This names a template in which you back up the usersync and tagsync role group configurations.
    4. On Create New Host Template for Cluster expand Ranger, select Ranger Tagsync and Ranger Usersync, then click Create, as shown in the following:
      Figure 1. Creating a role groups template
  3. On Cloudera Manager > Ranger > Instances, select the Ranger Tagsync and Ranger Usersync role groups, as shown.
Stopping, deleting and adding role instances
  1. In Actions for Selected, select Stop.
  2. In Actions for Selected, select Delete.
  3. Click Add Role Instances.
    1. In Add Role Instances to Ranger > Assign Roles > Ranger Tagsync x 1 New, click Select Hosts.
    2. Choose a new host to which the Ranger Tagsync role will be added.
    3. In Add Role Instances to Ranger > Assign Roles > Ranger Usersync x 1 New, click Select Hosts.
    4. Choose a new host to which the Ranger Usersync role will be added.
    5. On Review Changes, click Finish.
    6. On Cloudera Manager > Ranger > Instances, select the Ranger Tagsync and Ranger Usersync role groups on the new host.
    7. With Usersync and Tagsync roles selected on the new host, in Actions, select Start.
  4. Restart Ranger service.
  5. Restart any stale services, if necessary.