@Balaji Vemula
After changing dfs.permissions.superusergroup in hdfs-site.xml, it would require a NameNode restart for the change to take effect. If this cluster uses NameNode HA with QuorumJournalManager, then both NameNodes need to be restarted.
Run "hdfs groups <username>", where <username> is the user that you have added to the group that you want to be the HDFS supergroup. This command will print out a list of that user's group memberships, as perceived by the NameNode. If the list does not show your configured supergroup, then this indicates there is some kind of misconfiguration
From the root CLI switch user to user balu
# su - balu
Now at the prompt you should be able to run hdfs command as user balu
$ hdfs dfsadmin -printTopology
That should work even on your cloudera