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
Don't automatically add env life assertions to txns #2801
Conversation
...to environ.go in preparation for env life assert fix.
To be used to evaluate if a txn aborted because of the environment life assertion.
Environment life is only asserted for top level machines, not containers. Containers will get cleaned up anyway once the host machine is killed.
This was creating a signficant performance bottleneck as almost all txns were being serialised on the environment document.
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Build failed: Tests failed |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
Don't automatically add env life assertions to txns The multiEnvRunner will no longer automatically add assertions on environment life to transactions as this create a serious performance bottleneck. Instead, the env is asserted to be alive in specific key areas (mainly where a txn may result in provisioning of resources). Fixes LP #1474195 (Review request: http://reviews.vapour.ws/r/2180/)
Don't automatically add env life assertions to txns This is a forward port of #2801, fixing LP #1474195. The multiEnvRunner will no longer automatically add assertions on environment life to transactions as this create a serious performance bottleneck. Instead, the env is asserted to be alive in specific key areas (mainly where a txn may result in provisioning of resources). (Review request: http://reviews.vapour.ws/r/2231/)
The multiEnvRunner will no longer automatically add assertions on environment life to transactions as this create a serious performance bottleneck. Instead, the env is asserted to be alive in specific key areas (mainly where a txn may result in provisioning of resources).
Fixes LP #1474195
(Review request: http://reviews.vapour.ws/r/2180/)