If you are using DC/OS 1.11 or later:
To uninstall the service from the DC/OS CLI, enter:
dcos package uninstall miniod
Uninstalling the service consists of the following steps.
The scheduler is relaunched in Marathon with the environment variable SDK_UNINSTALL set to “true”. This puts the Scheduler in an uninstall mode.
The scheduler uninstalls the package with the following actions:
- All running tasks for the service are terminated so that Mesos will reoffer their resources.
- As the task resources are offered by Mesos, they are unreserved by the scheduler.
- Once all known resources have been unreserved, the scheduler’s persistent state in ZooKeeper is deleted.
The cluster automatically removes the scheduler task once it advertises the completion of the uninstall process.
Debugging an uninstall
In the vast majority of cases, this uninstall process goes off without a hitch. However, in certain situations, there can be snags along the way. For example, perhaps a machine in the cluster has permanently gone away, and the service being uninstalled had some resources allocated on that machine. This can result in the uninstall becoming stuck, because Mesos will never offer those resources to the uninstalling scheduler. Thus, the uninstalling scheduler will not be able to successfully unreserve the resources it had reserved on that machine.
This situation is indicated by looking at the deploy plan while the uninstall is proceeding. The deploy plan may be viewed using either of the following methods:
running dcos package install --cli minioif needed):
dcos minio --name=minio plan show deploy
If all else fails, you can manually perform the uninstall yourself. To do this, perform the following steps:
Delete the uninstalling scheduler from Marathon.
Unregister the service from Mesos using its UUID as follows:
dcos service --inactive | grep miniod miniod False 3 3.3 6240.0 15768.0 97a0fd27-8f27-4e14-b2f2-fb61c36972d7-0096 dcos service shutdown 97a0fd27-8f27-4e14-b2f2-fb61c36972d7-0096