The Agent installation varies depending on whether it was installed on Windows or Linux.
You can find the install location for your agent by opening the install instructions for your platform, they’re included for both Windows and Linux.
If the agent was installed as a Windows Service, you can manage the agent as you would any other service through the Windows Services tool.
To access the Data Governor Agent service, open the Windows start menu and find the Services program.
All Data Governor Agents are named with the pattern of
dg-agent-[tenant-id], the value of
[tenant-id] being the same value that is
used to store your agent on the host PC.
Once you find the service, you can easily start, stop and restart the agent as you would with any other Windows Service.
If the agent was installed as a systemd service, you can easily manage the service using the
It is highly recommended to use the
systemctl command over the
service command, as the
systemctl provides autocompletion
on tab (eg: typing in
systemctl status dg-agent- and then pressing tab in most cases will automatically fill in the rest of the agents name).
|Stop the agent||
|Restart the agent||
|Start the agent||
|Get the status of the agent service||
Agent’s cannot be “deleted” outright, instead you must migrate all jobs, tasks and data from one agent to another-which will prompt you to delete the agent after the process has been completed.
This can easily be done by going to the agents page and selecting the “Remove Agent” action.
After this you will prompted to select a new agent to migrate all the previous agents associated tasks, jobs and other data to.
Once the migration has finished, you will be prompted if you wish to delete the agent. Once that is finished the agent will be removed from your tenant entirely.
Removing the Agent from Data Governor will not stop it on the host, refer to the FAQ on managing the Agent service for more information.
The Data Governor server requests the agent to send an update on its status every minute, this is considered the “heartbeat” of the agent.
If the most recent heartbeat was sent any longer than 2 minutes ago then the agent is considered unhealthy.
Currently the only task that can only be executed on Windows is the Windows Powershell task as it relies on remoting into Windows Powershell to execute scripts.
Many of the Hadoop workloads such as the HDFS, Spark and Hive integrations do work on Windows but are the easiest to configure when the agent is installed on the cluster itself.