[BUG] Constant ~1.00 CPU utilization with docker setup

Describe the bug

OpenSearch in docker constantly hogging CPU at approximately 1.00 when started and even under no load. (this even happened when gitlab instance, which is the only client of the OpenSearch instance in my setup, is stopped)

Related component

Other

To Reproduce

1. Setup OpenSearch with the docker-compose.yml provided within Additional Details
2. Check system resources with your favoured tool (e.g. htop)
3. additionally, check system resources (again) under a circumstance that no active client is connected to the OpenSearch instance

Expected behavior

reasonably low CPU utilization when the OpenSearch instance is idle

Additional Details

Plugins Probably N/A?

Screenshots

Host/Environment (please complete the following information):

• OS: Arch Linux
• Docker: 29.7.2
• OpenSearch Image: public.ecr.aws/opensearchproject/opensearch:3

Additional context

docker-compose.yml with redacted passwords (my OpenSearch instance is setup for gitlab's advanced search)

services:
  # gitlab-ee service omitted.
  opensearch:
    image: public.ecr.aws/opensearchproject/opensearch:3
    container_name: gitlab-opensearch
    restart: unless-stopped
    volumes:
      - ./opensearch-data:/usr/share/opensearch/data
    expose:
      - 9200
      - 9600
    environment:
      - cluster.name=gitlab
      - node.name=opensearch
      - discovery.seed_hosts=opensearch
      - cluster.initial_cluster_manager_nodes=opensearch
      - bootstrap.memory_lock=true
      - plugins.security.disabled=true
      - OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m
      - OPENSEARCH_INITIAL_ADMIN_PASSWORD=REDACTED
      - plugins.security.audit.config.disabled_categories=TRANSPORT_AUDIT
    ulimits:
      nofile:
        soft: 65536
        hard: 65536
      memlock:
        soft: -1
        hard: -1