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

Jump to bottom

Improve documentation around disk space usage #8595

Merged
merged 1 commit into from
Nov 19, 2020
Merged

Improve documentation around disk space usage #8595

merged 1 commit into from
Nov 19, 2020

Conversation

kellyfj
Copy link
Contributor

@kellyfj kellyfj commented Nov 17, 2020

Motivation:

  • Figuring out how disk space is consumed by Pulsar is complex

Modifications

  • Clarified that retention policies are on a per-topic basis
  • Created entry in the FAQ on how to debug disk space issues (will need some help on this)

Verifying this change

Just a documentation change

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

  • Dependencies (does it add or upgrade a dependency): no
  • The public API: no
  • The schema: no
  • The default values of configurations: no
  • The wire protocol: no
  • The rest endpoints: no
  • The admin cli options: no
  • Anything that affects deployment: no

Documentation

  • Does this pull request introduce a new feature? no
  • If yes, how is the feature documented? not applicable
  • If a feature is not applicable for documentation, explain why? Just doc change
  • If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@kellyfj kellyfj force-pushed the improve_docs_around_disk_space_usage branch from eb4d8e2 to 1d7e065 Compare November 17, 2020 19:33
Jennifer88huang-zz
Jennifer88huang-zz reviewed Nov 19, 2020
View reviewed changes
faq.md
@@ -270,4 +270,9 @@ Since the VM has lot of RAM you can increase a lot from the defaults and leave t
### When there are multiple consumers for a topic, the broker reads once from bookies and send them to all consumers with some buffer? or go get from bookies all the time for each consumers ?
In general, all dispatching is done directly by broker memory. We only read from bookies when consumer are falling behind.


### My bookies ledgers are running out of disk space? How can I find out what went wrong
TBD
Copy link
Contributor

Choose a reason for hiding this comment

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

  1. do we add "TBD" in our docs?
  2. It's a long time we do not maintain this faq file.

@Jennifer88huang-zz Jennifer88huang-zz added doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. component/topic-policy labels Nov 19, 2020
@Jennifer88huang-zz Jennifer88huang-zz added this to the 2.7.0 milestone Nov 19, 2020
@sijie sijie merged commit 3e07468 into apache:master Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sijie sijie sijie approved these changes

@Jennifer88huang-zz Jennifer88huang-zz Jennifer88huang-zz approved these changes

Assignees

@kellyfj kellyfj

Labels
doc Your PR contains doc changes, no matter whether the changes are in markdown or code files.
Projects
None yet
Milestone
2.7.0
Development

Successfully merging this pull request may close these issues.
3 participants
@kellyfj @sijie @Jennifer88huang-zz