-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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.
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
Conversation
d5fd462
to
8bc86f3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution!
site2/website/release-notes.md
Outdated
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 |
There was a problem hiding this comment.
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
.
There was a problem hiding this comment.
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 ?
@Anonymitaet Stable version could use production environment wish recommended,It is better to have installation and deployment documentation in Chinese,many thanks,Technical documentation little sister |
Co-authored-by: Anonymitaet <[email protected]>
@freeznet @Anonymitaet PTAL again, |
1 similar comment
@freeznet @Anonymitaet PTAL again, |
Fixes #11338.
Add a note in the "Release notes" about how to fix the IncompatibleClassChange.