[branch-2.6] update to stable version of bk 4.11.1 - #8604
Merged
Conversation
sijie
approved these changes
Nov 18, 2020
sijie
requested changes
Nov 18, 2020
sijie
left a comment
sijie
left a comment
Member
There was a problem hiding this comment.
Let's make sure the branch-2.6 is able to build
Member
Author
|
doing the cherry-pick for #8270 |
changed the lience file for branch-2.6 Motivation Upgrade Apache BookKeeper client to version 4.11.1 and RocksDB to 6.10.2 (needed by Bookie) Modifications Upgrade Apache BookKeeper client, fix a few build errors, due to the introduction of BookieServiceInfo structure (see BP-38). Verifying this change This change is already covered by existing tests * Upgrade Apache BookKeeper to 4.11.1 * fix build * fix LICENSE files * Use BK 4.11.1 * Upgrade RocksDB to 6.10.2 * Fix license and upgrade maven assembly plugin * update license * restore bouncy castle license * fix licenses * Exclude BouncyCastle inherited from BK Co-authored-by: Enrico Olivelli <enrico.olivelli@diennea.com> Co-authored-by: Enrico Olivelli <eolivelli@apache.org>(cherry picked from commit 465964b)
jiazhai
force-pushed
the
update_bk_4111
branch
from
November 18, 2020 10:04
c899fa6 to
1a37f3a
Compare
codelipenghui
approved these changes
Nov 18, 2020
|
how to upgrade apache pulsar 2.6.1 version to 2.7.0 without losing any data |
Contributor
|
@vishnuvardhanp4 If you just upgrade the broker, I think this will not lose any data. If you want to upgrade the bookkeeper too, you can do like followings:
|
|
I am new to Apache pulsar .I am using apache pulsar standalone 2.6.1
version so iwant to upgrade it to 2.7.0 how to do it can u tell in detail
along with commands
…On Thu, 4 Mar 2021, 6:25 pm lipenghui, ***@***.***> wrote:
@vishnuvardhanp4 <https://github.com/vishnuvardhanp4> If you just upgrade
the broker, I think this will not lose any data. If you want to upgrade the
bookkeeper too, you can do like followings:
1. Disable the auto-recovery to prevent the not necessary data
replication during the bookkeeper upgrade.(bin/bookkeeper shell
autorecovery -disable)
2. Upgrade the bookies one by one(after one upgraded, check the
bookies works as expected, can write data and read data)
3. After all bookies upgraded, enabled the auto-recovery(bin/bookkeeper
shell autorecovery -enable)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8604 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASXOGZJISUYDHLHLPCQ2733TB57K5ANCNFSM4TZQIP7A>
.
|
Contributor
|
For the standalone mode, you just need to replace the lib directory with the new lib directory of 2.7.0 and then restart the server. You can use a separate environment to verify. Before replacing, you can backup the old lib directory. |
|
Then is my old data will be safe ? And also need to upgrade bookkeper ?
Thanks in advance
…On Fri, 5 Mar 2021, 6:01 am lipenghui, ***@***.***> wrote:
For the standalone mode, you just need to replace the lib directory with
the new lib directory of 2.7.0 and then restart the server. You can use a
separate environment to verify. Before replacing, you can backup the old
lib directory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8604 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASXOGZPE6IB2ALXXTJ5MNWTTCAQ47ANCNFSM4TZQIP7A>
.
|
Contributor
|
Yes, the data will be safe. The standalone contains the broker and bookkeeper, so the bookkeeper will also upgrade when you upgrade the standalone. |
|
Awesome, thanks!
can u tell me how can i get to know that pulsar standalone is upgraded to
2.7.0 ?
…On Fri, Mar 5, 2021 at 8:42 AM lipenghui ***@***.***> wrote:
Yes, the data will be safe. The standalone contains the broker and
bookkeeper, so the bookkeeper will also upgrade when you upgrade the
standalone.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8604 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASXOGZKBPHYCUZOKMWMDHL3TCBDZBANCNFSM4TZQIP7A>
.
|
|
after replacing lib and started facing below error
ERROR org.apache.bookkeeper.bookie.Bookie - Cookie for this bookie is not
stored in metadata store. Bookie failing to come up
INSTANCEID not exists in zookeeper. Not considering it for data verification
ERROR org.apache.pulsar.PulsarStandaloneStarter - Failed to start pulsar
service.
On Fri, Mar 5, 2021 at 9:46 AM Vishnu Vardhan <vishnuvardhanp4@gmail.com>
wrote:
… Awesome, thanks!
can u tell me how can i get to know that pulsar standalone is upgraded to
2.7.0 ?
On Fri, Mar 5, 2021 at 8:42 AM lipenghui ***@***.***> wrote:
> Yes, the data will be safe. The standalone contains the broker and
> bookkeeper, so the bookkeeper will also upgrade when you upgrade the
> standalone.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#8604 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASXOGZKBPHYCUZOKMWMDHL3TCBDZBANCNFSM4TZQIP7A>
> .
>
|
Contributor
|
If you are using pulsar standalone for development and you can lose your data you can erase the |
|
Using it in production.data should not be loose .is there any other
scenario to solve this issue .please help me out of this
Why the error is showing
…On Sat, 6 Mar 2021, 9:17 pm Enrico Olivelli, ***@***.***> wrote:
If you are using pulsar standalone for development and you can lose your
data you can erase the data directory and start from scratch
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8604 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASXOGZKOCPAPRY4K6RF2LP3TCJE77ANCNFSM4TZQIP7A>
.
|
Contributor
|
@vishnuvardhanp4 can you please paste more logs ? Side note: |
Contributor
|
can you please also create a dedicated ticket "issue", this way we can follow up the discussion about your case |
|
Sure, will do that.
…On Mon, Mar 8, 2021 at 4:31 PM Enrico Olivelli ***@***.***> wrote:
can you please also create a dedicated ticket "issue", this way we can
follow up the discussion about your case
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8604 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASXOGZJGY6BD6E53NNFSVUTTCSU7PANCNFSM4TZQIP7A>
.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It would be great to update branch-2.6 to a stable version of bk. so some issues could be fixed.
e.g. apache/bookkeeper#2333