Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 11338: add documentation about the upgrade of Pulsar 2.8.0 #11392

Merged
merged 3 commits into from
Aug 11, 2021
Merged

Issue 11338: add documentation about the upgrade of Pulsar 2.8.0 #11392

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8bc86f3
Issue 11338: add documentation about the upgrade of Pulsar 2.8.0
eolivelli Jul 20, 2021
88436fc
Apply @Anonymitatet's suggestion
eolivelli Jul 22, 2021
057bd9c
add link to https://github.com/apache/pulsar/pull/10878
eolivelli Jul 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions site2/website/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,15 @@

### 2.8.0 &mdash; 2021-06-12 <a id=“2.8.0”></a>

### Update notice

Due to a breaking change in the Schema API it may happen that some Pulsar Functions or Pulsar IO Connector fail to work,
throwing an `IncompatibleClassChangeError`.
In this case you have to rebuild your Function using Apache Pulsar 2.8.0 as dependency and redeploy it.
If you are running on Kubernetes you can temporarily let the Functions Worker pod run with a previous version of Pulsar
Copy link
Contributor

@freeznet freeznet Jul 21, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my understanding, for Kubernetes users, we need to take into account the runtime which users using. If users use thread or process runtime, then they should keep functions worker pod with a previous version of Pulsar. If users use Kubernetes runtime, they should keep the functionRuntimeFactoryConfigs.functionDockerImages or functionRuntimeFactoryConfigs.pulsarDockerImageName with previous version of Pulsar in functions_worker.yml as well, because by default it will use apachepulsar/pulsar:latest.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

even this is technically possible,
it is not simple to configure this parameter in a multi tenant environment, it is practically impossible, because you have to take care of the placement of the functions for each tenant.

Also we do not guarantee (it is not stated anywhere and there is no testcase) that the 'function worke' is able to work with a more recent version of the broker or of the other components.
In practice if you upgrade from 2.7.x to 2.8.x you can keep the function pods at version Pulsar 2.7.x, but this is not something that I would recommend to the public audience, as it needs some advanced knowledge of Pulsar internals

if the default is 'apachepulsar/pulsar:latest' this is kind of a bad problem, because in this case everything may break without notice.
if you are using the official Apache Pulsar Helm Chart we are setting properly the version

does this make sense to you @freeznet ?

in order to not cause downtime.
More context in [this issue](https://github.com/apache/pulsar/issues/11338).
eolivelli marked this conversation as resolved.
Show resolved Hide resolved

#### PIPs
- [PIP 45] Pluggable metadata interface [#9148](https://github.com/apache/pulsar/pull/9148) [#9221](https://github.com/apache/pulsar/pull/9221) [#9240](https://github.com/apache/pulsar/pull/9240) [#9273](https://github.com/apache/pulsar/pull/9273) [#9274](https://github.com/apache/pulsar/pull/9274) [#9338](https://github.com/apache/pulsar/pull/9338) [#9346](https://github.com/apache/pulsar/pull/9346) [#9351](https://github.com/apache/pulsar/pull/9351) [#9412](https://github.com/apache/pulsar/pull/9412) [#9485](https://github.com/apache/pulsar/pull/9485) [#9586](https://github.com/apache/pulsar/pull/9586) [#9967](https://github.com/apache/pulsar/pull/9967) [#9973](https://github.com/apache/pulsar/pull/9973) [#10391](https://github.com/apache/pulsar/pull/10391) [#10457](https://github.com/apache/pulsar/pull/10457) [#10532](https://github.com/apache/pulsar/pull/10532) [#10545](https://github.com/apache/pulsar/pull/10545) [#10647](https://github.com/apache/pulsar/pull/10647)
- [PIP 50] Package management service [#8637](https://github.com/apache/pulsar/pull/8637) [#8680](https://github.com/apache/pulsar/pull/8680) [#8744](https://github.com/apache/pulsar/pull/8744) [#8764](https://github.com/apache/pulsar/pull/8764) [#8816](https://github.com/apache/pulsar/pull/8816) [#8817](https://github.com/apache/pulsar/pull/8817) [#8858](https://github.com/apache/pulsar/pull/8858) [#8861](https://github.com/apache/pulsar/pull/8861) [#8893](https://github.com/apache/pulsar/pull/8893) [#8907](https://github.com/apache/pulsar/pull/8907)
Expand Down