I like the version without the 'swoosh'. Simplicity is king in by book.
-S
On 12/18/06, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
On 12/18/06, Linda Tan <[EMAIL PROTECTED]> wrote:
> I just learned no attachments are allowed on this list. I've put the
> image in the jira..
Thanks, it look
That's a great idea, thanks Yonik.
-Sangraal
On 12/11/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 12/11/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> I'm looking into creating something to track the top 10 - 20 searches
that
> run through Solr for a given per
I'm looking into creating something to track the top 10 - 20 searches that
run through Solr for a given period.
I could just create a counter object with an internal TreeMap or something
that just keeps count of the various terms, but it could grow very large
very fast and I'm not yet sure what i
That would be helpful, as long as it's conveyed clearly.
-S
On 11/7/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 11/7/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> comparing the CHANGES.txt files of any two nightly builds is the best
way
> to see what thigns have changed that you might wn
Thanks for the great explanation Yonik, I passed it on to my collegues for
reference... I knew there was a good reason.
-Sangraal
On 9/21/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 9/21/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> Perhaps a silly questions, but I'm
Perhaps a silly questions, but I'm wondering if anyone can tell me why solr
outputs XML like this:
201038
31
2006-09-15T21:36:39.000Z
rather than like this:
201038
31
2006-09-15T21:36:39.000Z
A front-end PHP developer I know is having trouble parsing the default Solr
output because of that
I sent out an email about this a while back, but basically this limit
appears only on Tomcat and only when Solr attempts to write to the response.
You can work around it by splitting up your posts so that you're posting
less than 5000 (or whatever your limit seems to be) at a time. You DO NOT
ha
I've set up 2 separate Solr indexes on one Tomcat instance. I basically
created two separate Solr webapps. I have one webapp that is the client to
both Solr instances as well. So the whole setup is 3 webapps.
I have one set of Solr source classes and an ant task to build a jar file
and copy it in
Hey guys,
You might remember a bunch of emails going back and forth between me and the
very helpful Solr folks a few weeks back. I just wanted to let you know
about what I've learned about the problem in last week or so.
The problem was that I would run into a hard limit of how many documents I
c
tem.err.println(ioe.toString());
} catch (ModuleException me) {
System.err.println("Error handling request: " + me.getMessage());
} catch (Exception e) {
System.err.println("Unknown Error: " + e.getMessage());
}
return updateResult.toString();
}
-
input -- not too difficult to do, though best to do
with two threads (i.e. fire off a thread to read the response before
you send any data). Seeing as the HttpClient code probably does this
already, I'll most likely end up using that.
On 7/31/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
&
Chris, my response is below each of your paragraphs...
I don't have the means to try out this code right now ... but i can't see
any obvious problems with it (there may be somewhere that you are opening
a stream or reader and not closing it, but i didn't see one) ... i notice
you are running th
Those are some great ideas Chris... I'm going to try some of them out. I'll
post the results when I get a chance to do more testing. Thanks.
At this point I can work around the problem by ignoring Solr's response but
this is obviously not ideal. I would feel better knowing what is causing the
is
connection handling correct can be
tough... it's probably a good idea if we work toward common client
libraries so everyone doesn't have to reinvent them.
-Yonik
On 7/28/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> Sure, the method that does all the work updating Solr is
Sure, the method that does all the work updating Solr is the doUpdate(String
s) method in the GanjaUpdate class I'm pasting below. It's hanging when I
try to read the response... the last output I receive in my log is Got
Reader...
--
package com.iceninetech.solr.update;
import com.icen
works fine, but in those instances the server responds much faster to the
request.
This is an elusive bug for sure.
-S
On 7/27/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 7/27/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> Commenting out the following line in SolrCore fixes my pr
I'll give that a shot...
Thanks again for all your help.
-S
On 7/27/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
You might also try the Java update client here:
http://issues.apache.org/jira/browse/SOLR-20
-Yonik
Commenting out the following line in SolrCore fixes my problem... but of
course I don't get the result status info... but this isn't a problem for me
really.
-Sangraal
writer.write("");
On 7/27/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
I'm running on Tomca
ing).
It is certainly worth investigating why this occurs, but I wonder
about the advantages of using such huge batches. Assuming a few
hundred bytes per document, 6100 docs produces a POST over 1MB in
size.
-Mike
On 7/27/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> Mi
ackTrace();
}
return updateResult.toString();
}
}
-Sangraal
On 7/27/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
Are you reading the response and closing the connection? If not, you
are probably running out of socket connections.
-Yonik
On 7/27/06, sangraal aiken <[EMAIL PROTECTE
certainly worth investigating why this occurs, but I wonder
about the advantages of using such huge batches. Assuming a few
hundred bytes per document, 6100 docs produces a POST over 1MB in
size.
-Mike
On 7/27/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> Mike,
> I've been posti
Mike,
I've been posting with the content type set like this:
conn.setRequestProperty("Content-Type", "application/octet-stream");
I tried your suggestion though, and unfortunately there was no change.
conn.setRequestProperty("Content-Type", "text/xml; charset=utf-8");
-Sangraal
On 7/
ate servlet.");
-Sangraal
On 7/27/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 7/26/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> I removed everything from the Add xml so the docs looked like this:
>
>
> 187880
>
>
> 187852
>
>
> and it st
onik
On 7/26/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> I see the problem on Mac OS X/JDK: 1.5.0_06 and Debian/JDK: 1.5.0_07.
>
> I don't think it's a socket problem, because I can initiate additional
> updates while the server is hung... weird I know.
>
> Thanks fo
ong timeout and never reusing
them?)
What is your OS/JVM?
-Yonik
On 7/26/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> Right now the heap is set to 512M but I've increased it up to 2GB and
yet it
> still hangs at the same number 6,144...
>
> Here's something interesting..
blocking... probably because Tomcat isn't
reading anything from the socket because it's busy trying to restart
the webapp.
What is the heap size of the server? try increasing it... maybe tomcat
could have detected low memory and tried to reload the webapp.
-Yonik
On 7/26/06, sangraal
orkerThread.runIt(
LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(
ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:613)
-Yonik
On 7/26/06, sangraal aiken <[EMAIL PROTECTED]> wrote:
> Hey there... I'm having an issue with large doc updates on my
Hey there... I'm having an issue with large doc updates on my solr
installation. I'm adding in batches between 2-20,000 docs at a time and I've
noticed Solr seems to hang at 6,144 docs every time. Breaking the adds into
smaller batches works just fine, but I was wondering if anyone knew why this
w
28 matches
Mail list logo
