Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Imesh Gunaratne]

On Wed, Jul 20, 2016 at 5:36 PM, Akila Ravihansa Perera 
wrote:

> Hi Imesh,
>
> Sorry for the confusion. In deploy script we are using DCOS CLI to get the
> status of the service. We had a Python script earlier to create a TCP
> socket to check whether service is active. But that is not a reliable
> solution since network might not be reachable from where the deploy script
> is being executed and also creating a TCP socket is not equivalent to
> creating a HTTP connection and checking the HTTP status code which is
> already handled by Mesos. So we offload that work to Mesos and let the
> users define any type of health check they think is suitable.
>

​Great! Thanks for the explanation Akila!​


>
> Thanks.
>
> On Wed, Jul 20, 2016 at 4:57 PM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Wed, Jul 20, 2016 at 1:19 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> mysqladmin client need not be installed on host machine since Mesos will
>>> run this command as a "docker run" command which will be executed inside
>>> the container. MySQL official image contains mysqladmin tool so this is not
>>> a problem.
>>>
>>
>> ​I thought this was regarding the check we need to make before deploying
>> the WSO2 server containers to wait until MySQL containers become ready.
>> ​
>>
>> ​Thanks​
>>
>>
>>> Thanks.
>>>
>>> On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Akila,

 On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> 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.
>

 ​Wouldn't this make it mandatory to have mysqladmin client installed in
 the host machine where the deployment script is run?

 Thanks​


>
> Thanks.
>
> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
>> 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 >> > 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
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



 --
 *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


>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
*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

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Akila Ravihansa Perera]

Hi Imesh,

Sorry for the confusion. In deploy script we are using DCOS CLI to get the
status of the service. We had a Python script earlier to create a TCP
socket to check whether service is active. But that is not a reliable
solution since network might not be reachable from where the deploy script
is being executed and also creating a TCP socket is not equivalent to
creating a HTTP connection and checking the HTTP status code which is
already handled by Mesos. So we offload that work to Mesos and let the
users define any type of health check they think is suitable.

Thanks.

On Wed, Jul 20, 2016 at 4:57 PM, Imesh Gunaratne  wrote:

>
>
> On Wed, Jul 20, 2016 at 1:19 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Imesh,
>>
>> mysqladmin client need not be installed on host machine since Mesos will
>> run this command as a "docker run" command which will be executed inside
>> the container. MySQL official image contains mysqladmin tool so this is not
>> a problem.
>>
>
> ​I thought this was regarding the check we need to make before deploying
> the WSO2 server containers to wait until MySQL containers become ready.
> ​
>
> ​Thanks​
>
>
>> Thanks.
>>
>> On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Akila,
>>>
>>> On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 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.

>>>
>>> ​Wouldn't this make it mandatory to have mysqladmin client installed in
>>> the host machine where the deployment script is run?
>>>
>>> Thanks​
>>>
>>>

 Thanks.

 On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne 
 wrote:

>
>
> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
> 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 
>> 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
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 Blog: http://ravihansa3000.blogspot.com

>>>
>>>
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> *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
>
>


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

Blog: http://ravihansa3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Imesh Gunaratne]

On Wed, Jul 20, 2016 at 1:19 PM, Akila Ravihansa Perera 
wrote:

> Hi Imesh,
>
> mysqladmin client need not be installed on host machine since Mesos will
> run this command as a "docker run" command which will be executed inside
> the container. MySQL official image contains mysqladmin tool so this is not
> a problem.
>

​I thought this was regarding the check we need to make before deploying
the WSO2 server containers to wait until MySQL containers become ready.
​

​Thanks​


> Thanks.
>
> On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne  wrote:
>
>> Hi Akila,
>>
>> On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> 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.
>>>
>>
>> ​Wouldn't this make it mandatory to have mysqladmin client installed in
>> the host machine where the deployment script is run?
>>
>> Thanks​
>>
>>
>>>
>>> Thanks.
>>>
>>> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne  wrote:
>>>


 On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
 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 
> 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
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
*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
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Akila Ravihansa Perera]

Hi Imesh,

mysqladmin client need not be installed on host machine since Mesos will
run this command as a "docker run" command which will be executed inside
the container. MySQL official image contains mysqladmin tool so this is not
a problem.

Thanks.

On Wed, Jul 20, 2016 at 12:46 PM, Imesh Gunaratne  wrote:

> Hi Akila,
>
> On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> 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.
>>
>
> ​Wouldn't this make it mandatory to have mysqladmin client installed in
> the host machine where the deployment script is run?
>
> Thanks​
>
>
>>
>> Thanks.
>>
>> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
>>> 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 
 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
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> *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
>
>


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

Blog: http://ravihansa3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Imesh Gunaratne]

Hi Akila,

On Mon, Jul 18, 2016 at 4:58 PM, Akila Ravihansa Perera 
wrote:

> 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.
>

​Wouldn't this make it mandatory to have mysqladmin client installed in the
host machine where the deployment script is run?

Thanks​


>
> Thanks.
>
> On Mon, Jul 18, 2016 at 9:56 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
>> 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 
>>> 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
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
*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
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Akila Ravihansa Perera]

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  wrote:

>
>
> On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa 
> 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 
>> 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
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Blog: http://ravihansa3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Imesh Gunaratne]

On Thu, Jul 7, 2016 at 10:51 AM, Isuru Haththotuwa  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 
> 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
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Isuru Haththotuwa]

Hi,

Yes, myself and Pubudu also faced this issue, lets fix it properly.

On Wed, Jul 6, 2016 at 10:57 PM, Pubudu Gunatilaka  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.

Thank you!





> On Wed, Jul 6, 2016 at 10:40 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> 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>
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Mesos artifacts] Deploy script is failing to check database service

[Pubudu Gunatilaka]

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 
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
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Mesos artifacts] Deploy script is failing to check database service

[Akila Ravihansa Perera]

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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev