, this isn’t
catastrophic since both shards must be up to run.
That said, it does seem reasonable to use all the nodes in your case. If you
omit the createNodeSet, what happens? I’m curious if that’s confusing things
somehow. And can you totally guarantee that both nodes are accessible when the
oduct-20201027&collection.configName=sial-catalog-product-20200808&numShards=2&replicationFactor=1&maxShardsPerNode=1&createNodeSet=uc1a-ecomdev-msc02:8983_solr,uc1a-ecomdev-msc01:8983_solr
The call returns this:
{
"responseHeader": {
"status": 0,
"
wondering if you're taking your node names from the information ZK
> > >> > records or assuming it's 127.0.0.1
> > >> >
> > >> > On Sat, Jul 18, 2015 at 8:56 AM, Savvas Andreas Moysidis
> > >> > wrote:
> > >> >&
ing your node names from the information ZK
> >> > records or assuming it's 127.0.0.1
> >> >
> >> > On Sat, Jul 18, 2015 at 8:56 AM, Savvas Andreas Moysidis
> >> > wrote:
> >> >> Thanks Eric,
> >> >>
> >&g
t 8:56 AM, Savvas Andreas Moysidis
>> > wrote:
>> >> Thanks Eric,
>> >>
>> >> The strange thing is that although I have set the log level to "ALL" I
>> see
>> >> no error messages in the logs (apart from the line saying that
sages in the logs (apart from the line saying that the
> response
> >> is a 400 one).
> >>
> >> I'm quite confident the configset does exist as the collection gets
> created
> >> fine if I don't specify the createNodeSet param.
> >
ng that the response
> is a 400 one).
>
> I'm quite confident the configset does exist as the collection gets created
> fine if I don't specify the createNodeSet param.
>
> Complete mystery..! I'll keep on troubleshooting and report back with my
> findings.
>
> Ch
2015 at 8:56 AM, Savvas Andreas Moysidis
> wrote:
>> Thanks Eric,
>>
>> The strange thing is that although I have set the log level to "ALL" I see
>> no error messages in the logs (apart from the line saying that the response
>> is a 400 one).
>&g
Thanks Eric,
The strange thing is that although I have set the log level to "ALL" I see
no error messages in the logs (apart from the line saying that the response
is a 400 one).
I'm quite confident the configset does exist as the collection gets created
fine if I don't speci
, and I'm quite sure
there are bunches of automated tests that would be failing so I
suspect it's just a misleading error being returned.
Best,
Erick
On Thu, Jul 16, 2015 at 2:22 AM, Savvas Andreas Moysidis
wrote:
> Hello There,
>
> I am trying to use the createNodeSet paramete
Hello There,
I am trying to use the createNodeSet parameter when creating a new
collection but I'm getting an error when doing so.
More specifically, I have four Solr instances running locally in separate
JVMs (127.0.0.1:8983, 127.0.0.1:8984, 127.0.0.1:8985, 127.0.0.1:8986) and a
stand
he 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
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
AM, Arkadi Colson
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
quot;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
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
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
ons
>>> 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 wrote:
>>
quot;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
"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
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, Ark
ect 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
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
>> I've been unable to get the collections create API to work with
>> createNodeSet containing hostnames, both localhost and external
>>hostnames.
>> I've only been able to get it working when using explicit IP addresses.
>>
>> It looks like zk stores th
create API to work with
> createNodeSet containing hostnames, both localhost and external hostnames.
> I've only been able to get it working when using explicit IP addresses.
>
> It looks like zk stores the IP addresses in the clusterstate.json and
> live_nodes. Is it possible th
Hi all,
I've been unable to get the collections create API to work with
createNodeSet containing hostnames, both localhost and external hostnames.
I've only been able to get it working when using explicit IP addresses.
It looks like zk stores the IP addresses in the clusterstat
25 matches
Mail list logo