Hello @AzfarB    We hope the above Post has helped answer your concerns & offered an Action Plan to further review. We are marking the Post as Resolved for now. For any concerns, Feel free to post your ask in a Post & we shall get back to you accordingly.   Regards, Smarak ... View more

How did you create the impala_test principal? ... View more

Hi Rama, yes, you can configure that in the "Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini". OPSAPS-41615 is still open, in the future you can ask the status from any of your account team contacts. If you don't know who are those contacts, please ask/clarify that through the already open support case. Best regards,  Miklos ... View more

Today I ran into this same issue but the solutions in the post didn't resolve the problem.  I found each time you would start cloudera-scm-server (sudo systemctl start cloudera-scm-server) it would just add the entries back to the database we are instructed to delete.     The following did resolve the problem - Edit /var/lib/cloudera-scm-server/certmanager/cm_init.txt Change the following top 3 lines from true to false as follows. setsettings AGENT_TLS false setsettings WEB_TLS false setsettings NEED_AGENT_VALIDATION false   Then stop and start the cloudera-scm-server. This time you will see the entries back in the DB but they'll be set to false. On the database server you can run the following to confirm they are set to false now. select * from CONFIGS where ATTR='web_tls'; select * from CONFIGS where ATTR='agent_tls'; ... View more

If you execute "rmr /solr". you may encounter following authentication error. rmr /solr Authentication is not valid : /solr/security   To workaround this you can use skipACL option, which found in the following site. https://www.programmersought.com/article/60861634876/ Note: This is workaround steps in Cloudera Manager.    1. Zookeeper->Configration->java Configuration Options for Zookeeper Server Add -Dzookeeper.skipACL=yes 2. Restart the zookeeper service Remember to revert the change and restart zookeeper after you manage to remove /solr   rgds, Rama. ... View more

Hi @EricL ,   My cluster running on VM and it is sandbox and we are not expecting very high I/O throughput.   I created softlink parcel-cache into /opt/cloudera/parcels/parcel-cache as /opt/cloudera/parcels different mountpoint with /opt/cloudera/parcel-cache. I tested the mv statement complete instantaneously and parcel distribution phase completed.  This is just my workaround.    Hope cloudera can fix this issue so thread wait until the unpack and copy complete successfully before reading the parcel or have longer timeout or set it as configurable parameter.   Thank you very much for your help rgds, Rama. ... View more

SHORT Cloudera has broken zookeeper 3.4.5-cdh5.4.0 in several places. Service is working but CLI is dead. No workaround other than rollback. LONG Assign a bounty on this ;-). I have stepped on this mine too and was angry enough to find the reason: Zookeeper checks JLine during ZooKeeperMain.run(). There is a try-catch block that loads a number of classes. Any exception during class loading fails the whole block and JLine support is reported to be disabled. But here is why this happens with CDH 5.4.0: Current opensource Zookeeper-3.4.6 works against jline-0.9.94. Has no such issue. In CDH 5.4 Cloudera has applied the following patch: roman@node4:$ diff zookeeper-3.4.5-cdh5.3.3/src/java/main/org/apache/zookeeper/ZooKeeperMain.java zookeeper-3.4.5-cdh5.4.0/src/java/main/org/apache/zookeeper/ZooKeeperMain.java 305,306c305,306 < Class consoleC = Class.forName("jline.ConsoleReader"); < Class completorC = --- > Class consoleC = Class.forName("jline.ConsoleReader"); > Class completorC = 316,317c316,317 < Method addCompletor = consoleC.getMethod("addCompletor", < Class.forName("jline.Completor")); --- > Method addCompletor = consoleC.getMethod("addCompleter", > Class.forName("jline.console.completer.Completer")); CDH 5.4 uses jline-2.11.jar for ZooKeeper and it has no jline.ConsoleReader class (from 2.11 it is jline.console.ConsoleReader). Jline 0.9.94 in turn has no jline.console.completer.Completer. So there is incompatibility with any existing JLine. Any Cloudera CDH 5.4 user can run zookeeper-client on his/her cluster and find it does not work. Open-source zookeeper-3.4.6 depends on jline-0.9.94 which has no such patches. Don't know why Cloudera engineers have done such a mine. I see no clean way to fix it with 3.4.5-cdh5.4.0. I stayed with 3.4.5-cdh5.3.3 dependency where I need CLI and have production clusters. It seemed to me both jline-0.9.94.jar and jline.2.11.jar in classpath for zookeeper will fix the problem. But just have found Cloudera made another 'fix' in ZK for CDH 5.4.0, they have renamed org.apache.zookeeper.JLineZNodeCompletor class to org.apache.zookeeper.JLineZNodeCompleter. But here is the code from ZooKeeperMain.java Class<?> completorC = Class.forName("org.apache.zookeeper.JLineZNodeCompletor"); And of course, it means practically it is not possible to start ZK CLI in CDH 5.4.0 proper way. Awful work. 😞 ... View more

you could also resize the mountpoint if you think it is oversized.   sudo mount -o size=10G -o remount cm_processes. After I resize from 71GB to 10GB, I don't find any different in "free -h". So I feel the tmpfs doesn't really block the physical memory ahead.   Taken from following reference. http://man7.org/linux/man-pages/man5/tmpfs.5.html   rgds, Rama. ... View more