You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Marc Roos <M....@f1-outsourcing.eu> on 2019/08/23 12:08:50 UTC

W0823 12:00:46. process.cpp:1453] Failed to link to '192.168.142.50:40746', connect: Failed connect: connection closed


When scaling the task from 0 to 1, it takes sometimes quite a while for 
it to become active. Waiting maybe 10-20 seconds on the first waiting 
reported by marathon. 

Step 1: deploying (fast)
Step 2: sometimes fast / sometimes 10-20 seconds
Step 3: DHCPREQUEST and DHCPACK (fast)
Step 4: Right after DHCPACK this error from the agent
        W0823 13:08:16.595113 2663211 process.cpp:1453] Failed to link 
to '192.168.142.53:41715', connect: Failed connect: connection closed
Step 5: waiting (fast)
Step 6: running (fast)

Sometimes the same task is instantly running. Although having the same 
'connection closed' error after the DHCPACK.