You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to programmatically spin up an EMR cluster then spin up a Dask cluster in the EMR cluster with YarnCluster construct.
Currently, what we are doing is - open up SSH tunnel to the master node of the EMR cluster (it's in private subnet), log onto the master node, create a .ipynb notebook that has "YarnCluster(..)" code. We execute that cell to spin up the Dask cluster.
It would be nice to automate this; e.g. run some commands to spin up an EMR cluster that also has Dask cluster.
Thanks!
The text was updated successfully, but these errors were encountered:
jennakwon06
changed the title
Start a Dask cluster with EMR cluster "step"?
Start a Dask cluster with EMR cluster programmatically
Jun 25, 2020
So yes - we are programatically launching an EMR cluster with boto EMR api.
But the manual step is - when EMR cluster is done launching (takes ~5 minutes), log onto the master node of the EMR cluster then run a Jupyter notebook with cell "cluster = YarnCluster(...)".
We then do "Client("ip-node-of-emr-master-node")" to connect to the YarnCluster from somewhere different than EMR master node - like a Jupyter notebook on a SageMaker notebook instance.
So the ideal is - from my SM notebook instance, I can do one call "spin-up-dask-cluster-on-emr-cluster(dask_cluster_settings, emr_cluster_settings)".
Hello,
We want to programmatically spin up an EMR cluster then spin up a Dask cluster in the EMR cluster with YarnCluster construct.
Currently, what we are doing is - open up SSH tunnel to the master node of the EMR cluster (it's in private subnet), log onto the master node, create a .ipynb notebook that has "YarnCluster(..)" code. We execute that cell to spin up the Dask cluster.
It would be nice to automate this; e.g. run some commands to spin up an EMR cluster that also has Dask cluster.
Thanks!
The text was updated successfully, but these errors were encountered: