Alter log level of garbage collector message (fix #10172) #10173
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
The garbage collector runs periodically to free unused memory with the default operation set to occur during quiet periods. In the event that a quiet period does not arise, the garbage collector is forced and a warning generated to inform users this has occured.
As warnings require users to take action, this log message causes confusion. Therefore, the log level of the garbage collection message has been altered from LevelWarn to LevelInfo to provide information that this has occured without expectation of users to take action.
Changelog
Instead of a warning when the GC is forced to run, an info message will be generated.
Component : server
Type: bugfix
Product: community-edition
Short Changelog
Instead of a warning when the GC is forced to run, an info message will be generated.
Long Changelog
Related Issues
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sql
auto manages the new metadata through schema diffing?run_sql
auto manages the definitions of metadata on renaming?export_metadata
/replace_metadata
supports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
query
types:args
payload which is not backward compatibleJSON
schemaGraphQL API
Schema Generation:
NamedType
Schema Resolve:-
null
value for any input fieldsLogging
JSON
schema has changedtype
names have changed