chetanmeh commented on issue #3858: Compute stable id for controller
URL: 
https://github.com/apache/incubator-openwhisk/issues/3858#issuecomment-404046183
 
 
   @markusthoemmes From what In understand even Invokers currently not have 
very stable ids. So there are two parts to problem
   
   ### Controller Stable Id
   
   Here requirement is that current approach may lead to orphan topics in Kafka 
if controller restarts and chooses a new id for every run. So here we either go 
for stable id or have a way in Kafka to expire topics which do not see some 
activity after some time
   
   ### Invoker Stable Id
   
   Currently Invokers make use of `--name` parameter to be provided a unique 
name which is then used to find a mapping id from zookeeper. The problem (at 
least for Mesos) is that there is no stable unique name parameter value to use. 
One can use the host ip but then it would vary if the next restart leads to  
container being placed on different host.
   
   Looking at [kube][1] setup it looks like it is using [StatefulSet][2] to 
keep stable id across restarts. So for Mesos we can also use similar 
[Persistent Volume][3] 
   
   However I am not sure if using stateful feature of container runtime should 
be the way to go as it would cause issue in case that node gives a problem or 
goes offline. In such a case invoker would be started on a new node and that 
would cause the topic to become orphan leaving activations present in  it 
unprocessed.
   
   Hence the search for newer approach
   
   [1]: 
https://github.com/apache/incubator-openwhisk-deploy-kube/blob/489ce8e90abf3bc411f8dd7087d42916c8a004be/helm/openwhisk/templates/invoker.yaml#L99
   [2]: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
   [3]: https://mesosphere.github.io/marathon/docs/persistent-volumes.html

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to