Information Classification: ll Limited Access
Thank you for your reply Shawn. I'm not part of that user list so I never
received any emails so far.
Could you please subscribe me (vyeleswar...@statestreet.com) or let me know the
process?
Also I would greatly appreciate if you could forward any responses received for
this issue.
To answer your question, we see these messages in the solr log file. Solr
search option is visible on the UI but when we search for a text, it says "No
results found".
The index files are not getting generated/created. We have the index job
scheduled to run every min, and solr log file is filled with below messages.
"Object not fetched because its identifier appears to be already in
processing".
These are the Solr & lucene versions.
solr-spec 4.3.1
solr-impl 4.3.1 1491148 - shalinmangar - 2013-06-09 12:15:33
lucene-spec 4.3.1
lucene-impl 4.3.1 1491148 - shalinmangar - 2013-06-09 12:07:58
Solr master and slave configuration is working fine and I'm able to access the
urls.
All we are trying is to make the search function work on UI. Please let me know
if you need any more details.
P.S: Kindly keep me in Cc until I'm added to the user list.
Thank you,
Dutt
-----Original Message-----
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Tuesday, February 27, 2018 10:09 PM
To: solr-user@lucene.apache.org
Cc: YELESWARAPU, VENKATA BHAN <vyeleswar...@statestreet.com>
Subject: Re: Gentle reminder RE: Object not fetched because its identifier
appears to be already in processing
On 2/27/2018 7:08 AM, YELESWARAPU, VENKATA BHAN wrote:
> While indexing job is running we are seeing the below message for all the
> objects.
>
> Object not fetched because its identifier appears to be already in
> processing
This time, I am going to include you as a CC on the message. This is not
normally something that I do, because posting to the list normally requires
subscribing to the list, so you should be getting all replies from the list.
I'm pretty sure that I already replied once asking for information, but I never
got a response.
Another thing I said on my last reply: The text of the error message you have
provided (in the subject and in the text I quoted above) is not in the Solr or
Lucene codebase. So right away we know that it wasn't generated by Solr. It
may have been generated by the other piece of software *inside* Solr, but
without the rest of the error information, we have no way of knowing what
actually happened. Solr errors tend to be dozens of lines long, with most of
the output being a Java stacktrace. And in order to make sense of the
stacktrace, we must have the Solr version.
In addition to the details Cassandra mentioned, there's one bit that will be
critical:
Where *exactly* did you see this error? Was it in the Solr admin UI, the Solr
logfile, the logging output from your indexing program, or somewhere else?
Thanks,
Shawn
