On 16 February 2016 at 06:09, Midas A wrote:
> Susheel,
>
> Is there any client available in php for solr cloud which maintain the same
> ??
>
>
No there is none. I recommend HAProxy for Non SolrJ clients and
loadbalancing SolrCloud.
HAProxy makes it also easy to do rolling
Susheel,
Is there any client available in php for solr cloud which maintain the same
??
On Tue, Feb 16, 2016 at 7:31 AM, Susheel Kumar
wrote:
> In SolrJ, you would use CloudSolrClient which interacts with Zookeeper
> (which maintains Cluster State). See CloudSolrClient
In SolrJ, you would use CloudSolrClient which interacts with Zookeeper
(which maintains Cluster State). See CloudSolrClient API. So that's how
SolrJ would know which node is down or not.
Thanks,
Susheel
On Mon, Feb 15, 2016 at 12:07 AM, Midas A wrote:
> Erick,
>
> We are
Erick,
We are using php for our application so client would you suggest .
currently we are using pecl solr client .
but i want to understand that suppose we sent a request to a node and that
node is down that time how solrj figure out where request should go.
On Fri, Feb 12, 2016 at 9:44
bq: in case of solrcloud architecture we need not to have load balancer
First, my comment about a load balancer was for the master/slave
architecture where the load balancer points to the slaves.
Second, for SolrCloud you don't necessarily need a load balancer as
if you're using a SolrJ client
Erick ,
bq: We want the hits on solr servers to be distributed
True, this happens automatically in SolrCloud, but a simple load
balancer in front of master/slave does the same thing.
Midas : in case of solrcloud architecture we need not to have load balancer
? .
On Thu, Feb 11, 2016 at 11:42
bq: We want the hits on solr servers to be distributed
True, this happens automatically in SolrCloud, but a simple load
balancer in front of master/slave does the same thing.
bq: what if master node fail what should be our fail over strategy ?
This is, indeed one of the advantages for
What exactly is your motivation? I mean, the primary benefit of SolrCloud
is better support for sharding, and you have only a single shard. If you
have no need for sharding and your master-slave replicated Solr has been
working fine, then stick with it. If only one machine is having a load
hi,
what if master node fail what should be our fail over strategy ?
On Wed, Feb 10, 2016 at 9:12 PM, Jack Krupansky
wrote:
> What exactly is your motivation? I mean, the primary benefit of SolrCloud
> is better support for sharding, and you have only a single shard.
@Jack
Currently we have around 55,00,000 docs
Its not about load on one node we have load on different nodes at different
times as our traffic is huge around 60k users at a given point of time
We want the hits on solr servers to be distributed so we are planning to
move on solr cloud as it
Hi,
We are currently using solr 5.2 and I need to move on solr cloud
architecture.
As of now we are using 5 machines :
1. I am using 1 master where we are indexing ourdata.
2. I replicate my data on other machines
One or the other machine keeps on showing high load so I am planning to
move on
What is the size of your index, hardware specs, average query load, rate of
Indexing?
On Wed, 10 Feb 2016, 14:14 kshitij tyagi
wrote:
> Hi,
>
> We are currently using solr 5.2 and I need to move on solr cloud
> architecture.
>
> As of now we are using 5 machines :
>
12 matches
Mail list logo