Closed sonnhotani closed 4 years ago
I found that there is a conflict between description of automatic_retries and retry_non_idempotent. automatic_retries: if retry_non_idempotent is set only GET, HEAD, PUT, DELETE, OPTIONS, and TRACE requests will be retried. https://www.elastic.co/guide/en/logstash/current/plugins-outputs-http.html#plugins-outputs-http-automatic_retries
retry_non_idempotent
retry_non_idempotent If automatic_retries is enabled this will cause non-idempotent HTTP verbs (such as POST) to be retried. https://www.elastic.co/guide/en/logstash/current/plugins-outputs-http.html#plugins-outputs-http-retry_non_idempotent
=> It should be: if retry_non_idempotent is NOT set only GET, HEAD, PUT, DELETE, OPTIONS, and TRACE requests will be retried.
Good catch ! I've been confused when reading the doc too. Can we get this merged ?
I found that there is a conflict between description of automatic_retries and retry_non_idempotent. automatic_retries: if
retry_non_idempotent
is set only GET, HEAD, PUT, DELETE, OPTIONS, and TRACE requests will be retried. https://www.elastic.co/guide/en/logstash/current/plugins-outputs-http.html#plugins-outputs-http-automatic_retriesretry_non_idempotent If automatic_retries is enabled this will cause non-idempotent HTTP verbs (such as POST) to be retried. https://www.elastic.co/guide/en/logstash/current/plugins-outputs-http.html#plugins-outputs-http-retry_non_idempotent
=> It should be: if
retry_non_idempotent
is NOT set only GET, HEAD, PUT, DELETE, OPTIONS, and TRACE requests will be retried.