On 7/25/2013 5:44 PM, Tim Vaillancourt wrote:
The transaction log error I receive after about 10-30 minutes of load
testing is:
"ERROR [2013-07-25 19:34:24.264] [org.apache.solr.common.SolrException]
Failure to open existing log file (non fatal)
/opt/easw/easw_apps/easo_solr_cloud/solr/xmshd_shard3_replica2/data/tlog/tlog.0000000000000000078:org.apache.solr.common.SolrException:
java.io.EOFException
<snip>
Caused by: java.io.EOFException
at
org.apache.solr.common.util.FastInputStream.readUnsignedByte(FastInputStream.java:73)
at
org.apache.solr.common.util.FastInputStream.readInt(FastInputStream.java:216)
at
org.apache.solr.update.TransactionLog.readHeader(TransactionLog.java:266)
at
org.apache.solr.update.TransactionLog.<init>(TransactionLog.java:160)
... 25 more
"
This looks to me like a system problem. RHEL should be pretty solid, I
use CentOS without any trouble. My initial guesses are a corrupt
filesystem, failing hardware, or possibly a kernel problem with your
specific hardware.
I'm running Jetty 8, which is the version that the example uses. Could
Jetty 9 be a problem here? I couldn't really say, though my initial
guess is that it's not a problem.
I'm running Oracle Java 1.7.0_13. Normally later releases are better,
but Java bugs do exist and do get introduced in later releases. Because
you're on the absolute latest, I'm guessing that you had the problem
with an earlier release and upgraded to see if it went away. If that's
what happened, it is less likely that it's Java.
My first instinct would be to do a 'yum distro-sync' followed by 'touch
/forcefsck' and reboot with console access to the server, so that you
can deal with any fsck problems. Perhaps you've already tried that.
I'm aware that this could be very very hard to get pushed through strict
change management procedures.
I did some searching. SOLR-4519 is a different problem, but it looks
like it has a similar underlying exception, with no resolution. It was
filed When Solr 4.1.0 was current.
Could there be a resource problem - heap too small, not enough OS disk
cache, etc?
Thanks,
Shawn
