You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/01/31 03:23:31 UTC

[GitHub] abaruni commented on issue #234: requeue messages to kafka if subject is throttled

abaruni commented on issue #234: requeue messages to kafka if subject is throttled
URL: https://github.com/apache/incubator-openwhisk-package-kafka/issues/234#issuecomment-361811832
 
 
   What @csantanapr said is correct. There wouldn't really be a need to requeue records. That data would be persisted for enough time to handle any throttling. Furthermore, a consumer is reading from exactly one topic and firing exactly one trigger. So, if that trigger encounters any 429 responses and we requeue, then the next trigger fire for the next batch of messages will likely also return a 429. We would not see any difference between a requeue and doing a no-op and polling once again. i.e. not committing offsets

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services