style95 commented on issue #5286: URL: https://github.com/apache/openwhisk/issues/5286#issuecomment-1201815098
One thing I couldn't get it is when a lease is removed for some reason, the system is supposed to recover the lease and all data. Since the network rupture can happen at any time, the should be resilient with them. When I design the new scheduler, that was the main requirement and we had tested many times. But it seems the data is not properly recovered in your case and that's my question. Regarding the cache about the scheduler endpoint, I think that would be a good improvement. Currently, if no scheduler endpoint is found, it will just fail activations. But we can make controllers send activations and queue creation request to the scheduler side anyway(with cached endpoints as long as it is reachable), and make schedulers handle the remaining. -- 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-unsubscr...@openwhisk.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
