You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Retry exporter helper does not have requeuingEnabled=true when in-memory queue is used. This results in data being dropped after after 5mins of retries (in default configuration).
What are the reasons why we think this is the right setting for the persistent queue but a wrong setting for the in-memory queue?
The text was updated successfully, but these errors were encountered:
I'm not sure about the necessity of this option. If the backend is unavailable for a long time, the collector will be blocked and memory will never be freed. Maybe we should better propose what's being implemented in #7098 instead?
tigrannajaryan
changed the title
In-memory QueuedRetry exporter helper must use requeuingEnabled=true
Should in-memory QueuedRetry exporter helper use requeuingEnabled=true?
Apr 3, 2023
As part of #8382, the decision was made to remove the re-enquiring capability and rely on the back-off retry mechanism only. So the issue is not relevant anymore.
Retry exporter helper does not have
requeuingEnabled=true
when in-memory queue is used. This results in data being dropped after after 5mins of retries (in default configuration).What are the reasons why we think this is the right setting for the persistent queue but a wrong setting for the in-memory queue?
The text was updated successfully, but these errors were encountered: