Hi, Most of our clients/customers use local storage. Some use SSDs and some SANs, and those with extra cash use SANs with SSDs.
But what you wrote needs more detail because sources of poor performance can come from many places and there are a lot or very different setups out there that work in one situation but not in another. Otis Solr & ElasticSearch Support http://sematext.com/ On Mar 15, 2013 6:37 AM, "Christian von Wendt-Jensen" < christian.vonwendt-jen...@infopaq.com> wrote: > Hi, > > I want to find what your experiences are with different storage setups. > > We tried running a master/slave setup on the SAN but quickly realized that > the master did not index fast enough. We didn't run with soft commit though > – maybe that would change the conclusion? > The slaves seemed to run OK with data on the SAN, but as soon as > replication was enabled, it died. Replication took hours and drained > resources preventing good performance on the replicas. The cache warmup > time took forever. > > How does YOUR setup look like, and what storage solutions could YOU > recommend? SAN? Local disc? Local SSD? Softcommit? > > > > > > Med venlig hilsen / Best Regards > > Christian von Wendt-Jensen > IT Team Lead, Customer Solutions > > Infopaq International A/S > Kgs. Nytorv 22 > DK-1050 København K > > Phone +45 36 99 00 00 > Mobile +45 31 17 10 07 > Email christian.sonne.jen...@infopaq.com<mailto: > christian.sonne.jen...@infopaq.com> > Web www.infopaq.com<http://www.infopaq.com/> > > > > > > > > > DISCLAIMER: > This e-mail and accompanying documents contain privileged confidential > information. The information is intended only for the recipient(s) named. > Any unauthorised disclosure, copying, distribution, exploitation or the > taking of any action in reliance of the content of this e-mail is strictly > prohibited. If you have received this e-mail in error we would be obliged > if you would delete the e-mail and attachments and notify the dispatcher by > return e-mail or at +45 36 99 00 00 > P Please consider the environment before printing this mail note. >
