New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StorageExtension is not safe with multiple Gateways #528
Comments
I wish the storage extension was stateless. |
As an idea: we can make use of context to store state |
Or one StorageExtension instance per Gateway instance |
This is the way to go, but I personally consider it as workaround as the service still has a state which is bad imho |
Hm, giving it one more thought I do not think there must not be any problems. The storage extension is only keeping the array of models scheduled for update. And the array is emptied on the last postExecute. |
For my use case it was be solved with #529 because I had two instances of the same gateway name. But it might still be an issue if you trigger |
There is only one
StorageExtension
instance per Model which is used in all Gateway instances. TheStorageExtension
keeps the Action Stack Level internally but this only works reliable when used with only one Gateway Instance. This leads to very unexpected behaviour.Example
The text was updated successfully, but these errors were encountered: