This is an automated email from the ASF dual-hosted git repository.
eolivelli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git
The following commit(s) were added to refs/heads/master by this push:
new fe26690 ISSUE #1565: Update 'upgrade' doc for 4.8 release
fe26690 is described below
commit fe266906c83b38d25a575fd8f745556e132e4349
Author: cguttapalem <[email protected]>
AuthorDate: Mon Jul 30 08:44:26 2018 +0200
ISSUE #1565: Update 'upgrade' doc for 4.8 release
Descriptions of the changes in this PR:
Update 'upgrade' doc by adding an entry
"4.7.x to 4.8.0 upgrade" for ExplicitLac persistence
Master Issue: #1565
Author: cguttapalem <[email protected]>
Reviewers: Enrico Olivelli <[email protected]>, Sijie Guo
<[email protected]>
This closes #1568 from reddycharan/upgradenote, closes #1565
---
site/docs/latest/admin/upgrade.md | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/site/docs/latest/admin/upgrade.md
b/site/docs/latest/admin/upgrade.md
index 0b29c8a..57c6520 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 [...]
+
### 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.
-
