Anyone an idea how to debug this?
Thx!
On 04/25/2013 09:18 AM, Arkadi Colson wrote:
Hi
It seems not to work in my case. We are using the solr php module for
talking to Solr. Currently we have 2 collections 'intradesk' and 'lvs'
for 10 solr hosts (shards: 5 - repl: 2). Because there is no
Anyone else having this problem that an update needs to go to a host
where a shard exists.
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)
Solr 4.2.1
apache-tomcat-7.0.33
Thx!
Met vriendelijke groeten
Hi
It seems not to work in my case. We are using the solr php module for
talking to Solr. Currently we have 2 collections 'intradesk' and 'lvs'
for 10 solr hosts (shards: 5 - repl: 2). Because there is no more disc
space I created 6 new hosts for collection 'messages' (shards: 3 - repl: 2).
We are using tomcat so we'll just wait. Hopefully it's fixed in 4.3 but
we have a work around for now so...
What exactly is the difference between jetty and tomcat. We are using
tomcat because we've read somewhere that it should be more robust in
heavily loaded production environments.
On 4/24/2013 12:49 AM, Arkadi Colson wrote:
We are using tomcat so we'll just wait. Hopefully it's fixed in 4.3 but
we have a work around for now so...
What exactly is the difference between jetty and tomcat. We are using
tomcat because we've read somewhere that it should be more robust in
Thx!
On 04/24/2013 04:46 PM, Shawn Heisey wrote:
On 4/24/2013 12:49 AM, Arkadi Colson wrote:
We are using tomcat so we'll just wait. Hopefully it's fixed in 4.3 but
we have a work around for now so...
What exactly is the difference between jetty and tomcat. We are using
tomcat because we've
Sorry - need to correct myself - updates worked the same as read requests -
they also needed to hit a SolrCore in order to get forwarded to the right node.
I was not thinking clearly when I said this applied to just reads and not
writes. Both needed a SolrCore to do their work - with the
Hi
Is it correct that when inserting or updating document into solr you
have to talk to a solr host where at least one shard of that collection
is stored?
For select you can talk to any host within the collection.configName?
BR,
Arkadi
I believe as of 4.2 you can talk to any host in the cloud.
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 Tue, Apr 23, 2013 at 10:45 AM, Arkadi Colson
If you use jetty - which you should :) It's what we test with. Tomcat only gets
user testing.
If you use tomcat, this won't work in 4.2 or 4.2.1, but probably will in 4.3
(we are voting on 4.3 now).
No clue on other containers.
- Mark
On Apr 23, 2013, at 10:59 AM, Michael Della Bitta
Oopps, Mark you said: If you use tomcat, this won't work in 4.2 or 4.2.1
Can you explain more what won't be at Tomcat and what will change at 4.3?
2013/4/23 Mark Miller markrmil...@gmail.com
If you use jetty - which you should :) It's what we test with. Tomcat only
gets user testing.
If you
The request proxying does not work with tomcat without calling an explicit
flush in the code - jetty (which the unit tests are written against) worked
without this flush. The flush is added to 4.3.
- Mark
On Apr 23, 2013, at 2:02 PM, Furkan KAMACI furkankam...@gmail.com wrote:
Oopps, Mark
Sorry but I want to make clears the things in my mind. Is there any
documentation that explains Solr proxying? Is it same thing with that: when
I use SolrCloud and if I send document any of the nodes at my cluster the
document will be routed into the leader of appropriate shard. So you mean I
can
: Furkan KAMACI
Sent: Tuesday, April 23, 2013 2:33 PM
To: solr-user@lucene.apache.org
Subject: Re: Update on shards
Sorry but I want to make clears the things in my mind. Is there any
documentation that explains Solr proxying? Is it same thing with that: when
I use SolrCloud and if I send document
This request proxying only applies to the read side. The write side forwards
updates around, it doesn't proxy requests.
- Mark
On Apr 23, 2013, at 2:33 PM, Furkan KAMACI furkankam...@gmail.com wrote:
Sorry but I want to make clears the things in my mind. Is there any
documentation that
On 4/23/2013 10:14 AM, Mark Miller wrote:
If you use jetty - which you should :) It's what we test with. Tomcat only gets
user testing.
If you use tomcat, this won't work in 4.2 or 4.2.1, but probably will in 4.3
(we are voting on 4.3 now).
No clue on other containers.
- Mark
On Apr 23,
On Apr 23, 2013, at 2:49 PM, Shawn Heisey s...@elyograg.org wrote:
What exactly is the 'request proxying' thing that doesn't work on tomcat? Is
this something different from basic SolrCloud operation where you send any
kind of request to any server and they get directed where they need to
Hi Mark;
All in all you say that when 4.3 is tagged at repository (I mean when it is
ready) this feature will work for Tomcat too at a stable version?
2013/4/23 Mark Miller markrmil...@gmail.com
On Apr 23, 2013, at 2:49 PM, Shawn Heisey s...@elyograg.org wrote:
What exactly is the
We have a 3rd release candidate for 4.3 being voted on now.
I have never tested this feature with Tomcat - only Jetty. Users have reported
it does not work with Tomcat. That leads one to think it may have a problem in
other containers as well.
A previous contributor donated a patch that
Mark, by the way is there an approximate date about when will Solr 4.3 be
ready?
2013/4/23 Mark Miller markrmil...@gmail.com
We have a 3rd release candidate for 4.3 being voted on now.
I have never tested this feature with Tomcat - only Jetty. Users have
reported it does not work with
20 matches
Mail list logo
