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

[GitBox <gi...@apache.org>]

jberstler commented on issue #234: requeue messages to kafka if subject is throttled
URL: https://github.com/apache/incubator-openwhisk-package-kafka/issues/234#issuecomment-352766207
 
 
   @rabbah Could you elaborate on what you mean by requeue the message? It sounds like you are suggesting that we produce the message back to kafka, but this could have all kinds of unintended consequences - keeping in mind the kafka instance being consumed is owned/operated by the trigger owner, not by the feed provider.
   
   If instead you mean to requeue firing the trigger until a later time, I'm not sure how this is better than simply extending the retry period. In this sense, I assume you mean that the provider should attempt to consume the next message in the queue and try to fire a trigger for that message instead, eventually coming back to the original "requeued" message at a later time. However, if the trigger URL is not responding correctly, I don't think that moving on to the next message in the topic will have any better results, as the problem won't be the content of the trigger payload. Even if the problem were the payload content, coming back to fire that message again still wouldn't work as the content would not have changed.
   
   Of course, there is always the possibility that I completely misunderstood your suggestion, and you intend something different from the above two options :smile: 

----------------------------------------------------------------
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