[SOLR-1951] extractingUpdateHandler doesn't close socket handles promptly, and indexing load tests eventually run out of resources

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 1.4.1, 1.5
• Component/s: update
• Labels: delay leak socket update

Environment

sun java
solr 1.5 build based on trunk
debian linux "lenny"

• Assignee: Unassigned
• Reporter: Karl Wright
• Created: 14/Jun/10 13:31
• Updated: 12/Dec/16 01:58
• Resolved: 17/Jun/10 00:02

Description

When multiple threads pound on extractingUpdateRequestHandler using multipart form posting over an extended period of time, I'm seeing a huge number of sockets piling up in the following state:

tcp6 0 0 127.0.0.1:8983 127.0.0.1:44058 TIME_WAIT

Despite the fact that the client can only have 10 sockets open at a time, huge numbers of sockets accumulate that are in this state:

root@duck6:~# netstat -an | fgrep :8983 | wc
28223 169338 2257840
root@duck6:~#

The sheer number of sockets lying around seems to eventually cause commons-fileupload to fail (silently - another bug) in creating a temporary file to contain the content data. This causes Solr to erroneously return a 400 code with "missing_content_data" or some such to the indexing poster.

Issue Links

• is related to: SOLR-1953 It may be possible for temporary files to accumulator until the Solr process is shut down