Latest revision as of 14:06, 21 December 2022

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

Reduce the Maximum Journal Size

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Reduce the amount of disk space that the journal can use, by introducing a 3 month retention limit, on top of the existing 4 GB disk space limit.

Owner

Name: chrismurphy
Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>

Current status

Targeted release: Fedora Linux 38
Last updated: 2022-12-21
FESCo issue: <will be assigned by the Wrangler>
Tracker bug: <will be assigned by the Wrangler>
Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Currently, the journal can occupy up to 4 GB of disk space. 4 GB is a lot of space to use for logs, and this has been a source of user complaints.

Limiting the journal logs to 3 months retention is primarily intended to reduce the amount of disk space used. The time-based limit also intended to set the journal limit based on the need for the data, as opposed to the more arbitrary disk space criteria.

Feedback

October 2020: systemd issue - Reduce default journal disk space size limit
January 2021: thinking journal retention limits mailing list thread
January 2021: Workstation Working Group issue
September 2022: Limiting the (systemd) journal size mailing list thread

Benefit to Fedora

Reduce the amount of disk space used for logs, thus increasing the amount of space available for other things
Reduce user complaints
A more privacy-conscious design

Scope

Proposal owners:
- Create a PR to change the systemd journal limit defaults.
- If the change isn't accepted in systemd, implement it as a downstream patch.
Other developers:
- Other developers aren't expected to be affected.
Release engineering: #Releng issue number
Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Objectives: N/A (not needed for this Change)

Upgrade/compatibility impact

How To Test

Post-release it will be useful to validate that the change has had the intended effect of reducing disk usage. This can be checked with sudo journalctl --disk-usage.

User Experience

The main user experience change will be increased disk space availability.

Dependencies

No dependencies.

Contingency Plan

Contingency mechanism: proposal owner to revert the code change if necessary.
Contingency deadline: beta freeze.
Blocks release? No.

Documentation

man journald.conf

Release Notes

@@ Line 103: / Line 103: @@
 * Proposal owners:
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-** Propose the journal limit change upstream in systemd
+** Create a PR to change the {{package|systemd}} journal limit defaults.
-** If the change isn't accepted in systemd, implement it as a downstream patch
+** If the change isn't accepted in systemd, implement it as a downstream patch.
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-** Other developers aren't expected to be affected
+** Other developers aren't expected to be affected.
 * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
@@ Line 141: / Line 141: @@
 -->
-Post-release it will be useful to validate that the change has had the intended effect of reducing disk usage. This can be checked with sudo journalctl --disk-usage.
+Post-release it will be useful to validate that the change has had the intended effect of reducing disk usage. This can be checked with <code>sudo journalctl --disk-usage</code>.
 == User Experience ==
@@ Line 155: / Line 155: @@
 -->
-Users generally shouldn't be aware of this change.
+The main user experience change will be increased disk space availability.
 == Dependencies ==
@@ Line 165: / Line 165: @@
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: proposal owner to revert the code change if necessary.
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-** Proposal owner to revert the code change if necessary.
 * Contingency deadline: beta freeze.
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->

Search

Changes/Reduce Maximum Journal Size: Difference between revisions