Release notes for 4.8.1

Release notes for 4.8.1

The commit to review is d09296c




Reviewers: Jia Zhai <None>, Matteo Merli <[email protected]>, Sijie Guo <[email protected]>

This closes apache#1795 from eolivelli/fix/481-release-notes

site/_config.yml

@@ -8,8 +8,9 @@ destination: local-generated
 twitter_url: https://twitter.com/asfbookkeeper
 
 versions:
-- "4.8.0"
 # [next_version_placeholder]
+- "4.8.1"
+- "4.8.0"
 - "4.7.2"
 - "4.7.1"
 - "4.7.0"

site/docs/4.8.1/overview/releaseNotes.md

@@ -2,67 +2,30 @@
 title: Apache BookKeeper 4.8.1 Release Notes
 ---
 
-This is the 13th release of Apache BookKeeper!
+This is the 14th release of Apache BookKeeper!
 
-The 4.8.1 release incorporates hundreds of bug fixes, improvements, and features since previous major release, 4.7.0.
-It is a new big milestone in Apache BookKeeper community,
-this release include great new features, like Relaxed Durability, Stream Storage service and Multiple active Entrylogs.
+The 4.8.1 release is a bugfix release which fixes a bunch of issues reported from users of 4.8.0.
 
-Apache BookKeeper/DistributedLog users are encouraged to [upgrade to 4.8.1](../../admin/upgrade). The technical details of
-this release are summarized below.
+Apache BookKeeper users who are using 4.8.0 are encouraged to upgrade to 4.8.1. The technical details of this release are summarized
+below.
 
 ## Highlights
 
-The main features in 4.8.1 are around following areas:
+- Use default metrics registry in Prometheus exporter, see [apache/bookkeeper#1765](https://github.com/apache/bookkeeper/pull/1765)
 
-- Durability
-- ExplicitLAC feature
-- New Table Storage Service
-- Bug Fixes
+- Don't cache Bookie hostname DNS resolution forever, see [apache/bookkeeper#1762](https://github.com/apache/bookkeeper/pull/1762)
 
+- Reduce stack traces in logs for common cases, see [apache/bookkeeper#1762](https://github.com/apache/bookkeeper/pull/1776)
 
-### New WriteFlag DEFERRED_SYNC
+- Ledger deletion racing with flush can cause a ledger index to be resurrected, see [apache/bookkeeper#1757](https://github.com/apache/bookkeeper/pull/1757)
 
-The writer may ask for temporary relaxed durability writes, that is to receive early acknowledge from Bookies, before an fsync() on Journal.
-Together with this new flag we introduced the new WriteHandle#force() API, this this API the writer is able to request an explicit guarantee of durability to the Bookies
-it is mostly like and explicit fsync() on a file system.
+- EntryMemTable.newEntry retains reference to passed ByteBuffer array, can cause corruption on journal replay, see [apache/bookkeeper#1737](https://github.com/apache/bookkeeper/pull/1737)
 
-See [`DEFERRED_SYNC`](../javadoc/org/apache/bookkeeper/client/api/WriteFlag) and [force()](../javadoc/org/apache/bookkeeper/client/api/ForceableHandle) for reference
 
-### New behaviour for Netty ByteBuf reference count management
+### Dependency Changes
 
-All the client side APIs which take ByteBufs now will have the net effect of decrementing by 1 the refcount.
-This is consistent with general contract of Netty.
-It is expected that the client passes the ownership of the ByteBuf to BookKeeper client.
-
-### Multiple Active Entrylogs
-
-It is now possible on the Bookie to have multiple active entry loggers,
-this new feature will help with compaction performance and some specific workloads.
-
-See [Multiple active entrylogs](https://github.com/apache/bookkeeper/issues/570)
-
-### Table Storage Service
-
-From this version we are providing the a table (key/value) service embedded in Bookies.
-
-See [BP-30: BookKeeper Table Service](https://github.com/apache/bookkeeper/issues/1205)
-
-### Make ExplicitLAC persistent
-
-ExplicitLAC was contributed from Salesforce in 4.5.0 release, but in the first release
-it was a beft-effort in-memory mechanism. Now you can configure Bookies to store durably ExplicitLAC.
-
-See [Make ExplicitLAC persistent](https://github.com/apache/bookkeeper/issues/1527)
-
-### Ensemble change on Delayed Write Failure
-
-We are handling more gracefully the case of a failure of a Bookie in spite of a succeeded write.
-If you are writing with Ack Quorum = 2 and Write Quorum = 3, writes will succeeed even if 1 of 3 Bookies fail,
-now BookKeeper will trigger an *ensemble change* and replace the failed bookie earlier.
-
-See [Ensemble change on Delayed Write Failure](https://github.com/apache/bookkeeper/issues/1390)
+There is no dependecy upgrade from 4.8.0.
 
 ## Full list of changes
 
-- [https://github.com/apache/bookkeeper/milestone/4](https://github.com/apache/bookkeeper/milestone/4?closed=1)
+- [https://github.com/apache/bookkeeper/issues?q=label%3Arelease%2F4.8.1+is%3Aclosed](https://github.com/apache/bookkeeper/issues?q=label%3Arelease%2F4.8.1+is%3Aclosed)

site/releases.md

@@ -64,6 +64,14 @@ Client Guide | API docs
 
 ## News
 
+### 22 November, 2018 Release 4.8.1 available
+
+This is the 14th release of Apache BookKeeper !
+
+The 4.8.1 release is a bugfix release which fixes a bunch of issues reported from users of 4.8.0.
+
+See [BookKeeper 4.8.1 Release Notes](../docs/4.8.1/overview/releaseNotes) for details.
+
 ### 26 September, 2018 Release 4.8.0 available
 
 This is the 13th release of Apache BookKeeper !