Hoss,
I'm sure the keys are unique. I'm generating them myself before adding. Only
a handful of items have gone in with duplicate keys.
Here is what the update handler is reporting (I assume since I last
restarted Solr on 6/13):
commits : 17429
autocommits : 0
optimizes : 0
docsPending : 3
del
: want to be sure as it seems that some are being dropped. I just need to know
: if this can happen during commits or if I should be looking elsewhere to
: resolve my dropped record problem.
are you sure you aren't adding documents with identicle uniqueKeys to
existing documents? what does "doc
The version of 1.2 I'm using does use the update servlet and would return 400
( or similar ) if something went wrong, and 200 if OK, but, like you
suggested, perhaps a 200 does not entirely mean it completely worked.
It sounds like 1.3 is the way to go. I will start with the 1.3 config and
schema
On Mon, Jun 16, 2008 at 6:07 PM, dls1138 <[EMAIL PROTECTED]> wrote:
> I'm getting all 200 return codes from Solr on all of my batches.
IIRC, Solr1.2 uses the update servlet and always returns 200 (you need
to look at the response body to see if there was an error or not).
> I skimmed the logs for
I'm getting all 200 return codes from Solr on all of my batches.
I skimmed the logs for errors, but I didn't try to grep for "Exception". I
will take your advice look there for some clues.
Incidentally I'm running solr 1.2 using Jetty. I'm not on 1.3 because I read
it wasn't released yet. Is th
No records should be dropped, regardless of if a commit or optimize is going on.
Are you checking the return codes (HTTP return codes for Solr 1.3)?
Some updates could be failing for some reason.
Also grep for "Exception" in the solr log file.
-Yonik
On Mon, Jun 16, 2008 at 4:02 PM, dls1138 <[EMA
