Member since
02-15-2016
113
Posts
7
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
8486 | 07-11-2017 08:10 AM | |
3895 | 03-07-2016 03:03 PM |
04-16-2018
12:16 PM
Hi ,
I have configured impala with haproxy for load balancing ,also impala is configured with ldap .
but i am not able to connect impala using ldap .
this is haproxy ==> allwcc9hddn01.prod.com:21051
beeline> !connect "jdbc:hive2://allwcc9hddn01.prod.com:21051/default;user=abcd;password=abcd" Connecting to jdbc:hive2://allwcc9hddn01.prod.com:21051/default;user=abcd;password=abcd Unexpected end of file when reading from HS2 server. The root cause might be too many concurrent connections. Please ask the administrator to check the number of active connections, and adjust hive.server2.thrift.max.worker.threads if applicable. Error: Could not open client transport with JDBC Uri: jdbc:hive2://allwcc9hddn01.prod.com:21051/default;user=abcd;password=abcd: null (state=08S01,code=0)
whereas kerberos works fine . what could be the reason ?
... View more
Labels:
- Labels:
-
Apache Hive
-
Apache Impala
-
Kerberos
04-16-2018
12:11 PM
user mapred:hadoop for logs in /tmp
... View more
04-02-2018
08:41 AM
Hi , do we have a coomand to check kudu table size. like hive and hbase table we can check size on hdfs . do we have similar thing for kudu
... View more
Labels:
- Labels:
-
Apache Kudu
03-11-2018
10:21 PM
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
02-06-2018
09:44 AM
Hi , Is there any probnlem in 5.14 mirror ,dwonload are getting fail frequently https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.14.0/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 503" Trying other mirror. Is this ok [y/N]: y Downloading Packages: https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.14.0/RPMS/x86_64/cloudera-manager-daemons-5.14.0-1.cm5140.p0.25.el6.x86_64.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 503" Trying other mirror. Error Downloading Packages: cloudera-manager-daemons-5.14.0-1.cm5140.p0.25.el6.x86_64: failure: RPMS/x86_64/cloudera-manager-daemons-5.14.0-1.cm5140.p0.25.el6.x86_64.rpm from cloudera-manager: [Errno 256] No more mirrors to try.
... View more
Labels:
- Labels:
-
Cloudera Manager
-
Manual Installation
07-11-2017
10:20 AM
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
07-11-2017
08:10 AM
What port cdsw web url run? # # This domain for DNS and is unrelated to Kerberos or LDAP domains. DOMAIN="cdsw.company.com" # IPv4 address for the master node that is reachable from the worker nodes. # # Within an AWS VPC, MASTER_IP should be set to the internal IP # of the master node; for instance, "10.251.50.12" corresponding to # master node name of ip-10-251-50-12.ec2.internal. MASTER_IP="10.11.140.64" DOMAIN="cdsw.company.com shall i put my company domain like cdsw.test.com or just test.com
... View more
07-10-2017
08:51 PM
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
07-10-2017
06:41 PM
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
07-10-2017
02:32 PM
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