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/10/18 19:47:21 UTC

[GitHub] dgrove-oss opened a new issue #2874: explore using zookeeper as persistent store for dynamic invokerId assignment

dgrove-oss opened a new issue #2874: explore using zookeeper as persistent store for dynamic invokerId assignment
URL: https://github.com/apache/incubator-openwhisk/issues/2874
 
 
   After thinking about the dev-list discussion on degrees of persistent stores for the OpenWhisk control plane [1], I think redis is not sufficient for the state for invokerIds.  We really want the assignment of ids to survive pretty much any partial failure of the control plane.  So zookeeper is the best match in terms of the persistence levels it support.  The interactions with the store happen only once per invoker instance during its startup, so we can afford the higher latency of zookeeper.   
   
   This issue is to track using zookeeper instead of redis to store the mapping from invoker names to invoker ids and the counter for the next available invoker id.
   
   [1]  http://mail-archives.apache.org/mod_mbox/incubator-openwhisk-dev/201710.mbox/%3CC10A4CFB-F08B-45D9-A98F-C1150AD465DF%40adobe.com%3E

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