Hi Imesh,

I've switched to command based health check for MySQL services. It will
basically run "mysqladmin -u $MYSQL_USER -p$MYSQL_PASSWORD status". This
will ensure MySQL service is ready to serve SQL requests.

Thanks.

On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne <[email protected]> wrote:

>
>
> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa <[email protected]>
> wrote:
>
>> Hi,
>>
>> Yes, myself and Pubudu also faced this issue, lets fix it properly.
>>
>> On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka <[email protected]>
>> wrote:
>>
>>> 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.
>>>
>>
>
>> What if we query the Mesos DNS in addition to port checking to see if its
>> updated? AFAIR what we are seeing is an java.net.UnknownHostException,
>> related to the DB hostname.
>>
>
> ​May be we can wait for MySQL sockets as we do for Carbon server
> transports.
>
> Thanks​
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

Blog: http://ravihansa3000.blogspot.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to