Repository navigation
Explain how to read the logs of a crashed HA pod - #1854
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Explains how to read the logs of an HA pod that crashes before its log file can be opened (
kubectl logs --previous), and that this needs--also-log-to-stderr=trueon every data instance and coordinator. Added to the Kubernetes HA Debugging section, with a FAQ entry that links to it.The flag is hidden in Memgraph (default
false), and the HA chart sets it throughcommonArgs.{data,coordinators}.logging.also_log_to_stderr(defaulttrue). Thekubectlcommands use the chart's pod and container names; I didn't run them on a cluster.Also fixes two nearby errors:
--log-retention-days(and the chart values). ItsSET DATABASE SETTINGexample quoted the setting name in backticks, which fails to parse; it now uses quotes and acypherfence. Ran it on Memgraph 3.14.0.commonArgs.{data,coordinators}.logging.log_leveldefaults toINFO(feat: update default log level to INFO helm-charts#277), notTRACE.Product PR
None, docs-only change.