[jbosstools-issues] [JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
Andre Dietisheim (JIRA)
issues at jboss.org
Wed Aug 30 08:46:00 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456176#comment-13456176 ]
Andre Dietisheim edited comment on JBIDE-24868 at 8/30/17 8:45 AM:
-------------------------------------------------------------------
* *Router timeout*:
according to the [docs|https://docs.openshift.org/latest/install_config/configuring_routing.html] one can override the global timeout for a specific route by annotating it:
{code}
{
...
"kind": "Route",
"metadata": {
"annotations": {
"haproxy.router.openshift.io/timeout": "1h",
{code}
Using oc one has to do
{code}
# oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s
{code}
As a non-admin user I can process this change and it seems effective. This is a change that we could apply to the route when debugging, removing it once we stop the debugging.
* *Debug connection timeout*:
Doing a keepalive-ping within the debug connection as arquilian does seems not to be possible for us since we're not in control of the sockets that are used for this sake.
* *lifeness probe*:
this seems like an edge case, not critical. I ack though that with a lifeness probe in place debugging gets annoying since the user would have to manually remove it before and add it back in after debugging.
[~jeffmaury], [~rhuss], [~aurelien.pupier] Thoughts?
was (Author: adietish):
* *Router timeout*:
according to the [docs|https://docs.openshift.org/latest/install_config/configuring_routing.html] one can override the global timeout for a specific route by annotating it:
{code}
{
...
"kind": "Route",
"metadata": {
"annotations": {
"haproxy.router.openshift.io/timeout": "1h",
{code}
Using oc one has to do
{code}
# oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s
{code}
As a non-admin user I can process this change and it seems effective. This is a change that we could apply to the route when debugging, removing it once we stop the debugging.
* *Debug connection timeout*:
Doing a keepalive-ping within the debug connection as arquilian does seems not to be possible for us since we're not in control of the sockets that are used for this sake.
* *lifeness probe":
this seems like an edge case, not critical. I ack though that with a lifeness probe in place debugging gets annoying since the user would have to manually remove it before and add it back in after debugging.
[~jeffmaury], [~rhuss], [~aurelien.pupier] Thoughts?
> 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.x
>
>
> 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.2.3#72005)
More information about the jbosstools-issues
mailing list