Skip to content
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

fix(kuma-cp): make store changes processing more reliable (backport of #6728) #6765

Merged
merged 1 commit into from
May 16, 2023

Conversation

kumahq[bot]
Copy link
Contributor

@kumahq kumahq bot commented May 15, 2023

Automatic cherry-pick of #6728 for branch release-2.2

Generated by action

cherry-picked commit c0953ae

When running deployment with postgres/etcd we are using EventBus which is responsible for sending database events to mesh-insight-resyncer component. In case of a problem with the connection to the database, mesh-insight-resyncer component is closed and restarted by ResilientComponent. On each restart, we are subscribing to the event bus, but we are not removing the old subscription. That caused the issue in which we were sending events to the subscriber that didn't exist at that time. Because we are sending it and no one is listing it, the component was hanging and events were not propagated to other subscribers.

Signed-off-by: Lukasz Dziedziak <lukidzi@gmail.com>
@kumahq kumahq bot requested review from a team, michaelbeaumont and lukidzi and removed request for a team May 15, 2023 15:30
@kumahq kumahq bot added the release-2.2 label May 15, 2023
@lukidzi lukidzi merged commit a1fc51f into release-2.2 May 16, 2023
@lukidzi lukidzi deleted the chore/backport-release-2.2-6728 branch May 16, 2023 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant