When I first do a linkconfig the route:implicit seems to be gone! So
recreating the collection will solve this. The problem that I cannot
request a collection that does not exists on that host is still there.
Arkadi
On 04/29/2013 03:31 PM, Arkadi Colson wrote:
The strange thing is that I created some time ago 2 other collections
and there the router:implicit has not been set. Is it possible to
create a collection withour the router:implicit?
http://solr01:8983/solr/admin/collections?action=CREATE&name=lvs&numShards=5&replicationFactor=2&collection.configName=smsc
<http://solr01-dcg.intnet.smartbit.be:8983/solr/admin/collections?action=CREATE&name=lvs&numShards=5&replicationFactor=2&collection.configName=smsc>
VERSIONS
Solr 4.2.1
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Met vriendelijke groeten
Arkadi Colson
Smartbit bvba • Hoogstraat 13 • 3670 Meeuwen
T +32 11 64 08 80 • F +32 11 64 08 81
On 04/29/2013 03:24 PM, Michael Della Bitta wrote:
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
