Joshua Jones
Joshua Jones
To elaborate further, when signing a request such as: ``` POST /some-index/_refresh?ignore_throttled=false&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true HTTP/1.1 Connection: Keep-Alive User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_232) Host: some-endpoint.us-east-1.es.amazonaws.com Accept-Encoding: gzip,deflate ``` After sending the actual signed request, the...
@debora-ito yes, this is the same issue that the user in #2078 was experiencing. However, this issue has nothing to do with the Elasticsearch Java client, as I have described...
Following is a minimum viable example that will produce an error response from the Elasticsearch service with the message "The request signature we calculated does not match the signature you...
My primary concern here, is that the algorithm used by the Java SDK `Signer` does not follow the AWS Signature Version 4 specification when the request method is "POST" and...
**Non-Blocking** The relationship between the weighted graph builder and the weighted graph is a bit odd. Currently the weighted graph has a dependency of its builder, which seems backwards. Instead...
Thank you for bringing this to our attention. We will look into what may be causing the increase in DNS lookups. A couple of things to note: > The OPENFGA_DATASTORE_CONN_MAX_IDLE_TIME...
@paulinejamin were you able to confirm that the DNS queries were for your database domain name?
@matthisholleville have you been able to confirm that connections are closing prematurely given your `OPENFGA_DATASTORE_CONN_MAX_IDLE_TIME` and `OPENFGA_DATASTORE_CONN_MAX_LIFETIME` settings? I have not yet been able to observe this behavior locally on...
@Rbillon59 thank you for that detailed analysis! I ran a similar test against version 1.8.14: ``` OPENFGA_DATASTORE_MAX_OPEN_CONNS=20 OPENFGA_DATASTORE_MAX_IDLE_CONNS=20 OPENFGA_DATASTORE_CONN_MAX_IDLE_TIME=600s OPENFGA_DATASTORE_CONN_MAX_LIFETIME (not set) ``` I observed my connections being reused appropriately...
@Rbillon59 thank you for running your tests against `v1.8.16`. We will continue to work on developing tests that can reproduce this issue in `v1.8.14` so that we can catch potential...