Unclosed session error with Data extraction service

Elastic Search
,
1

Hi, I’m running a AWS S3 connector (8.17.1) and extraction service (0.3.5) Docker containers.

After sync job I see this warning:

Unclosed client session

client_session: <aiohttp.client.ClientSession object at 0x714eb0be3010>

Unclosed connector

connections: ['deque([(<aiohttp.client_proto.ResponseHandler object at 0x714ea27c5080>, 2113.61946645)])']

connector: <aiohttp.connector.TCPConnector object at 0x714eb013e150>

These appear after the ingestion process finishes. I am trying to determine whether this is a known issue in elastic code or my configuration is contributing to the problem.

This is my docker-compose and configuration

File docker-compose.yaml

  s3-connector:
    depends_on:
      elasticsearch:
        condition: service_healthy
    image: docker.elastic.co/integrations/elastic-connectors:8.17.1
    container_name: s3-connector
    env_file:
      - ${ES_LOCAL_ENV_FILE}
    volumes:
      - ./elastic-connectors:/s3config
    command: ["/app/bin/elastic-ingest", "-c", "/s3config/s3config.yml"]
    restart: unless-stopped  
  extraction-service:
    depends_on:
      elasticsearch:
        condition: service_healthy
    image: docker.elastic.co/integrations/data-extraction-service:0.3.5
    container_name: extraction-service
    ports:
      - 8090:8090
    volumes:
      - ./elastic-connectors/files:/app/files
    env_file:
      - ${ES_LOCAL_ENV_FILE}
    restart: unless-stopped

File s3config.yaml:

connectors:
-
  connector_id: "${S3CONFIG_CONNECTOR_ID}"
  service_type: "s3"

extraction_service:
  host: http://host.docker.internal:${ES_LOCAL_EXTRACTION_PORT} #8090
  timeout: 30
  use_file_pointers: false
  stream_chunk_size: 65536
  shared_volume_dir: '/app/files'

elasticsearch:
  host: "http://host.docker.internal:${ES_LOCAL_PORT}" #9200
  username: "${ES_LOCAL_USERNAME}"
  password: "${ES_LOCAL_PASSWORD}"
  log_level: INFO
  request_timeout: 120
  max_wait_duration: 60
2

Hi,

This error was there for a bit due to the way how job scheduling/execution was happening in the service.

I believe it should be fixed in later versions, so if you can upgrade it is likely going to disappear.

If not, it should not practically impact you other than emitting the warning logs. Or do you see any problems that are connected to this error message?

3

Thank you, I think I will upgrade to the latest version later, it didn't cause any unexpected behaviour and worked fine so I think it's ok for now.