Member since
01-08-2018
133
Posts
31
Kudos Received
21
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
17285 | 07-18-2018 01:29 AM | |
3096 | 06-26-2018 06:21 AM | |
5245 | 06-26-2018 04:33 AM | |
2706 | 06-21-2018 07:48 AM | |
2231 | 05-04-2018 04:04 AM |
03-14-2018
09:15 AM
Check this out https://www.cloudera.com/documentation/enterprise/5-13-x/topics/cm_ig_create_local_package_repo.html#concept_qqw_ww3_gp It allows you to create a temporary repository without installing any software. Suppose that you have python installed.
... View more
03-13-2018
04:30 AM
Solved, The DNS entry was wrong ... solrs.mydomain was a CNAME and not a A Record. Thanks again for your help!
... View more
03-09-2018
06:26 AM
2 Kudos
What is the meaning of having kafka-sentry, when you don't have kerberos enabled? For the moment, Kerberos is the only authentication engine supported by Kafka. When you don't have Kerberos enabled, all connection are treated the same. As you can see from the log, it thinks that the username is ANONYMOUS, that's why it tries to find the group that this user belongs to. Since, the local system is not aware of any user (either local or synced to an LDAP/AD) with the name "ANONYMOUS", there is no group retrieved, so it cannot be matched to any kafka-sentry rule. It is normal that it will fail. Of course, you can create a user account "ANONYMOUS", assign it to a group and define a kafka-sentry rule with this group. But what is the meaning to that? All connections will have the same permissions.
... View more
03-05-2018
01:04 AM
Yes. I've end-up using impersonate user following this article http://gethue.com/ldap-or-pam-pass-through-authentication-with-hive-or-impala/ and plus <property> <name>hadoop.proxyuser.hue_hive.groups</name> <value>*</value> </property> on core-site.xml by this answer http://community.cloudera.com/t5/Web-UI-Hue-Beeswax/Failed-to-validate-proxy-privilege-of-hue-hive-for-administrator/m-p/49742
... View more
03-04-2018
09:57 AM
@GeKas I had tried delete but the limitation is it only supports on ORC file format . (Cloudera says its not production ready) . But in one of our lower enviroment we are using without any issue until now. Should have mentioned about the limitation that comes with. appreciate your pointer 🙂
... View more
03-02-2018
01:10 PM
The second error is normal. You are using the HiveServer1 driver to connect to HiveServer2, that's why it is failing. According to your beeline command, you have HS2. You need the following URL jdbc:hive2://localhost:10000;AuthMech=0;transportMode=binary with Class.forName("com.cloudera.hive.jdbc4.HS2Driver"); UID is not required, but you can provide it. Since you don't have LDAP configured, you definitelly don't have to set password.
... View more
03-02-2018
05:20 AM
1 Kudo
"History and Rollback" is only available on Cloudera Enterprise. If you have Cloudera express then you should not see it.
... View more
02-28-2018
02:30 AM
You are right. It is not a good idea to start messing with these files. Plus these files are temporary, meaning if you reboot the server, will be lost. These directories are automatically created by cloudera agent with the name of 'Auto-increment'-'service'-'roletype'. Eg. 1000-hdfs-NAMENODE 1001-yarn-NODEMANAGER The cloudera agent will retrieve this information from Cloudera Manager server. There is no permanent local storage for configuration files. Any such configuration change should be done using Cloudera Manager. But if (for whatever reason) you need to do it, then yes you can kill it. Cloudera agent does not rely on communication with Cloudera Manager to do the automatic restart. And since there this restart is not issued by Cloudera Manager, it will restart the service on the same "/var/run/cloudera-scm-agent/process/service_dir" directory. If the command restart comes from the Cloudera Manager, then a new folder is created. You should be carefull because this changes should be pushed to CM. If not, on a service restart by CM those changes will be lost.
... View more
- « Previous
- Next »