[fix][doc] Clarifying non-persistent topics a bit more#15720
[fix][doc] Clarifying non-persistent topics a bit more#15720Anonymitaet merged 3 commits intoapache:masterfrom
Conversation
|
@asafm:Thanks for your contribution. For this PR, do we need to update docs? |
|
@asafm:Thanks for providing doc info! |
github-actions
bot
added
the
doc
Anonymitaet
left a comment
Anonymitaet
left a comment
There was a problem hiding this comment.
Thanks for your contribution!
Does this apply to other doc versions? If so, would you like to update them?
@Anonymitaet It does but if I need to update all previous versions everytime I make a typo it will despair me :) |
@asafm just |
site2/docs/concepts-messaging.md
Outdated
|
|
||
| By default, non-persistent topics are enabled on Pulsar brokers. You can disable them in the broker's [configuration](reference-configuration.md#broker-enableNonPersistentTopics). You can manage non-persistent topics using the `pulsar-admin topics` command. For more information, see [`pulsar-admin`](https://pulsar.apache.org/tools/pulsar-admin/). | ||
|
|
||
| Currently non-persistent topics which are not partitioned are not persisted to ZK, which means if the broker owning them crashes, they won't get re-assigned to another broker because they only existed in the owner broker memory. The current work-around for that is to make sure `allowAutoTopicCreation` broker config is `true` and `allowAutoTopicCreationType` is `non-partitioned` (Those the the default values). |
There was a problem hiding this comment.
| Currently non-persistent topics which are not partitioned are not persisted to ZK, which means if the broker owning them crashes, they won't get re-assigned to another broker because they only existed in the owner broker memory. The current work-around for that is to make sure `allowAutoTopicCreation` broker config is `true` and `allowAutoTopicCreationType` is `non-partitioned` (Those the the default values). | |
| Currently, non-persistent topics which are not partitioned are not persisted to ZooKeeper, which means if the broker owning them crashes, they do not get re-assigned to another broker because they only exist in the owner broker memory. The current workaround is to set the value of `allowAutoTopicCreation` to `true` and `allowAutoTopicCreationType` to `non-partitioned` (they are default values) in broker configuration. |
There was a problem hiding this comment.
do not use ZK for ZooKeeper, spell it out
guide: https://docs.google.com/document/d/1lc5j4RtuLIzlEYCBo97AC8-U_3Erzs_lxpkDuseU0n4/edit#bookmark=id.zzzwnxsvrwb
5 participants
Modifications
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Documentation
Check the box below or label this PR directly.
Need to update docs?
doc-required(Your PR needs to update docs and you will update later)
no-need-doc(Please explain why)
doc(Your PR contains doc changes)
doc-added(Docs have been already added)