Closed Bug 1990765 Opened 14 days ago Closed 14 days ago

clean up kafka logs on hgweb nodes

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jcristau, Assigned: jcristau)

Details

Attachments

(1 file)

Bug 1896189 added a daily timer to run find /var/log/zookeeper /var/log/kafka -mtime +7 -delete.
That appears to run and work on the kafka nodes, but for some reason not on hgweb*, where we still have log files going back to 2018.

OK I think I see what happened. The new timer was enabled but not started, and we haven't rebooted the hgweb nodes (which would have started it) since then. I've manually started it now so the command should run at 00:00Z from now on.

Assignee: nobody → jcristau
Status: NEW → RESOLVED
Closed: 14 days ago
Resolution: --- → FIXED

Also did a one-off systemctl start kafka-logs-cleanup.service on hgweb4 to clear the nagios alert.

Avoid requiring a reboot before we start cleaning up logs.

Reopening to track the ansible fix.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Pushed by jcristau@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/1b3aee022f08
kafka-broker: make sure the log cleanup timer is started r=sheehan

Status: REOPENED → RESOLVED
Closed: 14 days ago14 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: