Daniel (dB.) Doubrovkine

> I think it is ready, but how do I run the CI tests? They should have kicked off. Not sure why they aren't 🤔 Either way this is a...

@ajleong623 I clicked the approve button, iterate to 🟢 , will keep doing that

@epugh @ajleong623 I am still not clear on whether CI will start suddenly failing with a future build of OpenSearch 3.1. The Dockerfile uses `opensearchstaging/opensearch:3.1.0` which is a moving target,...

> Is that the right approach with using a fixed sha? Yes, this looks better now.

[[Catch All Triage](https://github.com/opensearch-project/.github/blob/main/TRIAGING.md) - [1](https://github.com/dblock), [2](https://github.com/reta), [3](https://github.com/andrross/), [4](https://github.com/krisfreedain), [5](https://github.com/amistrn)]

May not be actually a leak, these processes may try to use all the memory they have. Does it eventually run out of memory in your case?

This will need to be debugged, I suggest walking the [SSL setup code](https://github.com/opensearch-project/logstash-output-opensearch/blob/4221dffef4c1d9fd5ded5ae726ef2874fdd9ba5b/lib/logstash/outputs/opensearch/http_client_builder.rb#L122) and seeing how it tries to use the store/key. If you need a way to code from...

I bet there's some time-based criteria in addition to batch size. Care to dig into the implementation to see how it's deciding to send the data? Documenting it would be...

I would start by getting a call stack for the exception, it will show you where the error comes from.

Looks like Sigv4 signing doesn't know how to handle compressed content. This is in the call stack: ``` "RUBY.sign_aws_request(/usr/share/logstash/vendor/bundle/jruby/3.1.0/gems/logstash-output-opensearch-2.0.3-java/lib/logstash/outputs/opensearch/http_client/manticore_adapter.rb:212)" ``` Needs an implementation.