Apoorva,
I was facing same problem few days back when i started useing
*CloudSolrServer*, it decreased my latency by almost 5 times than
HttpSolrServer .. below are few things i did for performance improvement.
+ Start using ConcurrentUpdateSolrServer
+ LB also choking the n/w in high tra
well, i have 8 m1.large ec2 having 2 core 7gb ram and 1tb ebs attached to each
server for index.
in my case i dont expect index to be store in ram neither a quick reply as its
not a real time application, i just want fault tolerance in application and
availability of full data.
Is it good to
Hi thanks for feedback erik.
What do you mean all the nodes in shards are down? i have 12 shards and i
suppose i have 12 nodes right? correct me if i am wrong.
Now whenever any one of them is down , say 1 down 11 active still i am getting
same error... is there any way to get results ignorin
