One way to get an index backup in Solr is through an HTTP call like this
http://localhost:8983/solr/replication?command=backup
I have 2 questions regarding this
1) Is there a way to get information on the progress of the backup
operation, much like the async param that was introduced in
4.8
I'm using Solr 4.7.2.
A few things I've missed follow. Before reaching the one leader-one failed
to recover state, the situation was no leader for the shard and both nodes
in recovery failed mode. A bit of tinkering to clusterstate.json forced
the one to be the leader but that didn't change a
SolrCloud configuration contains a single shard and 2 Solr servers, therefore
one acts as a leader and one as a replica.
Through a series of events(*) I've ended up with one Solr server being in
Active status and the leader of the shard while the other one in Recovery
failed status which cannot
Hi all,
In SolrCloud all nodes are equal in the sense that they can perform indexing
as well as searching.
Let's say a leader node is busy performing heavy-indexing, I wouldn't like
to also send search requests to that node. As far as I can tell from
CloudSolrServer source code, all it does when
Erick Erickson wrote
Back up, you're misunderstanding the update process. A leader node
distributes the update to every replica. So _all_ your nodes in a
slice are indexing when _any_ of them index. So the idea of sending
queries to just the replicas to avoid performance problems isn't
It seems that I've figured out a configuration approach to this issue.
I'm having the exact same issue and the only viable solutions found on the
net till now are
1) Pass -DnumShards=x when starting up Solr server
2) Use the Collections API as indicated by Shawn.
What I've noticed though - after
