You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 1, 2024. It is now read-only.
The bundle ownership assignment logic doesn't know the previous unloaded broker when unloading happens. It might assign the bundle to the same broker. In this case, it might cause an infinite bundle unloading loop.
To resolve this issue, we can check the destination broker when doing the doLoadShedding stage. When the destination broker is the same as the current owner broker, we can skip this unload, and if it is different, we set the new owner in this stage.
Modifications
Transfer the bundle to the new owner when needed to unload.
Verifying this change
See the ModularLoadManagerImplTest#testLoadShedding unit test.
Documentation
doc
doc-required
doc-not-needed
doc-complete
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
url: apache#20822
Motivation
The bundle ownership assignment logic doesn't know the previous unloaded broker when unloading happens. It might assign the bundle to the same broker. In this case, it might cause an infinite bundle unloading loop.
To resolve this issue, we can check the destination broker when doing the
doLoadShedding
stage. When the destination broker is the same as the current owner broker, we can skip this unload, and if it is different, we set the new owner in this stage.Modifications
Verifying this change
See the
ModularLoadManagerImplTest#testLoadShedding
unit test.Documentation
doc
doc-required
doc-not-needed
doc-complete
The text was updated successfully, but these errors were encountered: