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

Control of components' state #9

Closed
spark2ignite opened this issue Dec 2, 2015 · 4 comments
Closed

Control of components' state #9

spark2ignite opened this issue Dec 2, 2015 · 4 comments

Comments

@spark2ignite
Copy link

Right now, Dataproc deploys Hadoop, Spark, PySpark, SparkSQL, Hive and Pig among other things like HDFS. It would be great to have a AI script which will control the state of each component (on/off).

Some of us need only Spark working with Google Cloud Storage and having other components installed and running just wastes the resources of workers.

Maybe we should have a script with small "settings" section which will control which components we need to be ON and which are not necessary and turn them OFF

@spark2ignite spark2ignite changed the title Controlling components state Control of components' state Dec 2, 2015
@chimerasaurus
Copy link
Contributor

This suggestion makes sense. We'd probably want to control the individual daemons with the scripts. I am assuming you'd want the ability to set/unset specific packages/daemons to be on or off for the lifetime of the cluster, correct?

@spark2ignite
Copy link
Author

@evilsoapbox, that's correct!

@chimerasaurus
Copy link
Contributor

Hey @spark2ignite - We released an update today and I thought you might be interested based on this issue. We now allow you to set cluster properties to set XML and conf properties.

While it's not a direct answer to your issue, I thought you might find it interesting!

James

@spark2ignite
Copy link
Author

That's awesome, @evilsoapbox!

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

No branches or pull requests

2 participants