two instances to see if it's possible to reproduce the issue.
-- Nathan
--------
Nathan Neulinger nn...@neulinger.org
Neulinger Consulting (573) 612-1412
ax at all. I'm guessing that SOLR doesn't actually validate the
JSON, and it's parser is just creating something weird in that situation like a new request for a whole new document.
-- Nathan
On 07/15/2014 07:19 PM, Nathan Neulinger wrote:
Issue was closed in Jira requesting it
4.8.0 w/ solr cloud, 2 nodes, 3 zk, linux x86_64
It seems like when the issue occurs, I get a set of the errors all in a burst
(below), never just one.
Suggestions?
-- Nathan
Nathan Neulinger nn...@neulinger.org
Tried changing to use /solr/admin/cores instead as a test - still see the
same issue, though much less frequent.
Nathan Neulinger nn...@neulinger.org
Neulinger Consulting (573) 612-1412
On Sat
"timeout check" value,
because it is too small. The ping request is taking longer to run than
you have allowed in the timeout. Here's part of my haproxy config:
--
--------
Nathan Neulinger nn...@neul
the same box, that flood runs with generally 10-20ms request times and
zero errors.
-- Nathan
On 07/27/2014 07:12 PM, Nathan Neulinger wrote:
Cool. That's likely exactly it, since I don't have one set, it's using the
check interval, and occasionally must just be
too short.
Thank
Either way, looks like this is not a SOLR issue, but rather haproxy.
Thanks.
-- Nathan
On 07/27/2014 08:23 PM, Nathan Neulinger wrote:
Unfortunately, doesn't look like this clears the symptom.
The ping is responding almost instantly every time. I've tried setting a 15
second time
t at least one other person on #haproxy is seeing the same behavior.
Doesn't appear to be specific to solr.
-- Nathan
On 07/27/2014 10:44 PM, Shawn Heisey wrote:
On 7/27/2014 7:23 PM, Nathan Neulinger wrote:
Unfortunately, doesn't look like this clears the symptom.
The ping is res
Or do I need to actually determine a list of cores (..._shardX_replicaY) and trigger the core creates myself, at which
point I gather that it will start recovery for each of them?
-- Nathan
----
Nathan Neulinger nn..
it wrong?
-- Nathan
--------
Nathan Neulinger nn...@neulinger.org
Neulinger Consulting (573) 612-1412
s resolved for Solr 4.6.1 which should be out next week.
Joel Bernstein
Search Engineer at Heliosearch
On Fri, Jan 24, 2014 at 9:52 PM, Nathan Neulinger wrote:
How can we issue an update request and be certain that all of the replicas
in the SolrCloud cluster are up to date?
I found
nshum Gupta wrote:
Hi Nathan,
It'd be great to have more information about your setup, Solr Version?
Depending upon your version, you might want to also look at:
https://issues.apache.org/jira/browse/SOLR-4260 (which is now fixed).
On Fri, Jan 24, 2014 at 6:52 PM, Nathan Neulinger wrote:
ey're searchable, however. For a
document to be found in a search there must be a commit, either soft,
or hard with openSearcher=true. Here's a post that outlines all this.
If you have discrepancies when after commits, that's a problem
Best,
Erick
On Fri, Jan 24, 2014 at 8:52
Mark
http://about.me/markrmiller
On Jan 24, 2014, at 12:01 PM, Nathan Neulinger wrote:
I have an environment where new collections are being added frequently
(isolated per customer), and the backup is virtually guaranteed to be missing
some of them.
As it stands, bringing up the restored/out-of-dat
us that will reflect that the replica is
gone?
This is with 4.8.0.
-- Nathan
--------
Nathan Neulinger nn...@neulinger.org
Neulinger Consulting (573) 612-1412
live nodes.
If the live node is not there, it's gone regardless of the last state it
published.
- Mark
On Aug 23, 2014, at 6:00 PM, Nathan Neulinger wrote:
In particular, a shard being 'active' vs. 'gone'.
The web ui is clearly showing the given replicas as being
16 matches
Mail list logo
