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.

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

Double block storage on kafka machines #6451

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

gherceg
Copy link
Contributor

@gherceg gherceg commented Dec 16, 2024

There was an increase in case load on staging due to some testing, and the kafka machines do not have enough disk to handle it. I think this small increase should be enough to handle the additional load (trying to be conservative since it is annoying to downsize).

Environments Affected

Staging

@@ -253,7 +253,7 @@ servers:
volume_encrypted: yes
volume_type: "gp3"
block_device:
volume_size: 5
volume_size: 10
Copy link
Contributor

Choose a reason for hiding this comment

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

Are you aware if log rotation is enabled on these machines?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This block storage is solely for kafka data (/opt/data/) whereas kafka logs are in /var/log/kafka, so I don't think that was the issue here. I don't know the details of kafka's log rotation, but it looks like we have a default of 28 days (kafka_log_retention) so I would guess that the answer is still that log rotation is enabled on staging.

@gherceg gherceg merged commit db25218 into master Dec 16, 2024
2 checks passed
@gherceg gherceg deleted the gh/staging/increase-kafka-disk branch December 16, 2024 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants