You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexandr (JIRA)" <ji...@apache.org> on 2019/04/10 19:57:00 UTC

[jira] [Created] (MESOS-9726) No running tasks in marathon after restart non-leader mesos-master node

Alexandr created MESOS-9726:
-------------------------------

             Summary: No running tasks in marathon after restart non-leader mesos-master node
                 Key: MESOS-9726
                 URL: https://issues.apache.org/jira/browse/MESOS-9726
             Project: Mesos
          Issue Type: Bug
            Reporter: Alexandr


Good day!
I have problem with my mesos-cluster:
I have 3 mesos-master nodes with Marathon cluster (lets call them - Mas1,Mas2,Mas3) and 3 mesos-slave nodes (lets call them - Slv1,Slv2,Slv3) with running apps on it. And I also have a Zookeeper cluster on nodes Mas1,Mas2,Mas3.
So, Mesos leader - master-node "Mas1".
After I restarted master-node "Mas3" - he got back to the Mesos cluster, everything is fine but after a moment I opened Marathon and all running tasks from my mesos-slave nodes became "unknown" and have no instances on it. 
So I checked:
1. My mesos agents - everything was ok, 3 agents running. 
2. That all services are running and all clusters (Mesos\Marathon\Zookeeper) are fine
3. Decided to restart all mesos-slave services on slave nodes - on slave-node Slv3 1 of 3 instances launched for all applications, then restarted all marathon-services. After it all tasks switched to status "Waiting"\"Delayed".
4. Checked mesos-master and slave logs, no errors or information about any problems on cluster - only information about killing and launching new tasks on slave-node.
5. Decided to stop-start mesos-master service for re-election of a Mesos leader. 
After it leader became master-node "Mas2" and all tasks in marathon started to run instances like normal. 

Logs will be uploaded later. Wonder how it could happen



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)