[GitHub] eolivelli closed pull request #1568: ISSUE #1565: Update 'upgrade' doc for 4.8 release

[GitBox <gi...@apache.org>]

eolivelli closed pull request #1568: ISSUE #1565: Update 'upgrade' doc for 4.8 release
URL: https://github.com/apache/bookkeeper/pull/1568
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/site/docs/latest/admin/upgrade.md b/site/docs/latest/admin/upgrade.md
index 0b29c8a5cc..57c6520813 100644
--- a/site/docs/latest/admin/upgrade.md
+++ b/site/docs/latest/admin/upgrade.md
@@ -51,7 +51,7 @@ In a rolling upgrade scenario, upgrade one Bookie at a time. In a downtime upgra
 
 For each Bookie:
 
-1. Stop the bookie. 
+1. Stop the bookie.
 2. Upgrade the software (either new binary or new configuration)
 2. Start the bookie.
 
@@ -154,11 +154,14 @@ The default values of following settings are changed since 4.7.0.
 |------|-------------------|-------------------|-------|
 | enableDigestTypeAutodetection | false | true | Autodetect the digest type and passwd when opening a ledger. It will ignore the provided digest type, but still verify the provided passwd. |
 
+### 4.7.x to 4.8.X upgrade
+
+In 4.8.x a new feature is added to persist explicitLac in FileInfo and explicitLac entry in Journal. (Note: Currently this feature is not available if your ledgerStorageClass is DbLedgerStorage, ISSUE #1533 is going to address it) Hence current journal format version is bumped to 6 and current FileInfo header version is bumped to 1. But since default config values of 'journalFormatVersionToWrite' and 'fileInfoFormatVersionToWrite' are set to older versions, this feature is off by default. To enable this feature those config values should be set to current versions. Once this is enabled then we cannot rollback to previous Bookie versions (4.7.x and older), since older version code would not be able to deal with explicitLac entry in Journal file while replaying journal and also reading Header of Index files / FileInfo would fail reading Index files with newer FileInfo version. So in summary, it is a non-rollbackable feature and it applies even if explicitLac is not being used.
+
 ### 4.5.x to 4.6.x upgrade
 
 There isn't any protocol related backward compabilities changes in 4.6.x. So you can follow the general upgrade sequence to upgrade from 4.5.x to 4.6.x.
 
-
 ### 4.4.x to 4.5.x upgrade
 
 There isn't any protocol related backward compabilities changes in 4.5.0. So you can follow the general upgrade sequence to upgrade from 4.4.x to 4.5.x.
@@ -170,4 +173,3 @@ However, we list a list of things that you might want to know.
     to take a bookie out and recover it if you want to rollback to 4.4.x.
 
 If you are planning to upgrade a non-secured cluster to a secured cluster enabling security features in 4.5.0, please read [BookKeeper Security](../../security/overview) for more details.
-


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services