You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/11/18 05:50:48 UTC
[GitHub] [pulsar] jiazhai opened a new pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
jiazhai opened a new pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604
It would be great to update branch-2.6 to a stable version of bk. so some issues could be fixed.
e.g. https://github.com/apache/bookkeeper/pull/2333
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] codelipenghui commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
codelipenghui commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-791119314
Yes, the data will be safe. The standalone contains the broker and bookkeeper, so the bookkeeper will also upgrade when you upgrade the standalone.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] codelipenghui commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
codelipenghui commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-790597053
@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`)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] vishnuvardhanp4 commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
vishnuvardhanp4 commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-790828699
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, <no...@github.com> 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
> <https://github.com/apache/pulsar/pull/8604#issuecomment-790597053>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASXOGZJISUYDHLHLPCQ2733TB57K5ANCNFSM4TZQIP7A>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] eolivelli commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
eolivelli commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-792675269
can you please also create a dedicated ticket "issue", this way we can follow up the discussion about your case
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] codelipenghui commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
codelipenghui commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-791053508
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.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] vishnuvardhanp4 commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
vishnuvardhanp4 commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-791921287
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 <vi...@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 <no...@github.com> 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
>> <https://github.com/apache/pulsar/pull/8604#issuecomment-791119314>, or
>> unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ASXOGZKBPHYCUZOKMWMDHL3TCBDZBANCNFSM4TZQIP7A>
>> .
>>
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] vishnuvardhanp4 commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
vishnuvardhanp4 commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-792685339
Sure, will do that.
On Mon, Mar 8, 2021 at 4:31 PM Enrico Olivelli <no...@github.com>
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
> <https://github.com/apache/pulsar/pull/8604#issuecomment-792675269>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASXOGZJGY6BD6E53NNFSVUTTCSU7PANCNFSM4TZQIP7A>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] jiazhai commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
jiazhai commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-729534452
doing the cherry-pick for #8270
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] vishnuvardhanp4 commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
vishnuvardhanp4 commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-791998330
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, <no...@github.com>
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
> <https://github.com/apache/pulsar/pull/8604#issuecomment-791975005>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASXOGZKOCPAPRY4K6RF2LP3TCJE77ANCNFSM4TZQIP7A>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] eolivelli commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
eolivelli commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-791975005
If you are using pulsar standalone for development and you can lose your data you can erase the `data` directory and start from scratch
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] eolivelli commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
eolivelli commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-792674806
@vishnuvardhanp4 can you please paste more logs ?
"Failed to start pulsar" is not enough.
Side note:
Usually people use "standalone" for development, because with a single node you do not have fault tolerance.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] codelipenghui merged pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
codelipenghui merged pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] vishnuvardhanp4 commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
vishnuvardhanp4 commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-791140450
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 <no...@github.com> 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
> <https://github.com/apache/pulsar/pull/8604#issuecomment-791119314>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASXOGZKBPHYCUZOKMWMDHL3TCBDZBANCNFSM4TZQIP7A>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] vishnuvardhanp4 commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
vishnuvardhanp4 commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-791090981
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, <no...@github.com> 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
> <https://github.com/apache/pulsar/pull/8604#issuecomment-791053508>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASXOGZPE6IB2ALXXTJ5MNWTTCAQ47ANCNFSM4TZQIP7A>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
[GitHub] [pulsar] vishnuvardhanp4 commented on pull request #8604: [branch-2.6] update to stable version of bk 4.11.1
Posted by GitBox <gi...@apache.org>.
vishnuvardhanp4 commented on pull request #8604:
URL: https://github.com/apache/pulsar/pull/8604#issuecomment-790549364
how to upgrade apache pulsar 2.6.1 version to 2.7.0 without losing any data
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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