UNC-Libraries/Carolina-Digital-Repository — Issue #16: iRODS client socket timeouts on writes (jargon)
Author: gregjan
Created: 2011-11-10 18:30:59+00:00
State: open
Labels: bug

Lately several ingests have failed due to socket timeout. The jargon client inside of Fedora is waiting for a response from the server, but fails to get one within the normal 2 minutes timeout. There are any number of reasons for why the server might be slow, from replication to tape, to other kinds of IO blocking. I am fairly certain that the delay is not due to load/cpu on the iRODS server itself.

I am testing a patch to low-level storage which will increase this timeout to 5 minutes. I'd expect iRODS to finish long before then in most cases and reply. I'm also adding a special catch clause for socket timeout on iRODS output stream close. This is a particular operation that seems to take a long time. If it times out, there is still a chance that we can proceed. Since we do checksum comparison against iRODS for all write operations, any problems will still be detected.

This is in testing this afternoon on DEV.