vvraskin commented on issue #2859: LoadBalancerService does not consider concurrent requests when scheduling URL: https://github.com/apache/incubator-openwhisk/issues/2859#issuecomment-337006404 Good catch. I will try to reproduce it later, but I think you are right, the fact that we read async, doesn't allow us to see the update by the second call of `schedule`. Since we only write to the local instances, we could consider changing read to be synchronous, need to measure the performance overhead though. According to akka doc the use case you are showing should be supported: > You will always read your own writes. For example if you send a Update message followed by a Get of the same key the Get will retrieve the change that was performed by the preceding Update message. ---------------------------------------------------------------- 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
