Hi There,   Thanks for reaching out on the community. I'm Josh, and I'll help address this for you.   log4j.properties: CM is the central point of configuration for services, so the short answer is that you should adjust log4j settings using safety valves. Below is an engineering blog post with a good description of how CM works. http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/ When a CM agent for a host heart beats to Cloudera Manager, Cloudera Manager sends back processes that should be running, and the related config files, one of which is the log4j.properties, for that service and role. From here, the CM agent makes a run time directory for these config files and references those. For instance, the agent will make a directory like the one bellow for a namenode role: /var/run/cloudera-scm-agent/process/879-hdfs-NAMENODE/ this is why editing config files in on the OS has no effect, and is not recommended.    Enabling audit logging: To enable audit logging for a service without navigator, you would want to set the appropriate log4j settings in the appropriate safety valve for that service. Let's use HDFS as an example. Cloudera Manager has a configuration property for HDFS labeled "NameNode Logging Advanced Configuration Snippet (Safety Valve)". This is the one you want to put your log4j settings in. Once you've put your settings in, it will insert those into the log4j.properties it sends over to the agent in heartbeats. The specifics for enabling vanilla hadoop HDFS audit logging can be found bellow: http://apprize.info/security/hadoop/7.html   Considering all of this info, bear in mind that Navigator takes care of all of this for you, as well as adding additional features. For instance, HDFS audit logs can be very bulky and cumbersome by themselves and include many operations that aren't very helpful from an auditing standpoint. Navigator is able to apply event filters to an audit log, store relevant audits, and index them for further searching. Therefore, I highly recommend enabling navigator when doing so becomes feasible.   Please let me know if you have any other questions. Cheers     ... View more

Hello, In CDH 5.8, queries can be exported from a user's home directory and imported to another users in JSON format. Steps bellow 1. Go to "my documents" on old user. (house icon) 2. Select the queries you would like to export. If they're in a folder, you can export the whole folder or use "cntrl click" to select multiple queries. Another option is to drag select them. 3. Click the "download" icon on the action bar at the top of the file browser. This will download the queries as a json file or multiple json files. 4. Log into the new account and go to "my documents" house icon. 5. Click the "upload" icon in the action bar. 6. Select a json file in the file browser. json files can only be uploaded one at a time. 7. Click import to finish the process. ... View more

Howdy,   Josh here, from Cloudera. Thanks for reaching out on this.   As far as verifying whether or not your outlined configuration would work, the short answer would be perhaps.   You might have already seen it, but I'll point to this blog post as a reference. It's a good read, and includes a matrix for deciding the specs for your cluster's nodes. If you look, you'll see the configuration you're proposing is in the neighborhood of a "Light Processing Configuration", but for every other configuration listed, it starts to fall short. As long as you don't make a fully stacked cluster with every service imaginable(it seems like you don't intend on doing that), the "Light Processing" config could suffice. You can also check out this other community post to get a better idea of how speccing your cluster could pan out in terms of how many nodes you would want.    So, in short, perhaps. Let me know if this helps or if you have any other questions.   Cheers, Josh ... View more