You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "YELESWARAPU, VENKATA BHAN" <VY...@StateStreet.com> on 2018/02/27 14:08:18 UTC
Gentle reminder RE: Object not fetched because its identifier
appears to be already in processing
Information Classification: ** Limited Access
If any of you experts could help, we would greatly appreciate it. Thank you.
From: YELESWARAPU, VENKATA BHAN
Sent: Friday, February 23, 2018 8:30 AM
To: 'dev@lucene.apache.org' <de...@lucene.apache.org>; 'solr-user@lucene.apache.org' <so...@lucene.apache.org>
Subject: Object not fetched because its identifier appears to be already in processing
Information Classification: ** Limited Access
Dear Users,
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
What is the issue and how to resolve this so that indexing can work. Could you please guide.
Thank you,
Dutt
RE: Gentle reminder RE: Object not fetched because its identifier
appears to be already in processing
Posted by "YELESWARAPU, VENKATA BHAN" <VY...@StateStreet.com>.
Information Classification: ll Limited Access
Thanks Shawn, I submitted a request to subscribe.
After restarting jboss and redeploying solr war files, index files were successfully created and global search is now working.
Not sure what really was the problem and what was fixed. :) We spent few days on this.
Anyways, thank you very much for your support. Will get back if I have any questions.
Good day
Dutt
-----Original Message-----
From: Shawn Heisey [mailto:apache@elyograg.org]
Sent: Wednesday, February 28, 2018 1:08 PM
To: solr-user@lucene.apache.org
Cc: YELESWARAPU, VENKATA BHAN <VY...@StateStreet.com>
Subject: Re: Gentle reminder RE: Object not fetched because its identifier appears to be already in processing
On 2/28/2018 12:06 AM, YELESWARAPU, VENKATA BHAN wrote:
> 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 (vyeleswarapu@statestreet.com) or let me know the process?
> Also I would greatly appreciate if you could forward any responses received for this issue.
You can subscribe yourself. That's not something I can do for you.
http://lucene.apache.org/solr/community.html#mailing-lists-irc
> 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".
Can you place that logfile (ideally the whole thing) somewhere and provide a URL for accessing it? There are many paste websites and many file sharing sites that you can use to do this. With the actual logfile, hopefully the problem can be found.
If I do a google search for that error message, the only thing that comes up is messages from you. It doesn't appear to be something that people have encountered before.
> 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
If we determine that there *is* a bug, it will need to be demonstrated in the current version (7.2.1) before it can be fixed. There will be no more 4.x releases. As you can see, the version you're running is nearly five years old.
> 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.
What happens if you leave the query as *:* and execute it? This is special syntax for all documents.
Thanks,
Shawn
Re: Gentle reminder RE: Object not fetched because its identifier
appears to be already in processing
Posted by Shawn Heisey <ap...@elyograg.org>.
On 2/28/2018 12:06 AM, YELESWARAPU, VENKATA BHAN wrote:
> 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 (vyeleswarapu@statestreet.com) or let me know the process?
> Also I would greatly appreciate if you could forward any responses received for this issue.
You can subscribe yourself. That's not something I can do for you.
http://lucene.apache.org/solr/community.html#mailing-lists-irc
> 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".
Can you place that logfile (ideally the whole thing) somewhere and
provide a URL for accessing it? There are many paste websites and many
file sharing sites that you can use to do this. With the actual
logfile, hopefully the problem can be found.
If I do a google search for that error message, the only thing that
comes up is messages from you. It doesn't appear to be something that
people have encountered before.
> 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
If we determine that there *is* a bug, it will need to be demonstrated
in the current version (7.2.1) before it can be fixed. There will be no
more 4.x releases. As you can see, the version you're running is nearly
five years old.
> 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.
What happens if you leave the query as *:* and execute it? This is
special syntax for all documents.
Thanks,
Shawn
RE: Gentle reminder RE: Object not fetched because its identifier
appears to be already in processing
Posted by "YELESWARAPU, VENKATA BHAN" <VY...@StateStreet.com>.
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 (vyeleswarapu@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:apache@elyograg.org]
Sent: Tuesday, February 27, 2018 10:09 PM
To: solr-user@lucene.apache.org
Cc: YELESWARAPU, VENKATA BHAN <VY...@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
Re: Gentle reminder RE: Object not fetched because its identifier
appears to be already in processing
Posted by Shawn Heisey <ap...@elyograg.org>.
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
Re: Gentle reminder RE: Object not fetched because its identifier
appears to be already in processing
Posted by Cassandra Targett <ca...@gmail.com>.
There is not enough information here for anyone to answer. You mention a
"below message", but there is no message that we can see. If it was in an
attachment to the mail, it got stripped by the mail server.
If you want a response, please provide in the body of the mail details such
as: the error message you see (with the full stack trace, if possible);
what you are trying to index; the version of Solr you are using; any custom
configurations you may have in place; and any other detail that might help
someone who doesn't have access to your system try to guess what might be
going wrong.
Cassandra
On Tue, Feb 27, 2018 at 8:08 AM, YELESWARAPU, VENKATA BHAN <
VYELESWARAPU@statestreet.com> wrote:
> *Information Classification: **ll*
>
> * Limited Access *
>
> If any of you experts could help, we would greatly appreciate it. Thank
> you.
>
>
>
> *From:* YELESWARAPU, VENKATA BHAN
> *Sent:* Friday, February 23, 2018 8:30 AM
> *To:* 'dev@lucene.apache.org' <de...@lucene.apache.org>; '
> solr-user@lucene.apache.org' <so...@lucene.apache.org>
> *Subject:* Object not fetched because its identifier appears to be
> already in processing
>
>
>
> *Information Classification: **ll** Limited Access*
>
> Dear Users,
>
>
>
> 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
>
>
>
> What is the issue and how to resolve this so that indexing can work. Could
> you please guide.
>
>
>
> Thank you,
>
> Dutt
>
>
>