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

CORE-20780: Merging forward updates from release/os/5.2 to release/os/5.3 - 2024-08-30 #6336

Conversation

corda-jenkins-ci02[bot]
Copy link
Contributor

This PR was created by the merge bot.

Includes:

YashNabar and others added 4 commits July 5, 2024 11:52
…'ERROR' (#6235)

Addresses an issue where a subscription, on encountering a fatal exception, causes the coordinator to transition to 'DOWN'. This leaves the component marked as 'DOWN' instead of 'ERROR', which means it will not be restarted by K8s.
CORE-19976 Prevent components from being marked as 'DOWN' instead of 'ERROR'
…6270)

This change prevents a lifecycle component from moving from `ERROR` state to `UP` or `DOWN`. It should not be possible to do this, but it was observed that competing threads could achieve it through a race condition.
@corda-jenkins-ci02
Copy link
Contributor Author

Please remember to 'Merge' all forward merges and do not 'Squash and Merge'

@ronanbrowne ronanbrowne deleted the merge-release/os/5.2-release/os/5.3-2024-08-30-295 branch August 30, 2024 12:57
Copy link

sonarcloud bot commented Aug 30, 2024

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.

3 participants