[
https://issues.apache.org/jira/browse/BOOKKEEPER-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009349#comment-16009349
]
Hudson commented on BOOKKEEPER-1066:
------------------------------------
FAILURE: Integrated in Jenkins build bookkeeper-master #1746 (See
[https://builds.apache.org/job/bookkeeper-master/1746/])
BOOKKEEPER-1066: Introduce GrowableArrayBlockingQueue (eolivelli: rev
e2894a9e9946b4cc4647c280094bcb2eb1a521ea)
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/util/collections/GrowableArrayBlockingQueue.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/util/MathUtils.java
* (add)
bookkeeper-server/src/test/java/org/apache/bookkeeper/util/collections/GrowableArrayBlockingQueueTest.java
> Introduce GrowableArrayBlockingQueue
> ------------------------------------
>
> Key: BOOKKEEPER-1066
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1066
> Project: Bookkeeper
> Issue Type: Improvement
> Reporter: Matteo Merli
> Assignee: Matteo Merli
> Priority: Minor
> Fix For: 4.5.0
>
>
> In multiple places, (eg: journal, ordered executor, etc..), we are using
> {{LinkedBlockingQueue}} instances to pass objects between threads.
> The {{LinkedBlockingQueue}} differs from the {{ArrayBlockingQueue}} in that
> it doesn't require to define a max queue size, though, being implemented with
> a linked list, it requires to allocates list nodes each time an item is added.
> We can use a {{GrowableArrayBlockingQueue}} that behaves in the same way as
> the {{LinkedBlockingQueue}}, but it's implemented with an array that can be
> resized when the queue reaches the capacity.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
