Reports Manager

The Reports Manager fetches the fsimage from the NameNode at regular intervals. It reads the fsimage and creates a Lucene index for it. To improve the indexing performance, Cloudera recommends provisioning a host as powerful as possible and dedicating an SSD disk to the Reports Manager.

Table 1. Reports Manager
Component	Java Heap	CPU	Disk
Reports Manager	The recommended value is (4 * FsImage size + 2 GB) * x, where (1 < x <= 4). For Example: For a 20 GB FsImage size; this means 82 GB to 328 GB. important This release supports calculating directory size with snapshots included, which increases the required Java heap size by up to four times compared to earlier releases. Check the JVM Heap Memory Usage chart for Reports Manager, and increase the heap size until it no longer shows consistently high usage. Newer releases add a feature flag that you can use to disable the memory-intensive calculation.	Minimum: 8 cores Recommended: 16 cores (32 cores, with hyperthreading enabled.)	1 dedicated disk that is at least 20 times the size of the fsimage. Cloudera strongly recommends using SSD disks.