[jbosstools-issues] [JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482838#comment-13482838 ] 

Andre Dietisheim edited comment on JBIDE-24868 at 10/27/17 8:53 AM:
--------------------------------------------------------------------

What seems very likely the cause for node is the livenessProbe that's set to 30secs: 
{code}
                    "livenessProbe" : {
                        "httpGet" : {
                            "path" : "/pagecount",
                            "port" : 8080,
                            "scheme" : "HTTP"
                        },
                        "initialDelaySeconds" : 30,
                        "timeoutSeconds" : 3,
                        "periodSeconds" : 10,
                        "successThreshold" : 1,
                        "failureThreshold" : 3
                    },
{code}

They are present for the dc in the template:  https://github.com/openshift/nodejs-ex/blob/master/openshift/templates/nodejs-mongodb-persistent.json#L393

So if we add a timeout to the route we also need to disable or increase the timeout for the livenessProbe.

The docs for *livenessProbe*, *readynessProbe* etc. in Kube are at https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/


was (Author: adietish):
What seems very likely the cause for node is the livenessProbe that's set to 30secs: 
{code}
                    "livenessProbe" : {
                        "httpGet" : {
                            "path" : "/pagecount",
                            "port" : 8080,
                            "scheme" : "HTTP"
                        },
                        "initialDelaySeconds" : 30,
                        "timeoutSeconds" : 3,
                        "periodSeconds" : 10,
                        "successThreshold" : 1,
                        "failureThreshold" : 3
                    },
{code}

They are present for the dc in the template:  https://github.com/openshift/nodejs-ex/blob/master/openshift/templates/nodejs-mongodb-persistent.json#L393

So if we add a timeout to the route we also need to disable or increase the timeout for the livenessProbe.

> Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-24868
>                 URL: https://issues.jboss.org/browse/JBIDE-24868
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.5.0.Final
>            Reporter: Aurélien Pupier
>            Assignee: Andre Dietisheim
>              Labels: openshift_v3, server_adapter
>             Fix For: 4.5.1.Final
>
>         Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png
>
>
> it will avoid to have "debug connections always killed after 30s staying in a breakpoint"
> see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion
> k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)