user mapred:hadoop for logs in /tmp ... View more

Looks like this is resloved in hadoop 2.8.0 ( not sure though)  check this ==.> https://github.com/minio/minio/issues/2965   only workaround i found is first load data without  encryption and then enable encryption  on file copied in S3 (manually) .    btw i have a general question . this SSE is to portect data in S3 only ,what about if someone with aws admin role download data to local disk ,its not more encrypted data    ... View more

  at first login it should ask username/password to create new account  but i am not getting that option .  i am gettinig login page . ... View more

ok after coiple of troubleshooting it moved and completed Cloudera Data Science Workbench is not ready yet: some system pods are not ready Master node configuration successful. The application may take up to 10 minutes to initially startup. To check application status use: $ watch cdsw status but Every 2.0s: cdsw status Mon Jul 10 23:49:23 2017 Cloudera Data Science Workbench Status Service Status docker: active kubelet: active nfs: active Checking kernel parameters... Node Status Cloudera Data Science Workbench is not ready yet: kubectl command failed [root@docker ~]# kubectl get pods --show-all NAME READY STATUS RESTARTS AGE cron-2934152315-mqsei 1/1 Running 0 20m db-39862959-2gt3u 1/1 Running 0 20m db-migrate-052787a-qhp19 0/1 Completed 0 20m engine-deps-xfrsh 1/1 Running 0 20m ingress-controller-3138093376-eacx8 1/1 Running 0 20m livelog-1900214889-e8oys 1/1 Running 0 20m reconciler-459456250-t057g 1/1 Running 0 20m spark-port-forwarder-guxvb 1/1 Running 0 20m web-3826671331-1fp2r 1/1 Running 0 20m web-3826671331-66myb 1/1 Running 0 20m web-3826671331-z8ark 1/1 Running 0 20m is it still downloading the images ? ... View more

ok , i have reset the cdsw and started again but this time it stuck with <master/pki> created keys and certificates in "/etc/kubernetes/pki" <util/kubeconfig> created "/etc/kubernetes/kubelet.conf" <util/kubeconfig> created "/etc/kubernetes/admin.conf" <master/apiclient> created API client configuration <master/apiclient> created API client, waiting for the control plane to become ready <master/apiclient> all control plane components are healthy after 18.555501 seconds <master/apiclient> waiting for at least one node to register and become ready. proxy i checked and looks ok. kubectl get pods does not return anything ... View more

It moved after changing proxy setting and now waiting in infinite loop <master/addons> created essential addon: kube-proxy <master/addons> created essential addon: kube-dns Kubernetes master initialised successfully! You can now join any number of machines by running the following on each node: kubeadm join --token=2a582a.63ec0427495ec31c 10.17.160.64 Added bootstrap token KUBE_TOKEN to /etc/cdsw/config/cdsw.conf node "docker.test.com" tainted daemonset "weave-net" created Waiting for kube-system cluster to come up. This could take a few minutes... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... Some pods in kube-system have not yet started. This may take a few minutes. Waiting for 10 seconds before checking again... ... View more