lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3544) Under heavy load json response is cut at some arbitrary position
Date Thu, 14 Jun 2012 20:51:42 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295307#comment-13295307
] 

Hoss Man commented on SOLR-3544:
--------------------------------

can you provide some more details please...

1) what servlet container are you using?
2) how big (in bytes) are the responses when they work? how big are they when "cut off"?
3) does the "cut off" always happen on/around a specific piece of markup? (ie: when closing
a list or an object) or in the middle of arbitrary string values?  is it possible there are
certain byte sequences that always occur just before/at/after the cutoff happens?
4) your blog post mentions...

bq. Unfortunately, there was no indication of any malfunction in Solr except for the “Broken
Pipe” notification that the client has closed the connection.

...where are you seeing this? in packet sniffing tool? in the solr logs? ... what exactly
is the full message? 


                
> Under heavy load json response is cut at some arbitrary position
> ----------------------------------------------------------------
>
>                 Key: SOLR-3544
>                 URL: https://issues.apache.org/jira/browse/SOLR-3544
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 3.1
>         Environment: Linux version 2.6.32-5-amd64 (Debian 2.6.32-38) (ben@decadent.org.uk)
(gcc version 4.3.5 (Debian 4.3.5-4) )
>            Reporter: Dušan Omerčević
>
> We query solr for 30K documents using json as the response format. Normally this works
perfectly fine. But when the machine comes under heavy load (all cores utilized) the response
got interrupted at arbitrary position. We circumvented the problem by switching to xml response
format.
> I've written the full description here: http://restreaming.wordpress.com/2012/06/14/the-curious-case-of-solr-malfunction/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message