-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
CLI: Allow snapshot inspect to work on internal raft snapshots directly. #10089
Conversation
🤔 This PR has changes in the |
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.
I think this needs a changelog entry added but otherwise this all looks good. Having this is going to be very useful for debugging.
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/355992. |
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/356924. |
🍒✅ Cherry pick of commit d717d2c onto |
…ly. (#10089) * CLI: Add support for reading internal raft snapshots to snapshot inspect * Add snapshot inspect test for raw state files * Add changelog entry * Update .changelog/10089.txt
As documented, this extends
consul snapshot inspect
to allow it to automatically detect an attempt to open an internal snapshot direct from the raft data dir on a server rather than requiring a "packaged" snapshot to be generated and downloaded.This is often needed by operators trying to debug issues on live Consul servers.
A note is added to docs to try to clarify the difference between external, on-demand, packaged snapshot files, and internal raw raft state snapshots, and an example usage added.