Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

Hello Zhangliang, For the more efficient tuning of the content repository archive you can use these pages (you might have already known them): https://community.cloudera.com/t5/Community-Articles/Understanding-how-NiFi-s-Content-Repository-Archiving-works/ta-p/249418 https://nifi.apache.org/docs/nifi-docs/html/nifi-in-depth.html#deeper-view-provenance-log-files also  1] - Add the following property from Ambari under nifi.properties section to a value of 75% nifi.content.repository.archive.backpressure.percentage to 75% 2] Increase the disk space. ... View more

 we have a couple of options here: 1- Basically we have a dedicated person assigned from the Cloudera Account team. 2- You can raise a support case from the Cloudera support portal and the support team will help you to get this done.   I hope this answers your queries 🙂  ... View more

Hello CDPTester,   Welcome to CDP :).    Could you please update us this is the Data lake or the Datahub? In legacy CDH we were having Administrator access on CM through which we were able to move the roles.   But in CDP we have removed the full admin access for users. You can create your own custom template for Data hubs as per the requirement.    Also, We have resize option through which you can the required nodes to the cluster.   Let us know if you have any further queries. ... View more

- I would request you to please check with the Account team for queries like this. - This type of request is generally taken care of by the account team, not by the support team.   Please let me know if you have any further queries. ... View more

Could you please attach the cm-server and cm-agent logs to it. ... View more

This could the possible solution, Please share the CM server logs 1) log into CM server host and take a backup file of /etc/default/cloudera-scm-server to a backup location 2) Open /etc/default/cloudera-scm-server file and add the following to the CMF_JAVA_OPTS: -Dlog4j.configurationFile=file:/etc/cloudera-scm-server/log4j2.properties With the above configuration, the file looks like this: [...] export CMF_JAVA_OPTS="[...existing...javaoptions] -Dlog4j.configurationFile=file:/etc/cloudera-scm-server/log4j2.properties" [...] 3) Create the /etc/cloudera-scm-server/log4j2.properties file. #chmod 644 /etc/cloudera-scm-server/log4j2.properties 4) We noticed some issues with the ODBC connector: #ls -ltr /usr/share/java/mysql-connector-java.jar *Not existing file 6) We copied the ODBC from a different environment. Cloudera Manager is able to start, but it is failing to connect to DB, We granted more connections in the db.properties file: #vi /etc/cloudera-scm-server/db.properties and add the below line in this file: > com.cloudera.cmf.orm.hibernate.c3p0.max_statements=0 < 7) After the restart, the CM server started successfully ... View more