Hi, Solr and zookeeper both require a lot of I/O operations and in this case, there will an issue where solr is delaying the zookeeper write operation. So, it is recommended to have external zookeeper ensemble. Please refer below link for more details.
"ZooKeeper's design assumes that it has extremely fast access to its database. If the ZooKeeper database is stored on the same disks that hold the Solr data, any performance problems with Solr will delay ZooKeeper's access to its own database. This can lead to a performance death spiral where each ZK timeout results in recovery operations which cause further timeouts. ZooKeeper holds its database in Java heap memory, so disk read performance isn't quite as critical as disk write performance. In situations where the OS disk cache is too small for Solr's needs and the ZK database is on the same disk as Solr data, a large amount of disk access for Solr can interfere with ZK writes. Using very fast disks for ZK (SSD in particular) will result in good performance. Using separate physical disks for Solr and ZK data is strongly recommended. Having dedicated machines for all ZK nodes (a minimum of three nodes are required for redundancy) is even better, but not strictly a requirement." https://wiki.apache.org/solr/SolrPerformanceProblems Regards, Aniket S. Khare On Wed, May 30, 2018 at 10:57 AM, solr2020 <psgoms...@gmail.com> wrote: > Hi, > > What is the pros and cons of having Zookeeper instance and Solr instance in > the same VM/Server in production environment? > > Thanks. > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html > -- Regards, Aniket S. Khare
