I have two issues and I'm unsure if they are related:
Problem: After setting up a multiple collection Solrcloud 4.1 instance on
seven servers, when I index the documents they aren't distributed across
the index slices. It feels as though, I don't actually have a "cloud"
implementation, yet every
t; don't specify numShards it goes into a mode where it's up to you to
> distribute updates.
>
> - Mark
>
> On Mar 25, 2013, at 10:29 PM, Chris R wrote:
>
> > I have two issues and I'm unsure if they are related:
> >
> > Problem: After setting u
013 at 11:34 PM, Mark Miller wrote:
> I'm guessing you didn't specify numShards. Things changed in 4.1 - if you
> don't specify numShards it goes into a mode where it's up to you to
> distribute updates.
>
> - Mark
>
> On Mar 25, 2013, at 10:29 PM, Chris
node you fire the request at.
>
> Let us know if you index more docs and still see the problem.
>
> Best
> Erick
>
> On Wed, Mar 27, 2013 at 9:39 AM, Chris R wrote:
> > So - I must be missing something very basic here and I've gone back to
> the
> > Wik
in 4.2
> due to it's lack of result responses (you have to search the overseer
> logs). It's slightly better in 4.2 (you will get some response) and much
> better in 4.2.1 (you will get decent responses).
>
> Now that it's much more central, it will continue to improve rapi
So, upgraded to 4.2 this morning. I had gotten to the point where I okay
with the collection creation process in 4.1 using the API vice the solr.xml
file in 4.0, but now 4.2 doesn't seem to want to create the instanceDir?
e.g. the Dashboard reports the following when my solr.data.dir is set to
/d
d a
> nice home relative to the instance dir. If you don't do this, you won't be
> able to over shard, and things get tricky fast.
>
> - Mark
>
> On Mar 29, 2013, at 2:45 PM, Chris R wrote:
>
> > So, upgraded to 4.2 this morning. I had gotten to the point where
I've notice on the Admin UI that on some of my nodes that Core Selector
combo box doesn't populate. Known issue?
Chris
