[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title Sergio Merino reopened an issue I am reopening the ticket because I am having this issue and He Bihong is right. You can change the max requests per host, but given that the default max requests is 64, there is no way of going over that Jenkins / JENKINS-58463 Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" Change By: Sergio Merino Resolution: Duplicate Status: Resolved Reopened Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title He Bihong updated an issue Jenkins / JENKINS-58463 Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" Change By: He Bihong Environment: Plugin version: 1.16.3, Centos; Jenkins start with java ops: -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=2592000 Kubernetes: AWS EKS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200597.1562925236000.13517.1563334560152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title
He Bihong edited a comment on JENKINS-58463
Re: Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
The maxConcurrentRequests number 64 I mentioned in this class: io.fabric8.kubernetes.client.ConfigIt defined parameter maxConcurrentRequests and default value is 64, but not changed, even it provides setMaxConcurrentRequests method.It also not set in this class when init the Config: org.csanchez.jenkins.plugins.kubernetes.KubernetesFactoryAdapter, but set MaxConcurrentRequestsPerHost:{code:java}builder.withMaxConcurrentRequestsPerHost(maxRequestsPerHost);{code}Is it possible add a configure for maxConcurrentRequests maxRequests and set it here:{code:java}builder.withMaxConcurrentRequests(maxRequests);{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200597.1562925236000.13514.1563334020239%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title
He Bihong edited a comment on JENKINS-58463
Re: Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
The maxConcurrentRequests number 64 I mentioned in this class: io.fabric8.kubernetes.client.ConfigIt defined parameter maxConcurrentRequests and default value is 64, but not changed, even it provides setMaxConcurrentRequests method.It also not set in this class when init the Config: org.csanchez.jenkins.plugins.kubernetes.KubernetesFactoryAdapter, but set MaxConcurrentRequestsPerHost:{code:java}builder.withMaxConcurrentRequestsPerHost(maxRequestsPerHost);{code}Is it possible add a configure for maxConcurrentRequests and set it here:{code:java}builder.withMaxConcurrentRequests( maxRequestsPerHost maxRequests );{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200597.1562925236000.13512.1563334020212%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title He Bihong commented on JENKINS-58463 Re: Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" The maxConcurrentRequests number 64 I mentioned in this class: io.fabric8.kubernetes.client.Config It defined parameter maxConcurrentRequests and default value is 64, but not changed, even it provides setMaxConcurrentRequests method. It also not set in this class when init the Config: org.csanchez.jenkins.plugins.kubernetes.KubernetesFactoryAdapter, but set MaxConcurrentRequestsPerHost: builder.withMaxConcurrentRequestsPerHost(maxRequestsPerHost); Is it possible add a configure for maxConcurrentRequests and set it here: builder.withMaxConcurrentRequests(maxRequestsPerHost); Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200597.1562925236000.13508.156900165%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title Jesse Glick resolved as Duplicate Possibly a symptom of JENKINS-58290. Please ensure that you are running the latest plugin release before filing a bug report. Jenkins / JENKINS-58463 Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200597.1562925236000.12592.1563303960453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title Carlos Sanchez commented on JENKINS-58463 Re: Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" where do you see the hardcoded 64 number ? if you set the k8s cloud parameter max Requests Per Host to a value it will be used every time the client is recreated Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200597.1562925236000.8619.1562925900169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58463) Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API"
Title: Message Title He Bihong created an issue Jenkins / JENKINS-58463 Job build failed by "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API" Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-07-12 09:53 Environment: Plugin version: 1.16.3, Centos; Jenkins start with java ops: -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=2592000 Priority: Major Reporter: He Bihong Job will failed randomly by message "Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API". The metrics total requests reached 64 when the issue happen. It seems in Kubernetes-plugin codes, the k8s client maxRequests is set to 64 by hard code. No configuration can change it. This java parameter also can not change it: kubernetes.max.concurrent.requests. This issue will happen even set MaxConcurrentRequestsPerHost to a big number. Once change MaxConcurrentRequestsPerHost in jenkins, the issue will disappear some times, but will occur again after running for a period. It seems it due to that the k8s API client recreated when change the configuration. Is it possible add a configuration for k8s client maxRequests?
