Click the Sandbox link for the task you wish to examine. Active Tasks are tasks currently running, and Completed Tasks are tasks that have exited. You should now see two lists of tasks.Service nodes run under a framework whose name matches the service name (default confluent-kafka). The scheduler runs under marathon with a task name matching the service name (default confluent-kafka). Navigate into the correct framework for your needs.Click the Frameworks tab in the upper left to get a list of services running in the cluster.You can also access the logs via the Mesos UI: Use the pull-down in the upper right to select the file to be examined. By default, you will see stdout, but stderr is also useful. In the task details, click on the Logs tab to go into the log viewer.In the list of tasks for the service, click on the task to be examined (scheduler is named after the service, nodes are each named node-server according to their type).Navigate to Services and click on the service to be examined.Visit to access the DC/OS web interface.To view logs for a given node, perform the following steps: In all cases, logs are generally piped to files named stdout and/or stderr. Node logs are useful for examining problems in the service itself.Scheduler logs are useful for determining why a node is not being launched (this is under the purview of the Scheduler).Logs for the scheduler and all service nodes can be viewed from the DC/OS web interface. dcos confluent-kafka -name= plan show deploy To verify whether this is the case, check the service’s deploy plan for any errors.
Certain configuration values may not be changed, or may not be decreased. This commonly occurs when an invalid configuration change was made by the user. After a configuration change, the service may enter an unhealthy state.
0 kommentar(er)
