You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Shawn Heisey <so...@elyograg.org> on 2012/11/30 22:15:02 UTC
Exceptions in branch_4x log
This is branch_4x, checked out 2012-11-28. Here is my solr log, created
by log4j at WARN level:
http://dl.dropbox.com/u/97770508/solr-2012-11-30.log
There are a bunch of unusual exceptions in here. Most of them appear to
be related to getting information from the mbeans handler, specifically
getting the size of the index from the replication handler ... it
appears that for this exception, the index gets updated while the stats
are being gathered, and files in the index disappear.
The other exceptions look like they are I/O related. I don't know why
they are happening. Can anyone shed any light on the situation? What
other information should I include for troubleshooting?
For the disappearing index files, I am guessing that some kind of
synchronization may need to be added so that the index cannot change
while the replication handler is gathering the size information. I am
actually not using replication, the only reason I have the handler
configured is so that I can get the size of my indexes. See SOLR-3990.
https://issues.apache.org/jira/browse/SOLR-3990
I think I need to file jira issues for these problems, but I would like
to understand them better before doing that. Can anyone offer any insight?
Thanks,
Shawn
Re: Exceptions in branch_4x log
Posted by Mark Miller <ma...@gmail.com>.
On Nov 30, 2012, at 5:04 PM, Shawn Heisey <so...@elyograg.org> wrote:
> The other exceptions in the log look more serious.
My guess would be that the sizeOf exception is leading to the others.
- Mark
Re: Exceptions in branch_4x log
Posted by Shawn Heisey <so...@elyograg.org>.
On 11/30/2012 2:24 PM, Mark Miller wrote:
> You are using a local filesystem and not like NFS?
>
> If you are not replicating, I'm surprised this would happen and doubt it's the bug mentioned in the other reply.
>
> It could just be a bug we have to defend against - if a file is not there because the index is changing as we are counting, we should probably just continue on.
Yes, it's a local filesystem, ext4 on LVM, scsi driver is mpt2sas --
Dell hardware RAID1.
Linux bigindy5 2.6.32-279.14.1.el6.centos.plus.x86_64 #1 SMP Wed Nov 7
00:40:45 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I've checked out the latest revision from SVN and I'll file a new bug if
that particular exception happens again.
The other exceptions in the log look more serious. This is a dev box,
so it doesn't see all that much traffic, but so far I have not noticed
any actual problems.
Thanks,
Shawn
Re: Exceptions in branch_4x log
Posted by Mark Miller <ma...@gmail.com>.
You are using a local filesystem and not like NFS?
If you are not replicating, I'm surprised this would happen and doubt it's the bug mentioned in the other reply.
It could just be a bug we have to defend against - if a file is not there because the index is changing as we are counting, we should probably just continue on.
- Mark
On Nov 30, 2012, at 4:15 PM, Shawn Heisey <so...@elyograg.org> wrote:
> This is branch_4x, checked out 2012-11-28. Here is my solr log, created by log4j at WARN level:
>
> http://dl.dropbox.com/u/97770508/solr-2012-11-30.log
>
> There are a bunch of unusual exceptions in here. Most of them appear to be related to getting information from the mbeans handler, specifically getting the size of the index from the replication handler ... it appears that for this exception, the index gets updated while the stats are being gathered, and files in the index disappear.
>
> The other exceptions look like they are I/O related. I don't know why they are happening. Can anyone shed any light on the situation? What other information should I include for troubleshooting?
>
> For the disappearing index files, I am guessing that some kind of synchronization may need to be added so that the index cannot change while the replication handler is gathering the size information. I am actually not using replication, the only reason I have the handler configured is so that I can get the size of my indexes. See SOLR-3990.
>
> https://issues.apache.org/jira/browse/SOLR-3990
>
> I think I need to file jira issues for these problems, but I would like to understand them better before doing that. Can anyone offer any insight?
>
> Thanks,
> Shawn
>
Re: Exceptions in branch_4x log
Posted by Shawn Heisey <so...@elyograg.org>.
On 11/30/2012 2:24 PM, Markus Jelsma wrote:
> Hi, try updating your check out, i think that's fixed now.
> https://issues.apache.org/jira/browse/SOLR-4117
Thank you, that's the most common problem. I'll let you know how it
turns out.
There are still other problems in the log. Anyone have any idea about
those?
Thanks,
Shawn
RE: Exceptions in branch_4x log
Posted by Markus Jelsma <ma...@openindex.io>.
Hi, try updating your check out, i think that's fixed now.
https://issues.apache.org/jira/browse/SOLR-4117
-----Original message-----
> From:Shawn Heisey <so...@elyograg.org>
> Sent: Fri 30-Nov-2012 22:21
> To: solr-user@lucene.apache.org
> Subject: Exceptions in branch_4x log
>
> This is branch_4x, checked out 2012-11-28. Here is my solr log, created
> by log4j at WARN level:
>
> http://dl.dropbox.com/u/97770508/solr-2012-11-30.log
>
> There are a bunch of unusual exceptions in here. Most of them appear to
> be related to getting information from the mbeans handler, specifically
> getting the size of the index from the replication handler ... it
> appears that for this exception, the index gets updated while the stats
> are being gathered, and files in the index disappear.
>
> The other exceptions look like they are I/O related. I don't know why
> they are happening. Can anyone shed any light on the situation? What
> other information should I include for troubleshooting?
>
> For the disappearing index files, I am guessing that some kind of
> synchronization may need to be added so that the index cannot change
> while the replication handler is gathering the size information. I am
> actually not using replication, the only reason I have the handler
> configured is so that I can get the size of my indexes. See SOLR-3990.
>
> https://issues.apache.org/jira/browse/SOLR-3990
>
> I think I need to file jira issues for these problems, but I would like
> to understand them better before doing that. Can anyone offer any insight?
>
> Thanks,
> Shawn
>
>