[ 
https://issues.apache.org/jira/browse/DIRSERVER-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606051#action_12606051
 ] 

Alex Karasulu commented on DIRSERVER-1161:
------------------------------------------

Emmanuel did you want to take this on since you've been working on this.  if 
not let me know I can knock this out after getting back up to speed with this 
issue.  We probably should fix this in 1.5.3.

> search results are not streamed to the client until final done response is 
> queued
> ---------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1161
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1161
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0
>         Environment: JDK 1.5.0_11 
>            Reporter: Norval Hope
>            Priority: Blocker
>             Fix For: 1.5.3
>
>         Attachments: apacheds_1.5.1_streaming.patch, 
> apacheds_1.5.1_streaming.patch, apacheds_1.5.1_streaming_log_output.txt, 
> installers_1.5.1_streaming.patch, installers_1.5.1_streaming.patch, 
> mina_1.1.2_streaming.patch, mina_1.1_trunk_streaming.patch, pom.xml, 
> streaming_log_output.txt, streaming_logging.patch
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Search results accumulate in Events on the SessionBuffer.eventQueue within 
> ExecutorFilter.fireEvent() until final done response for the search is 
> written to the session and then all results for the search (possibly millions 
> depending on the search and state of the directory) are written out at once. 
> This is a big problem for scalability and I gather from previous 
> correspondence with Alex that this behaviour is unexpected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to