Thanks, Erick that's exactly the clarification/confirmation I was looking for!
Greg
more of a workaround than a true fix?
>
> I'm entirely willing to apply this patch to all of the code I've got that
> talks to my solr servers and try it out but I'm reluctant to because this
> looks like a client-side fix to a server-side issue.
>
> Thanks,
> G
7;ve got that
talks to my solr servers and try it out but I'm reluctant to because this
looks like a client-side fix to a server-side issue.
Thanks,
Greg
--
View this message in context:
http://lucene.472066.n3.nabble.com/updating-docs-in-solr-cloud-hangs-tp4067388p4086160.html
Sent fro
Hi,
My cluster hangs again running an update process, the HTTP POST request was
aborted because a timeout error. After the hang, I couldn't do more updates
without restart the cluster.
I could see this error on node's log after kill it. Is like if solr waits for
the update response forever …
Did you take a stack trace of your _server_ and see if the
fragment I posted is the place a bunch of threads are
stuck? If so, then it's what I mentioned, and the patch
I pointed to should fix it up (when it's ready)...
The fact that it hangs more frequently with replication > 1
is consistent with
Shawn:
replicationFactor higher than one yes.
--
Yago Riveiro
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Sunday, June 2, 2013 at 4:07 PM, Shawn Heisey wrote:
> On 6/2/2013 8:28 AM, Yago Riveiro wrote:
> > Erick:
> >
> > In my case, when server hangs, no exception is thrown,
On 6/2/2013 8:28 AM, Yago Riveiro wrote:
> Erick:
>
> In my case, when server hangs, no exception is thrown, the logs on both
> servers stop registering the update INFO messages. if a shutdown one node,
> immediately the log of the alive node register some update INFO messages that
> appears wa
cument from the index and indexes an
> > updated one. The underlying lucene always requires to delete the old
> > document and index the new one..
> >
> >
> > We usually dont use partial update when updating huge number of documents.
> > This is really useful for small num
en updating huge number of documents.
> This is really useful for small number of documents (mostly during push
> indexing)...
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/updating-docs-in-solr-cloud-hangs-tp4067388p4067416.html
> Sent from the Solr - User mailing list archive at Nabble.com.
updating huge number of documents.
This is really useful for small number of documents (mostly during push
indexing)...
--
View this message in context:
http://lucene.472066.n3.nabble.com/updating-docs-in-solr-cloud-hangs-tp4067388p4067416.html
Sent from the Solr - User mailing list archive at
Hi,
I'm experimenting the same issue, I'm indexing a big file with 15M in batches
of 100K.
Sometimes, the indexing operation hangs and my HTTP client return an error of
timeout.
I see that is more frequent when the collection has more replicas.
Other thing that I can see is a lot of POST up
Hi all,
We're using Solr 4.1.0 and a 15 node Solr Cloud (configured for a 2 minute
autoCommit with no searcher being built). We have a large dataset in
Cassandra and use a Hadoop cluster to read over the dataset, build
documents, and insert them (via CloudSolrServer). That part works as
expected
12 matches
Mail list logo
