Service Monitor and Activity Monitor are the two heavy hitters. They both write to a TSDB on the local FS in a directory that you specify in the configs. I would split as I mentioned above: Host1: CM, DB, Amon, Rman Host2: Smon, Hmon, Event, Alert Service Monitor - resource usage dependent on the number of services being ran. It will grow as new nodes are added, as the new nodes will be running new services. Activity Monitor - Collection information on MR. Host monitor - Resource req. will depend on the number of hosts; will grow as new hosts are added. Reports Manager - Is all about the reports. This is usually light if only the pre-built reports are in place and generated. I have had to bump this up as the cluster usage and size grew. I haven't looked into it but it is likely because the reports run on a schedule even if they are not used. Event Server - Events can be generate out of any metrics or log entries. You can add more or more can be generated if they are triggered by changes to the system. Alert Publisher - Resource req. will depend on the number of alerts. This will grow with new hosts and services. More alerts can be added. ... View more

Activity Monitor and Reports Manager use a backend db to store their data. The rest use local directories. So these two are prime to be moved to a second host. You could move the others but you would have to manually migrate the data over. ... View more

CDH does not come with the Kafka parcel.  You need to add that seperately.  Check the list of available parcels.  If it is not present add the remote repo for CDH Kafka and check for new parcels.  If it is available, download, distribute, and activate.   From CM Add a Service Wizard:   "Apache Kafka is publish-subscribe messaging rethought as a distributed commit log. Before adding this service, ensure that either the Kafka parcel is activated or the Kafka package is installed." ... View more