The suggested best practice is now to have a only single Dynamic SmartConnect Pool for NameNode and DataNode, not separate pools as in early documents.  [URL]  You would utilize a single pool per Access Zone as needed, Racks can then be used within pools to control client IP access to nodes also.  Everything Big Data at EMC
Each Isilon node acts as namenode/datanode. What is the purpose of having ip range pools namenode pool and datanode pool?  Could you please explain me this or point me to any technical documentation on this configuration? Thanks in advance. Ashok
ISILON hdfs question