<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scout24 on webratz.de</title><link>https://www.webratz.de/tags/scout24/</link><description>Recent content in Scout24 on webratz.de</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Oct 2018 21:44:13 +0200</lastBuildDate><atom:link href="https://www.webratz.de/tags/scout24/index.xml" rel="self" type="application/rss+xml"/><item><title>ECS / Docker NFS Issue hunt down</title><link>https://www.webratz.de/article/nfs-bug-hunting/</link><pubDate>Wed, 10 Oct 2018 21:44:13 +0200</pubDate><guid>https://www.webratz.de/article/nfs-bug-hunting/</guid><description>&lt;p&gt;&lt;em&gt;This post appeared initially on the &lt;a href="https://medium.com/scout24-engineering/ecs-docker-nfs-issue-hunt-down-81d44adac042"&gt;Scout24 Engineering Blog&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Who doesn’t know this situation: Sometime something weird is going on in your setup, but everything is so vague that you don’t know where to start. This is a story about a bug we experienced in a production setup and how we found out what was the root cause.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;The problem&lt;/h2&gt;
&lt;p&gt;Imagine a ECS cluster with multiple tasks running with an NFS (EFS in this case) backed persistent root volume. Launching new tasks works just fine but as soon you are doing a cluster upgrade complete hosts seem to be unable to start tasks or can only start a few and then break. But also some hosts just work fine. So scaling up or down your cluster is a really scary thing that could not be done anymore without manual intervention. That’s an unacceptable situation, but what to do?&lt;/p&gt;</description></item></channel></rss>