Major Description
Not sure if this is still present on 2.0, need to verify.
From the logs: You'll be able to see that two memcached processes are running after an Erlang crash.
While we have a workaround for this, I want to ensure we are able to identify why/when this happens and prevent it in the future. We have seen this happen under a variety of scenarios, so I think some "protection" is required when Erlang starts up and sees a memcached process already running.