Raspberry Pi / CPU frequency remains maxed out after influx TSM compacting job

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. every day when InfluxDB compacts the InfluxDB logs the CPU frequency of my Raspberry Pi is at maximum and not returning to lower level until reboot of device

__Expected behavior:__
CPU behaviour should return to normal levels after compacting job.

__Actual behavior:__
Once the TSM compacting job is started around 5am, the utilisation goes up and causing high CPU frequency which remains on highest level

__Environment info:__

* System info: Linux 5.10.17-v7l+ armv7l
* InfluxDB version: InfluxDB v1.8.4 (git: 1.8 bc8ec4384eed25436d31045f974bf39f3310fa3c)
* Other relevant environment details: no docker

__Logs:__
Include snippet of errors in log.

Reproduce the scheduled InfluxDB TSM compaction on the stated Raspberry Pi environment and observe CPU utilization and frequency before, during, and after the job. Review the available screenshots and collect the missing log details; done means the CPU frequency returns to normal after compaction without rebooting the device.

Written by the indexing model from the issue text.