title: How to setup Elasticsearch client nodes?
body: <p>I have couple of Elasticsearch questions regarding client node:</p>
  
  <ol>
  <li><p>Can I say: any nodes as long as they are opening HTTP port, I can treat them as "client" nodes, because we can do search/index through this node.</p></li>
  <li><p>Actually we treat the node as client node when the <code>cluster=false</code> and <code>data=false</code>, if I set up 10 client nodes, do I need to route in my client side, I mean if I specify <em>clientOne:9200</em> in my code as ES portal, then would <em>clientOne</em> forward other HTTP requests to other client nodes, otherwise, <em>clientOne</em> would be under very high pressure. i.e do they communicate with each other between client nodes?</p></li>
  <li><p>When I specify client nodes in ES cluster, should I close other nodes' HTTP port? Because we can only query client nodes.</p></li>
  <li><p>Do you think it's necessary to set up both data node and client node in the same machine, or just setup data node acts as client node as well, anyways it's  in the same machine?</p></li>
  <li><p>If the ES cluster would be heavily/frequently indexed while less searched, then I don't have to set up client node, because client node good for gathering data, right please?</p></li>
  <li><p>For general search/index purpose should I use http port or tcp port, what's the difference in clients perspective please?</p></li>
  </ol>