The incluxdb2.1.1 virtual machine with 32g memory will normally use only about 3G, but the entire virtual machine memory will be used up after a few hours, resulting in restart

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

1. ...
2. ...
3. ...

Expected behavior:
Describe what you expected to happen.

Actual behavior:
Describe What actually happened.

Environment info:

• System info: Run uname -srm and copy the output here
• InfluxDB version: Run influxd version and copy the output here
• Other relevant environment details: Container runtime, disk info, etc

Config:
Copy any non-default config values here or attach the full config as a gist or file.

Logs:
Include snippet of errors in log.

Performance:
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.

# Commands should be run when the bug is actively happening.
# Note: This command will run for ~30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=30s"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz` and `iostat.txt` output files.

Start by requesting the missing reproduction steps, InfluxDB version, system and environment details, configuration, logs, and performance outputs listed in the issue. No source files, tests, or entry points are named, so the memory-growth cause and completion criteria cannot be determined from the report alone.