Member since
09-01-2014
23
Posts
0
Kudos Received
4
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1574 | 09-09-2014 02:16 AM | |
3372 | 09-08-2014 08:30 PM | |
1251 | 09-08-2014 04:23 AM | |
5795 | 09-05-2014 03:50 AM |
12-19-2018
03:59 PM
Hi Ben, But if we cannot find that file, what should we do? Why these files are missing? Thanks, Mo
... View more
09-09-2014
02:16 AM
Solved this issue. My problem was simple, My NodeManager log directory setting is not pointing to the container. yarn.nodemanager.log-dirs=/apps/ext/var/log/hadoop-yarn it was suppopsed to be yarn.nodemanager.log-dirs=/apps/ext/var/log/hadoop-yarn/container I figured it out after I see this message on my NodeManager web ui, under Node Log information, "NodeHealthReport 1/1 log-dirs turned bad" I was able to run and finish the PiEstimator after I update the log-dirs and restart the service.
... View more
09-08-2014
09:32 PM
Thank you for the feedback.
... View more
09-08-2014
08:15 PM
Nevermind, the log storage setting for HBase is available on CM. I didn't realilze those arrows next to category label can be expanded. And there will be 'Log' category which I can update the value.
... View more
09-08-2014
04:23 AM
Please disregard this post. Dumb post. I didn't realize those arrows for each category can be expanded, which gives me the ability to change the log directory. Sorry.
... View more
09-05-2014
07:47 AM
Glad you solved this! Keep in mind that when using the symlink, you may need to re-create it whenever you upgrade your cloudera-scm-server-db package in the future, since the symlink confuses the packaging code. Thanks, Darren
... View more
09-01-2014
11:20 PM
Thx! yeah it works. It's now writing to the cloudera-scm-server.log
... View more