Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

propagate user-set Spark configurations to the driver pod #5

Merged
merged 1 commit into from Nov 21, 2016

Conversation

erikerlandson
Copy link
Collaborator

@erikerlandson erikerlandson commented Nov 16, 2016

Adding logic to propagate all user-configured settings to the driver running in the cluster. As a corollary, all of the dynamic executor configuration parameters are passed along, and so dynamic executor behavior is now fully configurable:
http://spark.apache.org/docs/latest/configuration.html#dynamic-allocation

Use spark image: manyangled/kube-spark:dynamic

@erikerlandson
Copy link
Collaborator Author

Annotate this as associated with kubernetes/kubernetes#34377

@foxish
Copy link
Owner

foxish commented Nov 21, 2016

Merging. Thanks @erikerlandson.

@foxish foxish merged commit 1eb6751 into foxish:k8s-support Nov 21, 2016
s"--conf spark.executor.jar=$clientJarUri")

submitArgs ++= conf.getAll.filter { case (name, _) => !confBlackList.contains(name) }
.map { case (name, value) => s"--conf ${name}=${value}" }

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @erikerlandson and @foxish

Thanks for writing this change! I was looking at this because it would fix an issue I was having.

But it seems that line 113-114 appending to submitArgs are missing in the latest revision of KubernetesClusterScheduler.scala. I wonder if they were intentionally removed?

Thanks,
Kimoon

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It must have been omitted in one of the commits. I will add the change in my next commit.
Thanks for pointing that out.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @iyanuobidele,

That makes sense. Thanks for fixing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants