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 seemingly innocent mistake will be hard to untangle. For your first question: "I wonder why the infos for the second replica are not shown..." the answer is that you are using a core-level API which does not "understand" anything about SolrCloud, it's all purely local to that instance. So it's doing exactly what you ask it to; reporting on the status of cores (replicas) _on that particular Solr instance_. The _Collections_ API _is_ cloud/Zookeeper aware and will report them all. What it does is fire the core-level command out to all live Solr nodes and assemble the response into a single cluster-wide report. Second, the core-level "replication" command is all about old-style master/slave index replication and I have no idea what it's reporting on when you ask for replication status in SolrCloud. It has nothing to do with, say, "replication factor" or anything else cloud related as Shawn indicates. Old-style master/slave is used in SolrCloud under the covers for "full sync", perhaps that's happened sometime (although ideally it won't happen at all unless something goes wrong with normal indexing and the only option is to copy the entire index from the leader). The take-away is that the replication command is probably not doing what you think it is. Best, Erick On Fri, Jun 29, 2018 at 7:47 AM, Arturas Mazeika <maze...@gmail.com> wrote: > 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 post). I wonder why.. > > Cheers, > Arturas > > On Fri, Jun 29, 2018 at 4:30 PM, Shawn Heisey <apa...@elyograg.org> wrote: > >> 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", >>> >>> "indexPath":"F:\\solr_server\\solr-7.2.1\\example\\cloud\\no >>> de4\\solr\\de_wiki_man_shard4_replica_n12\\data\\index/", >>> >>> I wonder why the infos for the second replica are not shown. Comments? >>> >> >> SolrCloud is aware of (and uses) the replication feature, but the >> replication feature is not cloud-aware. It is a core-level feature (not a >> cloud-specific feature) and is only aware of that one specific core (shard >> replica). This is not likely to ever change. >> >> Thanks, >> Shawn >> >>
