On Wed, Jan 10, 2018 at 1:33 PM, Matt Cheah <mch...@palantir.com> wrote: > If we use spark-submit in client mode from the driver container, how do we > handle needing to switch between a cluster-mode scheduler backend and a > client-mode scheduler backend in the future?
With a config value set by the submission code, like what I'm doing to prevent client mode submission in my p.o.c.? There are plenty of solutions to that problem if that's what's worrying you. > Something else re: client mode accessibility – if we make client mode > accessible to users even if it’s behind a flag, that’s a very different > contract from needing to recompile spark-submit to support client mode. The > amount of effort required from the user to get to client mode is very > different between the two cases Yes. But if we say we don't support client mode, we don't support client mode regardless of how easy it is for the user to fool Spark into trying to run in that mode. -- Marcelo --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
