I am putting the arguments in the "Arguments" field in the "Run Experiment" UI ... View more

@tristanzajoncsorry to bother you again.If i am am not wrong cloudera does not provide any sandbox for cdsw along with the CDH cluster. Because I have checked the cdh sandbox(5.13) and it only contains the cdh services not cdsw. If we add the cdsw service then it will create the port conflict and that was reason cloudera asked to install the cdsw in a different node.  Am i correct? ... View more

do you have a guide on how to setup a proper wildcard DNS entry?   I haven't worked with DNS servers before or looked at DNS configs ... View more

Could you share the logs ?  fire the below command .    cdsw logs ... View more

Environmental variables are currently set at runtime. You can override the defaults global in Admin > Engine panel or within a project in Settings > Environment. Best, Tristan ... View more

@tristanzajonc wrote: The <none> indicator is not an issue -- it simply indicates that those nodes are worker nodes and don't have stateful information stored on them.   Hanging engines on "ContainerCreating" typically means you have not run "cdsw enable <worker-ip>" on the master node for all your worker nodes.  This whitelists the IP of your worker nodes for NFS mounts.  If you have not done this, containers can hang waiting for the project mounts to become available when scheduled onto a worker node.   Please let me know if running "cdsw enable" for each worker IP resolves this issue.   Thanks, Tristan   FYI, i was having the same issue.  and this resolved it for me.    Thanks ... View more

proxy config options. option 1 both http_proxy and no_proxy blank ERROR: The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port? option 2 http_proxy =proxyserver:8080 and no_proxy ="127.0.0.1,localhost,10.masterIP,100.66.0.1,100.66.0.1/24" ERROR: The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port? option 3 http_proxy ="" and no_proxy ="127.0.0.1,localhost,10.masterIP,100.66.0.1,100.66.0.1/24" ERROR: new below error etcd-cdswserver.local 1/1 Running 0 22m 10.x.x.x cdswserver.local kube-apiserver-cdswserver.local 1/1 Running 0 21m 10.x.x.x cdswserver.local kube-controller-manager-cdswserver.local 1/1 Running 0 22m 10.x.x.x cdswserver.local kube-dns-3913472980-xtsrm 2/3 CrashLoopBackOff 15 22m 100.66.0.2 cdswserver.local kube-proxy-2fqts 1/1 Running 0 22m 10.x.x.x cdswserver.local kube-scheduler-cdswserver.local 1/1 Running 0 22m 10.x.x.x cdswserver.local weave-net-hd8pw 2/2 Running 0 22m 10.x.x.x cdswserver.local Cloudera Data Science Workbench Pod Status WARNING: Unable to bring up pods tagged as 'k8s-app' in the kube-system cluster. WARNING: Unable to bring up kube-system cluster.: 1 WARNING: Some pods in the CDSW application are not yet up.: 1 WARNING: Application services are incomplete WARNING: Config maps are incomplete WARNING: Secrets are incomplete WARNING: Persistent volumes are incomplete WARNING: Persistent volume claims are incomplete WARNING: Ingresses are incomplete WARNING: Unable to bring up pods tagged as 'k8s-app' in the kube-system cluster. ERROR:: Cloudera Data Science Workbench is not ready yet: some system pods are not ready: 1 [admin@cdswserver ~]$ sudo cdsw logs Generating Cloudera Data Science Workbench diagnostic bundle... Checking system basics... Saving kernel parameters... Getting the list of kernel modules Getting the list of systemd units Checking validation output... Checking application configuration... Checking disks... Checking Hadoop configuration... Checking network... Checking system services... Checking Docker... Checking Kubernetes... Checking Kubelet... Checking application services... Checking cluster info... Checking app cluster info... Exporting user ids... Error from server (NotFound): configmaps "internal-config" not found error: pod name must be specified Checking system logs... Producing logs tarball... ... View more

Thanks for your question.   Standalone R and Python jobs run only on the CDSW edge nodes where we have more control over dependency management using Docker.  However these jobs can push workloads into the cluster using tools like PySpark, Sparklyr, Impala, and Hive.  This allows you to get full dependency management for R and Python in the edge environment while still scaling specific workloads into the cluster.  There is not currently a way to run the R and Python jobs themselves under YARN.   In terms of SparkR, we recommend, but do not directly support, Sparklyr instead of SparkR.   I hope that is helpful. Tristan ... View more

Hi, A complete redo resolved it.  ... View more

The analyis.py file is meant to be run within the CDSW console, not directly from the terminal.  See the "Getting Started" guide within the CDSW documentation.  Within CDSW, Python consoles are backed by Jupyter kernels, which have the necessary configuration to create plots.   Best, Tristan ... View more

Thanks for the update.     >  Are you looking for support on a particular environment?   Yes, looking for Debian (Wheezy or Jessie) support. ... View more