You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2021/10/26 07:50:00 UTC

[jira] [Updated] (SPARK-36890) Use default WebsocketPingInterval for Kubernetes watches

     [ https://issues.apache.org/jira/browse/SPARK-36890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun updated SPARK-36890:
----------------------------------
    Affects Version/s:     (was: 3.0.3)
                           (was: 3.1.2)
                           (was: 3.1.1)
                           (was: 3.0.2)
                           (was: 2.4.8)
                           (was: 2.4.7)
                           (was: 3.0.1)
                           (was: 2.4.6)
                           (was: 3.1.0)
                           (was: 2.4.5)
                           (was: 2.4.4)
                           (was: 2.4.3)
                           (was: 2.4.2)
                           (was: 2.3.4)
                           (was: 2.4.1)
                           (was: 2.3.3)
                           (was: 2.3.2)
                           (was: 2.3.1)
                           (was: 2.4.0)
                           (was: 2.3.0)
                           (was: 3.0.0)
                       3.3.0

> Use default WebsocketPingInterval for Kubernetes watches
> --------------------------------------------------------
>
>                 Key: SPARK-36890
>                 URL: https://issues.apache.org/jira/browse/SPARK-36890
>             Project: Spark
>          Issue Type: Improvement
>          Components: Kubernetes
>    Affects Versions: 3.3.0
>            Reporter: Philipp Dallig
>            Assignee: Philipp Dallig
>            Priority: Major
>             Fix For: 3.3.0
>
>
> If you access the Kubernetes API via a load balancer (e.g. HAProxy) and have set a tunnel timeout, the following error message is thrown exactly after each timeout.
> {code}
> >>> 21/09/27 15:35:19 WARN WatchConnectionManager: Exec Failure
> java.io.EOFException
>         at okio.RealBufferedSource.require(RealBufferedSource.java:61)
>         at okio.RealBufferedSource.readByte(RealBufferedSource.java:74)
>         at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117)
>         at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101)
>         at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
>         at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
>         at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203)
>         at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
> {code}
> This exception is quite annoying when working interactively with a paused pySpark shell where the driver component runs locally but the executors run in Kubernetes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org