Khoi Pham

I see these lines in jobserver logs: ``` [2019-12-30 13:25:41,753] INFO .Cluster(akka://JobServer) [] [akka.cluster.Cluster(akka://JobServer)] - Cluster Node [akka.tcp://JobServer@spark-jobserver:7080] - Node [akka.tcp://[email protected]:35619] is JOINING, roles [manager] ... [2019-12-30 13:26:41,978] INFO AkkaClusterSupervisorActor...

Also I see this in driver's stdout: ``` [2019-12-30 13:25:42,761] WARN neAppClient$ClientEndpoint [] [akka://JobServer/user/jobManager-665fe58b-4a34-48ef-b5f0-b9d0b609cbf3] - Failed to connect to master spark-master-f784b584c-gwz7k:7077 ``` Is there anyway to tell driver to connect...

K8s does not support random port binding. Ideally each driver should run in it's own pod, not sharing the same pod as the spark worker. That way one could identify...

Actually if jobserver code for drivers sets the port to random then even k8s scheduler might not be able to help.

See this: https://github.com/kubernetes/kubernetes/issues/49792 Kubernetes only run containers and containers are ephemeral things and best practice dictate that it should only run one process. So they are more like processes less...

Yes. I think neither will work with jobserver for now. On Thu, Jan 2, 2020, 9:02 PM Behroz Sikander wrote: > ok so if I get you correct then you...

How did you overcome random port binding issue? Did you run jobserver and worker/driver on the same container? On Fri, Jan 3, 2020 at 10:23 AM Noorul Islam K M...

How about a simpler solution such as adding command `Go: Test -run` that display an input box where you can specify `-run` flag directly? That would work for all edge...

Except I never run tests on the command line anymore but mostly rely on "Go: Test Package" command. Sure I could run things on the command line but I also...

In the mean time, running mockgen in source mode is working pretty well for me.