[GitHub] [openwhisk] style95 commented on pull request #5110: [New Scheduler] Add memory queue for the new scheduler

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

style95 commented on pull request #5110:
URL: https://github.com/apache/openwhisk/pull/5110#issuecomment-878037782


   > One comment on the persistence nature of the queue. I think queueing with kafka doesn't add anything to openwhisk if openwhisk does not provide at least once guarantee of activation execution. It's unnecessary overhead to queue up through kafka if the activation can get lost elsewhere anyways.
   
   Agree.
   
   I think the immediate next step could be removing Kafka from the critical path completely as currently, container creation messages and activation messages from controller to scheduler are delivered through Kafka.
   
   
   > This queue is designed in a way that activations are not persistent.
   But it could be improved in the future by taking a similar approach with what Kafka does.
   
   I mentioned above that if we really need to support the at-least-once semantic, we can consider this approach.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org