qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aidan Skinner (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Created: (QPID-1303) I/O layer requirements need definition
Date Tue, 30 Sep 2008 13:49:44 GMT
I/O layer requirements need definition
--------------------------------------

                 Key: QPID-1303
                 URL: https://issues.apache.org/jira/browse/QPID-1303
             Project: Qpid
          Issue Type: Task
          Components: Java Broker, Java Client
    Affects Versions: M4
            Reporter: Aidan Skinner
            Assignee: Aidan Skinner
             Fix For: M4


The Qpid broker has displayed some undesirable behaviour when under heavy load, with high
volume persistent messaging exposing some limitations to the way in which the broker manages
the processing of that load.

Team discussions & analysis have led us to the existing i/O layer on the broker, and specifically
the way that MINA handles the stream of messages in this scenario. It seems most likely that
we now have a pressing need to replace the MINA I/O packages with an improved solution - where
the main focus of this replacement is to improve, significantly, the reliability of the Java
broker under heavy load.

This task describes the work required to define a clear technical specification for an I/O
layer for the Qpid Java Broker. As the cost & risk implied by this replacement is substantial,
we must be sure that we have a quality definition of the requirements the new code must meet.

The deliverables for this task are:

- A Technical Specification for the new I/O layer which includes:

1. A written set of numbered & prioritised functional and non-functional tech requirements
(ranked High/Med/Low). This can be done using a wiki page or a document in word format.
2. A completed review process, taking place on Apache Qpid and engaging the community. This
process should be documented alkongside the spec, including actions taken.
3. Updates resulting from a completed review reflected back into the spec & signed off.

Once we have a complete tech spec, we can then design, spec & estimate the work required.
This will include a review of existing code written by Rob Godfrey in this space, to compare
with the spec etc and ascertain fit for the problem before undertaking further work. 

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


Mime
View raw message