spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "shane knapp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-26997) k8s integration tests failing after client upgraded to 4.1.2
Date Wed, 27 Feb 2019 18:18:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-26997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779599#comment-16779599
] 

shane knapp commented on SPARK-26997:
-------------------------------------

i just confirmed that k8s 1.10.0 is definitely incompatible w/the 4.1.2 client.  testing
against [~vanzin]'s recent (and absolutely trivial) PR, i found that the integration tests
would fail w/his changes reverted (using 4.1.2), and passed with his changes testing against
4.1.0.

this means we need a minimum viable version of k8s to test against.  how do we choose? 
especially as it seems that backwards compatibility isn't "a thing".

putting on my build engineer hat:  i am extremely reluctant to tie spark testing infrastructure
deps directly to some magical process that follows k8s releases.  it also appears that slight
variations in local testing infrastructure (i use kvm2, [~vanzin] uses virtualbox, and [~skonto]
none at all) cause failures (or successes) in different, and spectacular ways.

and i think we might be going about creating the pods and containers to run these tests. 
it might be better to use yaml instead of setting a bunch of scala vars and hitting an api.

this is already proven to be an absolute nightmare to debug, and for all these exact reasons.

discuss.  :)

> k8s integration tests failing after client upgraded to 4.1.2
> ------------------------------------------------------------
>
>                 Key: SPARK-26997
>                 URL: https://issues.apache.org/jira/browse/SPARK-26997
>             Project: Spark
>          Issue Type: Bug
>          Components: Kubernetes
>    Affects Versions: 3.0.0
>            Reporter: Marcelo Vanzin
>            Priority: Critical
>
> SPARK-26742 upgraded the client libs to version 4.1.2, and that doesn't seem to agree
well with the minikube we're using in jenkins. My PRs are failing (minikube 0.25):
> {noformat}
> 19/02/25 17:46:52.599 ScalaTest-main-running-KubernetesSuite INFO ProcessUtils: 19/02/25
17:46:52 INFO ShutdownHookManager: Deleting directory /tmp/spark-3007689c-e3ca-48f5-a673-f3bad5c4774a
> 19/02/25 17:46:52.788 OkHttp https://192.168.39.69:8443/... ERROR ExecWebSocketListener:
Exec Failure: HTTP:500. Message:container not found ("spark-kubernetes-driver")
> java.net.ProtocolException: Expected HTTP 101 response but was '500 Internal Server Error'
> 	at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229)
> 	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196)
> 	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
> 	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)
> 19/02/25 17:46:52.999 OkHttp https://192.168.39.69:8443/... ERROR ExecWebSocketListener:
Exec Failure: HTTP:404. Message:404 page not found
> java.net.ProtocolException: Expected HTTP 101 response but was '404 Not Found'
> 	at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229)
> 	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196)
> 	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
> 	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)
> {noformat}
> Tests pass on my local minikube (0.34). Reverting that change makes them pass on jenkins
(see https://github.com/apache/spark/pull/23893).
> Not sure if this is a client bug or a compatibility issue.
> [~shaneknapp] [~skonto]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message