That means that documents will be indexed and stored on the node
they're sent to. It shouldn't keep Solr Cloud from loadbalancing
reads. Fixing that won't address the problem you're asking about, but
it may clear up other unintended behaviors.
What version of Solr are you using, and what servlet container?
Michael Della Bitta
------------------------------------------------
Appinions
18 East 41st Street, 2nd Floor
New York, NY 10017-6271
www.appinions.com
Where Influence Isn’t a Game
On Mon, Apr 29, 2013 at 9:20 AM, Arkadi Colson <ark...@smartbit.be> wrote:
> I found this in the zookeeper directory /collections/collectionX/
>
> {
> "configName":"smsc",
> "router":"implicit"}
>
>
> Is "router:implicit" the cause of this? Is it possible to fix?
>
> Thx!
>
>
> On 04/29/2013 01:24 PM, Arkadi Colson wrote:
>>
>> Is it correct that if I create a collection B with parameter createNodeSet
>> = hostB and I query on hostA something for collectionA it could not be
>> found?
>>
>> BR,
>> Arkadi
>>
>>
>>
>>
>
