Thanks for the heads up. I just tested this and you are right. I am making
a call to "addBeans" and it succeeds without any issue even when the server
is down. That sucks.
A big part of this process is reliant on knowing exactly what has made it
into the index and what has not, so this a difficult
On 10/9/2012 3:02 PM, Briggs Thompson wrote:
*Otis* - jstack is a great suggestion, thanks! The problem didn't happen
this morning but next time it does I will certainly get the dump to see
exactly where the app is swimming around. I haven't used
StreamingUpdateSolrServer
but I will see if that m
They are both SolrJ.
What is happening is I have a "batch" indexer application that does a full
re-index once per day. I also have an "incremental" indexer that takes
items off a queue when they are updated.
The problem only happens when both are running at the same time - they also
run from the
On Wed, Oct 10, 2012 at 5:36 PM, Briggs Thompson
wrote:
> There are other updates that happen on the server that do not fail, so the
> answer to your question is yes.
The other updates are using solrj or something else?
It would be helpful if you could prepare a simple java program that
uses sol
There are other updates that happen on the server that do not fail, so the
answer to your question is yes.
On Wed, Oct 10, 2012 at 8:12 AM, Sami Siren wrote:
> On Wed, Oct 10, 2012 at 12:02 AM, Briggs Thompson
> wrote:
> > *Sami*
> > The client IS
> > instantiated only once and not for every re
On Wed, Oct 10, 2012 at 12:02 AM, Briggs Thompson
wrote:
> *Sami*
> The client IS
> instantiated only once and not for every request. I was curious if this was
> part of the problem. Do I need to re-instantiate the object for each
> request made?
No, it is expensive if you instantiate the client
Thanks all for your responses. For some reason the emails were getting
filtered out of my inbox.
*Otis* - jstack is a great suggestion, thanks! The problem didn't happen
this morning but next time it does I will certainly get the dump to see
exactly where the app is swimming around. I haven't used
: I did some digging and experimentation and found something interesting.
: When starting up the application, I see the following in Solr logs:
: Creating new http client, config:maxConnections=200&maxConnectionsPerHost=8
...
: It seems as though the maxConnections and maxConnectionsPerHos
Hi Briggs,
Did you try StreamingUpdateSolrServer? We are still facing the same issues
but noticed this happens only when "Physical Memory" in Solr Admin is high.
And yes SolrJ respects the connections.
Hi Team,
Another option we discussed was upgrading to HttpClient 4.2 in Solr war.
Would that f
On Tue, Oct 9, 2012 at 4:52 AM, Briggs Thompson
wrote:
> I am running into an issue of a multithreaded SolrJ client application used
> for indexing is getting into a hung state. I responded to a separate thread
> earlier today with someone that had the same error, see
> http://lucene.472066.n3.nab
Hi,
Qs:
* Have you tried StreamingUpdateSolrServer?
* Newever version of Solr(J)?
When things hang, jstack your app that uses SolrJ and Solr a few times
and you should be able to see where they are stuck.
Otis
--
Search Analytics - http://sematext.com/search-analytics/index.html
Performance Moni
11 matches
Mail list logo
