Either one will work, but on a long-running cluster where you rarely restart Yarn, set it to the FQDN of rm1, and also set rm1 to be the active RM. That's because the discovery of active RM is done in sequence rm1 --> rm2. ... View more

@dvt isoft Not necessarily. That would be only if your blocks will be 100% filled with data. Let's say you have a 1024 MB file and the block size is 128 MB. That would be exactly 8 blocks at 100%. Let's say you have 968 MB file and the block size is128 MB. That is still 8 blocks but with lower usage. A block once used by a file cannot be reused for a different file. That's why loading small files could be a waste. Just imagine 100 files of each 100 KB will be using 100 blocks for 128 MB, 10x more than the examples I provided above. You need to understand your files, block % usage etc. The command you execute shows the blocks empty x size/block ... I know that is confusing 🙂 +++ If this is helpful please vote and accept as the best answer. ... View more

@Bhavin Tandel I had a similar issue recently and while the Ambari YARN Queue Manager View doesn't offer a configurable URL, a workaround I found was to add the cluster as a Remote Cluster (using the alias URL when defining the Ambari Cluster URL) and then point the View to the remote cluster. This seemed to work just fine. ... View more