-
Notifications
You must be signed in to change notification settings - Fork 864
ES-2678: Added checks to verify that clusterInfo() is (#21972) #21973
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
Conversation
* ES-2678: Added checks to verify that clusterInfo() is availble before accessing it. * Fixed linter errors * Fixed error reported by Cursor Bugbot * Added Changelog entry
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
// log crash dump feature | ||
CrashHandler::logBacktrace(); | ||
} | ||
THROW_ARANGO_EXCEPTION(TRI_ERROR_SHUTTING_DOWN); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Cluster Info Null Error Masked
The clusterInfo()
method now unconditionally throws TRI_ERROR_SHUTTING_DOWN
when _clusterInfo
is null. This is problematic because if the server is not shutting down, it previously triggered a fatal assertion. The new behavior replaces this critical error with a misleading TRI_ERROR_SHUTTING_DOWN
exception, obscuring the actual problem of _clusterInfo
being unavailable during normal operation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is OK, because we maintain complete backwards compatibilitiy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
// log crash dump feature | ||
CrashHandler::logBacktrace(); | ||
} | ||
THROW_ARANGO_EXCEPTION(TRI_ERROR_SHUTTING_DOWN); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is OK, because we maintain complete backwards compatibilitiy.
ES-2678: Added checks to verify that clusterInfo() is availble before accessing it.
Fixed linter errors
Fixed error reported by Cursor Bugbot
Added Changelog entry
Scope & Purpose
(Please describe the changes in this PR for reviewers, motivation, rationale - mandatory)
Checklist
Related Information
(Please reference tickets / specification / other PRs etc)