Skip to content

Don't return khepri status when khperi_db is disabled #12085

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

Merged
merged 1 commit into from
Aug 22, 2024

Conversation

mkuratczyk
Copy link
Contributor

When khepri_db feature flag is disabled, Khepri servers are running but are not clustered. In this case rabbit_khepri:status/0 shows that all nodes are leaders, which is confusing and scary (even though actually harmless). Instead, we now just print that mnesia is in use.

When khepri_db feature flag is disabled, Khepri servers
are running but are not clustered. In this case `rabbit_khepri:status/0`
shows that all nodes are leaders, which is confusing and scary
(even though actually harmless). Instead, we now just print that mnesia
is in use.
@michaelklishin michaelklishin merged commit 9b6041d into main Aug 22, 2024
195 checks passed
@michaelklishin michaelklishin deleted the metadata_store_status-mnesia branch August 22, 2024 17:30
michaelklishin added a commit that referenced this pull request Aug 22, 2024
Don't return khepri status when khperi_db is disabled (backport #12085)
michaelklishin added a commit that referenced this pull request Aug 23, 2024
Don't return khepri status when khperi_db is disabled (backport #12085) (backport #12092)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants