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 2017/11/02 16:40:05 UTC

[GitHub] tysonnorris commented on issue #2913: De-link Kafka-topic from Invoker-Id

tysonnorris commented on issue #2913: De-link Kafka-topic from Invoker-Id
URL: https://github.com/apache/incubator-openwhisk/issues/2913#issuecomment-341482607
 
 
   @ServoKvd there is a thread here: https://lists.apache.org/thread.html/bb94eb7bb9cd29b9fef2515936e031bcb36357b8ec5ec55dfc03ed26@%3Cdev.openwhisk.apache.org%3E
   
   What Markus is getting at is that regardless of which invoker an activation is routed to for the first execution of the action, subsequent executions of the same action should be routed to some invoker where the action is already running in a container (since container startup and init is relatively expensive). While I agree its possible to use unique consumer groups + partitions instead of unique toipcs, I think this will be a moot point once the scheduling is done at execution time (and flexibility of NOT using partition keys can be maintained). 
   
   Separately, there's some other issues you are adding to the mix, like "action priority" where different actions may be queued in separate topics - currently the queues (or single queue, ultimately) operate strictly as FIFO ordering, and I don't think there is a good reason to change that based on action or kind. It may be nice at some point to allow more configuration options for prewarm/warm containers, but this is a change for invokers and not the loadbalancer, I think. 

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