Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Date: Thu, 5 Jan 2012 22:02:40 +0000 (UTC)
From: "Jay Kreps (Updated) (JIRA)" <jira@apache.org>
To: kafka-dev@incubator.apache.org
Message-ID: 
 <1292689867.11746.1325800960663.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1063016114.23438.1321068052780.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (KAFKA-202) Make the request processing in kafka
 asynchonous
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/KAFKA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Kreps updated KAFKA-202:
----------------------------

    Attachment: KAFKA-202-v3.patch

Updated patch to current trunk.
                
> Make the request processing in kafka asynchonous
> ------------------------------------------------
>
>                 Key: KAFKA-202
>                 URL: https://issues.apache.org/jira/browse/KAFKA-202
>             Project: Kafka
>          Issue Type: New Feature
>            Reporter: Jay Kreps
>            Assignee: Jay Kreps
>         Attachments: KAFKA-202-v2.patch, KAFKA-202-v3.patch, KAFKA-48-socket-server-refactor-draft.patch
>
>
> We need to handle long-lived requests to support replication. To make this work we need to make the processing mechanism asynchronous from the network threads.
> To accomplish this we will retain the existing pool of network threads but add a new pool of request handling threads. These will do all the disk I/O. There will be a queue mechanism to transfer requests to and from this secondary pool.

--
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