Member since
02-23-2018
108
Posts
12
Kudos Received
9
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1264 | 04-11-2019 12:32 AM | |
2080 | 03-28-2019 04:14 AM | |
1393 | 01-22-2019 12:20 AM | |
1668 | 09-25-2018 03:26 AM | |
3485 | 09-14-2018 04:58 AM |
03-28-2019
08:51 AM
Instructions for changing hostnames are provided in the Changing Hostnames documentation chapter. For CM server the hostname change should be trivial and working fine afterwards. Is your CM TLS enabled? Do you get any error message when connecting to the CM web UI? The CM server logs as asked by @manuroman will reveal if there is an issue.
... View more
02-12-2019
10:03 AM
Hi @Tulasi, Greate to hear the issue got resolved! I will report internally on this to our documentation team to see how we can improve on it. Thanks, Li
... View more
01-22-2019
12:20 AM
1 Kudo
Hi, @Vinn Yes, only will have a error if any service try to write them. But inmediatly this will create a new log file. Regards, Manu.
... View more
10-04-2018
03:09 AM
This is resolved. Solution was that last segment is the file and will be created automatically. It should not be created as dir.
... View more
10-01-2018
08:52 AM
1 Kudo
@Nishikant, yes, when testing on a limited-resource VM, I shut down anything I don't need. Still, with limited resources, don't expect awesome performance. If you are using YARN, that spins up containers that will require memory as well. If you have Cloudera Manager installed, it is what you use to start and stop all hadoop roles. You may also need to configure heap space in Cloudera Manager to reduce the heap to ensure you don't overcommit.
... View more
09-25-2018
03:26 AM
Hi @josemg, I am in the same situation, but you have available both version. In HUE UI, in the user tab (right top) yo can select "change to the newest version" Regards, Manu.
... View more
09-25-2018
12:36 AM
@mmm286- in-case your issue is resolved , could you please kindly update the details and mark as solved
... 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