Cleanup in Elastic?

[mrsombre]

I see elastic variables are commented out https://github.com/reportportal/service-jobs/blob/develop/src/main/resources/application.yml#L48, but there are also some logic to cleanup elastic.
Is it not working yet or just not could be changed using environment variables?

[mrsombre]

After conducting several tests, I discovered that the queue in RabbitMQ is not being consumed by the jobs service unless there is a configuration set for Elasticsearch. This can be verified by referring to the SaveLogMessageJob.java file (see SaveLogMessageJob.java, Line 17).
Therefore, it is crucial to define the necessary environment variables in Docker.

      RP_ELASTICSEARCH_HOST: http://${ELASTIC_HOST}:${ELASTIC_PORT}
      RP_ELASTICSEARCH_USERNAME: ${ELASTIC_USERNAME}
      RP_ELASTICSEARCH_PASSWORD: ${ELASTIC_PASSWORD}

It is also important to note that the names of the Elasticsearch environment variables differ from those used in the API. Specifically, they use the prefix 'RP_ELASTICSEARCHLOGMESSAGE_'. Moreover, the variable 'RP_ELASTICSEARCH_HOST' should be specified in the format of 'scheme://host:port'. This is in contrast to the API configuration, where the host and port are separated into distinct variables.
If not configured correctly, the queue may become overloaded, consuming excessive disk space. Additionally, Elasticsearch indexes will not be created under these circumstances.