Member since
04-22-2014
1218
Posts
341
Kudos Received
157
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
21162 | 03-03-2020 08:12 AM | |
12072 | 02-28-2020 10:43 AM | |
3509 | 12-16-2019 12:59 PM | |
3025 | 11-12-2019 03:28 PM | |
4831 | 11-01-2019 09:01 AM |
09-17-2018
09:38 AM
@sid2707, Sounds like you may need to add some debugging to your shell script to identify what values are being evaluated and why no results are being returned.
... View more
09-14-2018
05:57 PM
@desind, No limit that I know of on the CM side. Please start a new thread and provide your LDAP configuration, what happens in the logs and also the "abc_efg_scd_dfc" user LDIF entry. There are lots of reasons for failures, so it is important we start with what you observe and the items involved.
... View more
09-14-2018
05:42 PM
@pollard, Are any of your services running? Maybe provide a screen shot of Cloudera Manager's home page and also the hosts page. "Could not connect to quickstart.cloudera:21050" means that Hue cannot connect to the impala daemon so make sure that it is running and listening on port 21050
... View more
09-14-2018
09:25 AM
@TomasTF, (1) Service Monitor will pull query information from the Impala Daemons so first make sure that Service Monitor is not having trouble getting information after the queries complete. View: /var/log/cloudera-scm-firehose/mgmt-cmf-mgmt-SERVICEMONITOR-`hostname -f`.log.out (2) When you query Impala queries via Cloudera Manager, Cloudera Manager will request query information from Service Monitor. So, check Cloudera Manager and Service Monitor logs for any log messages that may be relevant when you are trying to view queries: /var/log/cloudera-scm-firehose/mgmt-cmf-mgmt-SERVICEMONITOR-`hostname -f`.log.out /var/log/cloudera-scm-server/cloudera-scm-server.log (3) Make sure you have enough disk space on the volume where your Service Monitor Storage Directory is located. (4) Lastly, if there are no messages that indicate problems with the above, try increasing Impala Storage from 1GiB to 2 or 3 GiB. Perhaps for some reason you were running out of space, but I don't think that is too likely. Worth a try if nothing else mentioned above gives you any clues.
... View more
09-13-2018
12:15 PM
Hi @Paulina, Sentry will use OS group lookup to resolve group membership. Are you using OS level configuration that maps to LDAP users? Also, being an Admin does not grant any access to servers; rather, it gives grant privlige. What we really need to do is clearly define what you have configured in terms of grants and user/group membership so we can start to clarify what you expect to have happen and what is actually happening. - is the grants you have made that you perceive are not having the desired effect - the result of "id -Gn <user>" - groups that are listed as Sentry Admin Groups - test results with beeline (to remove the level of abstraction introduced by Hue).
... View more
09-06-2018
03:38 PM
@Krish216, The solution has been applied many times, so it is most likely that a minor mistake was made. How did you add the CM certificate to the /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem file? What exactly did you add? How did you get that text? PEM files can be very sensitive to missing "-" in the headers of certificates. also, it could be possible you copied/pasted and some extra characters got in there... Try running: openssl s_client -connect <cm_host>:7183 -CAfile /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem < /dev/null If openssl connects without a problem, your agent on the same host should too. Make sure you have restarted the agent after making the pem file update: # service cloudera-scm-agent restart
... View more
09-06-2018
09:49 AM
1 Kudo
@Makrand, Do you need to have Cloudera Manager 5.13.1 or are you mainly concerned about having CDH 5.13.1? If you just want CDH 5.13.1, It is fine to have Cloudera Manager 5.15.1 manage it. In Cloudera Manager, to got Administration --> Settings --> Parcels Add the following in Remote Parcel Repository URLs: https://archive.cloudera.com/cdh5/parcels/5.13.1/ Save and then navigate to Hosts --> Parcels Click the Check for new Parcels button You should now see the CDH 5.13.1 parcel is available for download.
... View more
09-06-2018
09:14 AM
@Paulina, If you want Hue to authenticate to Hive via LDAP, you need to make sure you have configured the username and password of an LDAP user hue can use for auth: [beeswax] auth_username=hue auth_password=<hue_password> The above assumes you have a user named "hue" in your ldap server who can authenticate. You would add this to Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini If you want to use kerberos for Hue to authenticate, then do the following: (1) In CM > Hive > Configuration > Advanced > Hive Client Advanced Configuration Snippet (Safety Valve) for hive-site.xml Name: hive.server2.authentication Value: kerberos (2) Save (3) Restart Hue Service Reason: Hue picks up its Hive authentication method from the hive-site.xml that is emitted. If you enable LDAP authentication in Hive, the hive.server2.authentication becomes LDAP which Hue will then try to use. To tell Hue to use kerberos, you can use the above technique.
... View more
09-05-2018
03:12 PM
1 Kudo
@willschlemmel, I checked the code and it seems that you are correct and this truncation was by design. The API calls you are making are also used internally to return search results for Impala Queries in Cloudera Manager's UI. When the queries got long, this hurt Cloudera Manager performance, so the decision was made to truncate the query string at 10000 characters. You can get the full query string by looking at that query itself. I think the idea for the Python API is that you would return the list of queries and then call get_query_details(self, query_id, format='text') to get the details if you want to see the full query. If you want to, you can try adjusting an internal configuration value in Cloudera manager to verify that the limit you are hitting is indeed the one I've asserted. (1) Back up your /etc/default/cloudera-scm-server file (2) Edit that file and add the following to the CMF_JAVA_OPTS environment variable: -Dcom.cloudera.server.web.cmf.impala.components.ImpalaDao.IMPALA_SQL_STATEMENT_MAX_DISPLAY_LENGTH=20000 If you have not made any previous edits to the file, the result will look like this: export CMF_JAVA_OPTS="-Xmx2G -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Dcom.cloudera.server.web.cmf.impala.components.ImpalaDao.IMPALA_SQL_STATEMENT_MAX_DISPLAY_LENGTH=20000" (3) Restart Cloudera Manager with: # service cloudera-scm-server restart If you now see trucation at 20000 characters, it seems we have our cause. NOTE: this will also impact performance inside of Cloudera Manager's impala queries UI. Just be aware that this is not dangerous but a bit experimental, so use due caution if working on a production system. Another note is that you can adjsut the max display length as you desire, but it only takes integer values (which should be plenty big enough for most queries).
... View more
09-04-2018
04:08 PM
LOL... just checked the dates. It has been quite a while since Neta Je posted this (09-03-2015!) I just saw your response, @Koti_Karri and followed along ;-).
... View more