Hi Shawn,
hi Erick,
hi et al.,
Very nice clarifications indeed. I also looked at the index replication
section. In addition to the clarifications in this thread this brought
quite some light into the area (and shows that I need to read solrcloud
part of the manual more extensively). Thanks a lot
On 6/29/2018 8:47 AM, Arturas Mazeika wrote:
Out of curiosity: some cores give infos for both shards (through
replication query) and some only for one (if you still be able to see the
prev post). I wonder why..
Adding to what Erick said:
If SolrCloud has initiated a replication on that core
Arturas:
Please make yourself a promise, "Only use the collections commands" ;)
At least for a while.
Trying to mix collection-level commands and core-level commands is
extremely confusing at the start. Under the covers, the Collections
API _uses_ the Core API, but in a very precise manner. Any
Hi Shawn et al,
Thanks a lot for the clarification. It makes a lot of sense and explains
which functionality needs to be used to get the infos :-).
Out of curiosity: some cores give infos for both shards (through
replication query) and some only for one (if you still be able to see the
prev
On 6/29/2018 7:53 AM, Arturas Mazeika wrote:
but the query reports infos on only one shard:
F:\solr_server\solr-7.2.1>curl -s
http://localhost:9996/solr/de_wiki_man/replication?command=details | grep
"indexPath\|indexSize"
"indexSize":"15.04 GB",
Hi Solr-Team,
I am benchmarking solr with the German Wikipedia pages on 4 nodes (Running
on ports , 9998, 9997 and 9996), 4 shards, replication factor 2):
"F:\solr_server\solr-7.2.1\bin\solr.cmd" start -m 3g -cloud -p -s
"F:\solr_server\solr-7.2.1\example\cloud\node1\solr"
