Hi, I wonder about these issues: (2 about building, 1 about consistency)
- BOOKKEEPER-66 use IPv4 for builds : currently you cannot build on some debian linux boxes with default settings without applying the patch for the build, or without skipping tests. (Ivan also mentioned modifying shell startup scripts, but the patch solves the build issue at least).
- BOOKKEEPER-67 BookieReadWriteTest gets blocked and never finishes : this problem also comes up when building from a default debian box, but there is no clear fix, apart from tweaking OS settings. I just ran the tests on ubuntu 11, and the "too many open files" issue also affects other new tests from hedwig.
Note: both of these issues can be fixed by using the right settings on the linux os. Maybe it's possible to simply add a build notice.
- BOOKKEEPER-37 Ordering of published messages is not preserved when doing asynchronous publication : asynchronous publishing is broken. Unfortunately, it's a complex issue (much more than I thought initially) , requiring quite a few changes, and my understanding is that it could be postponed to 4.1 (more focused on communications).
Matthieu On 11/23/11 9:39 PM, Ivan Kelly wrote:
Hi guys, This thread is to discuss what will be released with 4.0.0. First off, in case people are wondering what happened to 3.4.0, what was 3.4.0 is now known as 4.0.0. This is due to API changes, which we felt justified a new major version number. Now that ZooKeeper 3.4.0 is out, we can start getting a release for BookKeeper 4.0.0 together. The following JIRAs are must haves for the release. BOOKKEEPER-111 Document bookie recovery feature BOOKKEEPER-110 Review documentation BOOKKEEPER-62 Bookie can not start when encountering corrupted records BOOKKEEPER-112 Bookie Recovery on an open ledger will cause LedgerHandle#close on that ledger to fail The following are patch available at the moment, so they should be in the release also. BOOKKEEPER-39 Bookie server failed to restart because of too many ledgers (more than ~50,000 ledgers) BOOKKEEPER-117 Support multi threads in hedwig cpp client to leverage multi-core hardware BOOKKEEPER-118 Hedwig client doesn't kill and remove old subscription channel after redirection. There a final set, which are marked for 4.0.0. I haven't gone through these in detail, but I think they could all be postponed to 4.1.0 if necessary. BOOKKEEPER-53 race condition of outstandingMsgSet@SubscribeResponseHandler BOOKKEEPER-72 Fix warnings issued by FindBugs BOOKKEEPER-55 SubscribeReconnectRetryTask might retry subscription endlessly when another subscription is already successfully created previously BOOKKEEPER-56 Race condition of message handler in connection recovery in Hedwig client Comments/suggestions welcome, Ivan
