Cloudera Docs

Migrate Knox Gateway service from one host to another

Learn how to migrate the Knox Gateway service from one host to another host in your cluster using Cloudera Manager.

Before migrating the Knox Gateway service, verify if any custom topologies have been manually added to the cluster. If custom topologies exist, convert them to shared provider configurations and descriptors using Knox simplified topology management in Cloudera Manager. This ensures they are automatically replicated to the new host. For detailed instructions, see Add a new shared provider configuration and Add a custom descriptor to Apache Knox.

  1. In Cloudera Manager, select the Knox service.
  2. Click Instances > Add Role Instances.
  3. Select the new host where you want to migrate the Knox Gateway service.
    When you add the new Knox Gateway role instance, the default topology files are automatically copied to the new host. If you converted custom topologies to shared provider configurations and descriptors using Knox simplified topology management in Cloudera Manager, they are also automatically deployed to the new host.
  4. Click Continue.
  5. Start the Knox Gateway role on the new host.
  6. Test the Knox Gateway functionality on the new host by verifying that you can access Knox Gateway services through the new host and that all topologies and descriptors are functioning correctly.
  7. Monitor the Knox Gateway service on the new host for any issues or anomalies. Review the logs and metrics to ensure the service is operating normally after migration.
  8. After confirming that the Knox Gateway service is functioning correctly on the new host, remove the Knox Gateway role instance from the old host.
    1. Stop the Knox Gateway role on the old host.
    2. Delete the Knox Gateway role instance from the old host.