I want to run redis server cluster on mesos, but have some problems. The first problem is the storage path, since it is storage service, I need to set the storage path out of the sandbox, so the next run of the service will find the data. and the data will not get garbage collected. The scheduler will keep track of storage services and its state, and pass storage path to the executor to create or restart a storage service.
Does this solution have any problems? And another problem is that when the slave is deactived due to network partition or slave process exited for more than 75 seconds, when the slave connected again, the slave will be asked to shutdown itself and all its tasks, so all the running storage services will be shutdown and you have to start the slave again, and restart all the storage services. If the service takes long time to restart, it will cause the service unavailable for a while. Are there any way to solve this problem? like instead of simply shut down the deactived slave and all its task, let framework decide how to handle the re-registering of deactivated slave. I read the code, it says "We disallow deactivated slaves from re-registering, we don't allow the slave to re-register, as we've already informed frameworks that the tasks were lost."
