Hi Akila, Yes we faced several issues related to this. Apart from what you have mentioned, we encountered mysql app name is not getting resolved. This could be the delay in updating Mesos DNS. For these issues we looking into following options.
*Option 1:* Use a sleep before deploying a carbon server. Not the best option. *Option 2:* Depend on the health status results. Currently, we do use a health check for mysql apps. Using dcos CLI we can check the status of the app whether the app is alive or not. But this cannot guarantee the DBs are ready to serve requests and Mesos DNS is updated. Thank you! On Wed, Jul 6, 2016 at 10:40 PM, Akila Ravihansa Perera <[email protected]> wrote: > Hi, > > When deploying services to Mesos, the deploy script checks whether port is > open in marathon-lb. But this check fails to identify whether MySQL DBs are > up and running. We might have to figure out a way to handle this. Because > of this issue, the product fails to startup since databases are not ready > to serve requests. The product deployment needs to be on hold until all > databases are ready serve requests. > > Thanks. > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
