Hi @basha4 ,    Thanks for the update! Great to know the issue got resolved. Please help to mark this as resolved thread.   Cheers, Li ... View more

Hi @Amn_468 ,   Please check this documentation on how to plan storage space for Cloudera Management Services: https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ig_reqs_space.html   And documentation on SMON and HMON: https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ig_storage.html#data_storage The minimum size is a sum of 12GB for /var/lib/cloudera-service-monitor/ and an additional 10GB for /var/lib/cloudera-host-monitor/, it's not supported to set up less space than that. A metrics storage below 10 GB is not tested, and could cause issues with monitoring and alerts.   Here are some details information: 1. Eventserver (/var/lib/cloudera-scm-eventserver): The amount of storage space the Event Server uses is influenced by configuring how many discrete events it can retain. To configure data retention in Cloudera Manager Administration Console, Go the Cloudera Management Service. Click the Configuration tab. Select Scope > Event Server or Cloudera Management Service (Service-Wide). Select Category > Main. Edit the following property: Maximum Number of Events in the Event Server Store The maximum size of the Event Server store, in events. When this size is exceeded, events are deleted starting with the oldest first until the size of the store is below this threshold   2. Reports Manager (/var/lib/cloudera-scm-headlamp): Reports Manager downloads the fsimage from the NameNode (every 60 minutes by default) and stores it locally to perform operations against, including indexing the HDFS filesystem structure. More files and directories results in a larger fsimage, which consumes more disk space. Reports Manager has no control over the size of the fsimage. If your total HDFS usage trends upward notably or you add excessively long paths in HDFS, it might be necessary to revisit and adjust the amount of local storage allocated to the Reports Manager. Periodically monitor, review, and adjust the local storage allocation. 3. Service Monitor: 10GiB Services Time Series Storage + 1GiB Impala Query Storage + 1GiB YARN Application Storage =================== ~12GiB Minimum / No Maximum The amount of storage space the Service Monitor uses is influenced by configuring how many hours|days worth of data it is configured retain. Find these properties at Cloudera Manager UI Home > Cloudera Management Service > Configuration > Scope > Service Monitor: - Time-Series Storage (firehose_time_series_storage_bytes) - Impala Storage (firehose_impala_storage_bytes) - YARN Storage (firehose_yarn_storage_bytes) 4. Host Monitor: Host Monitor data growth is controlled by configuring a maximum amount of storage space it may use. Find these properties at Cloudera Manager UI Home > Cloudera Management Service > Configuration > Scope > Host Monitor: Time-Series Storage (firehose_time_series_storage_bytes) (Default + Minimum: 10GiB Host Time Series Storage)   Thanks and hope this helps, Li ... View more

Hi @Raja723 ,   Could you please share a screenshot for us to see which step you were asked to enter database name and table name? Please use the Add a Role wizard to add the Reports Manager role. During the step, it should ask you the database host, database type, database name and username/password. As long as you specify the values correctly, the wizard should do a database connection and create the necessary tables in the database for you automatically. Please make sure you follow the documentation to create the database first and make sure that CM server can make successful connection to the RMAN database. Here is the documentation for Mysql: https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ig_mysql.html#mysql_configure_cm_db   Thanks and hope this helps, Li ... View more

Hi @Ma ,   Please check this community thread in regarding to Cloudera Manager 6.1 Express functionality change: https://community.cloudera.com/t5/Product-Announcements/ANNOUNCE-Cloudera-Manager-6-1-Express-functionality-change/td-p/84180   In short, from Cloudera Enterprise 6.1 and higher, we are limiting Cloudera Express customers using both CM6 and CDH6 to a maximum of 100 deployable nodes across all of their environments.   Thanks and hope this answers your question. Li   ... View more