re: Solr admin console. Hmmm, switch it to a different node? It gets you the same info no matter which node you're pointing at in your SolrCloud....
Not sure why this happens though. Best, Erick On Sat, Nov 8, 2014 at 10:12 AM, Michal Krajňanský <michal.krajnan...@gmail.com> wrote: > Hi Erick, > > I found the issue to be related to my other question (about shared > solrconfig.xml) which you also answered. > > Turns out that I had set data.dir variable in solrconfig.xml to an absolute > path that coincided with a different index. So replica tried to be created > there and something nasty probably happened. When removed the variable > value, the replica starts to be created where expected (and appropriatelly > grows in size). > > During this recovery process (copying 60GB of data), the Solr Admin console > is unusable however. Anything I could do about this? > > Thank you a lot, > > > Michal > > 2014-11-07 20:16 GMT+01:00 Erick Erickson <erickerick...@gmail.com>: > >> How did you create the replica? Does the admin screen show it >> attached to the proper shard? >> >> What I'd do is set up my SolrCloud instance with (presumably) >> a single node (leader) and insure my searches were working. >> Then (and only then) use the Collection API ADDREPLICA >> command. You should see your replica be updated and >> be good-to-go >> >> Best, >> Erick >> >> On Fri, Nov 7, 2014 at 9:13 AM, Michal Krajňanský >> <michal.krajnan...@gmail.com> wrote: >> > Hi all, >> > >> > >> > I have a Solrcloud setup with a manually created collection with the >> index >> > obtained via other means than Solr (data come from Lucene). >> > >> > I created a replica for the index and expected to see the data being >> copied >> > to the replica, which does not happen. In the Admin interface I see >> > something like: >> > >> > >> > Version Gen Size Master (Searching) >> > 1415379668601 >> > 5853288 >> > 60.13 GB >> > Master (Replicable) >> > 1415379668601 >> > 5853288 >> > - >> > Slave (Searching) >> > 1415379668601 >> > 3 >> > 1.84 KB >> > >> > The versions seem to match. But obviously the replica only contains a >> > handful of documents I indexed AFTER the replica was created. >> > >> > How do I replicate the documents that were already in the index? Or am I >> > missing something? >> > >> > Best, >> > >> > >> > Michal Krajnansky >>
