Unregister Data Collector from Control Hub

You can unregister a Data Collector from StreamSets Control Hub when you no longer want to use that Data Collector installation with Control Hub.

When you restart an unregistered Data Collector, previously-configured Data Collector user accounts become immediately available unless changed in the interim. Use your Data Collector user account to log in.

Pipeline permissions, however, are not automatically reverted. To ensure that users can access pipelines, transfer pipeline permissions from the obsolete Control Hub users and groups back to Data Collector users and groups. Or, you can edit pipeline permissions individually.

The method you use to unregister a Data Collector depends on the Data Collector installation type:

Tarball installation: You can unregister the Data Collector from the Data Collector UI, from the command line interface, or from Control Hub.
RPM installation: You must unregister the Data Collector from Control Hub.
Cloudera Manager installation: You must unregister the Data Collector from both Control Hub and Cloudera Manager.

Unregistering from Data Collector

For a Data Collector tarball installation, you can unregister the Data Collector from Control Hub using the Data Collector UI.

Note: For a Data Collector RPM installation, you must use Control Hub to unregister the Data Collector. For a Data Collector installation with Cloudera Manager, you must use both Control Hub and Cloudera Manager to unregister the Data Collector.

In Control Hub, stop all jobs started on the Data Collector.
In Data Collector, click Administration > Disable Control Hub.
The Disable Control Hub dialog box appears.
To disable Data Collector from working with Control Hub, click Yes.
Restart Data Collector.

After restarting Data Collector, use your Data Collector user account to log in.

To ensure that users can access pipelines, transfer pipeline permissions from the obsolete Control Hub users and groups back to Data Collector users and groups. Or, you can edit pipeline permissions individually.

For more information about transferring permissions, see Transferring Permissions. For information about configuring individual pipeline permissions, see Sharing Pipelines.

Unregistering from the Command Line Interface

For a Data Collector tarball installation, you can unregister the Data Collector from Control Hub using the Data Collector command line interface.

For a Data Collector RPM installation, you must use Control Hub to unregister the Data Collector. For a Data Collector installation with Cloudera Manager, you must use both Control Hub and Cloudera Manager to unregister the Data Collector.

Note: To use an automation tool such as Ansible, Chef, or Puppet to automate the unregistering of Data Collectors, configure the tool to use the

streamsets sch
                unregister

command. The command must be run on the local machine where Data Collector is installed. The Data Collector does not need to be running. See the command line help for the list of available options. If you choose to skip updating the dpm.properties configuration file, you must configure the automation tool to update the file.

Start the Data Collector, and then use the system disableDPM command to unregister the Data Collector.

Use the command from the $SDC_DIST directory as follows:

bin/streamsets cli \
(-U <sdcURL> | --url <sdcURL>) \
[(-a <sdcAuthType> | --auth-type <sdcAuthType>)] \
[(-D <dpmURL> | --dpmURL <dpmURL>)] \ 
[(-u <sdcUser> | --user <sdcUser>)] \
[(-p <sdcPassword> | --password <sdcPassword>)] \
system disableDPM

When using the system disableDPM command, the following basic options are required:


Basic Option	Description
-U <sdcURL> or --url <sdcURL>	Required. URL of the Data Collector. The default URL is `http://localhost:18630`.
-a <sdcAuthType> or --auth-type <sdcAuthType>	Required. Authentication type used by the Data Collector. Set to `dpm`. If you omit this option, Data Collector uses the Form authentication type, which causes the disableDPM command to fail.
-D <dpmURL> or --dpmURL <dpmURL>	Required. Enter the appropriate URL: For Control Hub cloud, enter `https://cloud.streamsets.com`. For Control Hub on-premises, enter the URL provided by your system administrator. For example, `https://<hostname>:18631`.
-u <sdcUser> or --user <sdcUser>	Required. Enter your Control Hub user ID using the following format: `<ID>@<organization ID>` If you omit this option, Data Collector uses the `admin` user account, which causes the disableDPM command to fail.
-p <sdcPassword> or --password <sdcPassword>	Required. Enter the password for your Control Hub user account.

For example, the following command unregisters a Data Collector with Control Hub:

bin/streamsets cli -U http://localhost:18630 -a dpm -D https://cloud.streamsets.com -u alison@MyOrg -p MyPassword system disableDPM

Restart the Data Collector to apply the changes.

After restarting Data Collector, use your Data Collector user account to log in.

For more information about transferring permissions, see Transferring Permissions. For information about configuring individual pipeline permissions, see Sharing Pipelines.

Unregistering from Control Hub and Cloudera Manager

If you installed a Data Collector through Cloudera Manager, you must use both Control Hub and Cloudera Manager to unregister the Data Collector.

You use Control Hub to deactivate the authentication token. Then, you use Cloudera Manager to modify Data Collector configuration properties and files.

In Control Hub, stop all jobs running on the Data Collector.
In Cloudera Manager, shut down the Data Collector.
In Control Hub, click Execute > Data Collectors in the Navigation panel.
Hover over the Data Collector that you shut down, and then click the Delete icon.
In the confirmation dialog box, click Delete and Unregister.
In Cloudera Manager, select the StreamSets service, then click Configuration.
Enter "Control Hub" in the search field to display the Control Hub configuration properties.
Clear the Enable Control Hub property.
Find the location to the authentication token file in the Control Hub Token Location property, and then delete the file.

After restarting Data Collector, use your Data Collector user account to log in.

To ensure that users can access pipelines, use Data Collector to transfer pipeline permissions from the obsolete Control Hub users and groups back to Data Collector users and groups. Or, you can edit Data Collector pipeline permissions individually.