Skip to content

Commit

Permalink
Clarify non-permanent error handling in receiver/doc.go (#7476)
Browse files Browse the repository at this point in the history
See discussion here #7459 (comment)

It is expected that the receivers should always retry, not just that they may retry.
  • Loading branch information
tigrannajaryan authored Apr 3, 2023
1 parent b1426af commit 1c47d89
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion receiver/doc.go
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
// receiving protocol allows to do that. In case of OTLP/HTTP for example, this means
// that HTTP 400 response is returned to the sender.
//
// If the error is non-Permanent then the nextConsumer.Consume*() call may be retried
// If the error is non-Permanent then the nextConsumer.Consume*() call should be retried
// with the same data. This may be done by the receiver itself, however typically it is
// done by the original sender, after the receiver returns a response to the sender
// indicating that the Collector is currently overloaded and the request must be
Expand Down

0 comments on commit 1c47d89

Please sign in to comment.