On 12/5/2015 3:21 PM, tedsolr wrote: > I'm running v5.2.1 on red hat linux. The "solr status" command is not > recognizing all my nodes. Consequently, "solr stop -all" only stops the node > on 8983. What's the recommended file structure for placing multiple nodes on > the same host? I am trying multiple "solr" folders within the same solr home > folder. With SOLRHOME/server/solr & SOLRHOME/server/solr2, what I get after > starting two nodes in cloud mode (with one embedded ZK) is a solr-8983.pid > file in SOLRHOME/bin & a solr-8984.pid file in SOLRHOME/server/solr2. > Doesn't seem right. Can I force PID files to all be in SOLRHOME/bin?
Most people will never have any need to run more than one SolrCloud instance per server once they move beyond the "-e cloud" example, which sets up multiple nodes on one machine because it's the only practical way to make that example work. There are valid reasons for multiple nodes per machine in production, but they mostly apply to extremely high-end hardware running very large indexes. For a more modest Solr install, the extra complexity is unnecessary and will most likely waste memory. One Solr instance can handle multiple indexes easily. If you really do need more than one node per server, then you definitely want separate solr home directories for each instance. If it were me and running only one Solr instance wasn't possible or practical for some reason, I would go with completely separate installs where each one has its own service name and solr home, so there are completely separate copies of all the install files and the startup script. This is the method outlined in the documentation page that Hoss gave you. Thanks, Shawn
