title: Daemon service in ECS throwing no space left on device
body: <p>Recently after a production deployment, our primary service was not reaching steady state. On analysis we found out that the filebeat service running as a daemon service was unsteady. The stopped tasks were throwing &quot;no space left on the device&quot;. Also, the CPU and memory utilization for the filebeat was higher than the primary service.
  A large amount of log files were being stored as part of the release. After reverting the change, the service came back to steady state.</p>
  <p>Why did filebeat become unsteady? If memory was an issue, then why didn't the service also throw &quot;no space&quot; issue as both filebeat and primary service runs on the same EC2 instance?</p>