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). For Example: For a 20 GB FsImage size; this means 4 * 20 GB + 2 GB = 82 GB. important Calculating directory size with snapshots included substantially increases the required Java heap size. If this feature is enabled using the Enable snapshot processing configuration parameter, check the JVM Heap Memory Usage chart for Reports Manager and increase the heap size until it no longer shows consistently high usage. Up to four times the above recommended value may be necessary.	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.