Skip to content

Clarify configChecksumAnnotation behavior for non-reloadable params#1148

Open
jtnats wants to merge 1 commit intonats-io:mainfrom
jtnats:docs/clarify-config-checksum-annotation
Open

Clarify configChecksumAnnotation behavior for non-reloadable params#1148
jtnats wants to merge 1 commit intonats-io:mainfrom
jtnats:docs/clarify-config-checksum-annotation

Conversation

@jtnats
Copy link
Copy Markdown

@jtnats jtnats commented Mar 27, 2026

Purpose

Clarify configChecksumAnnotation behavior for non-reloadable params

Summary

  • Expand the configChecksumAnnotation comment in values.yaml to warn that non-reloadable parameters (e.g. max_mem, max_file) are silently ignored when the reloader sends SIGHUP
  • Recommend setting configChecksumAnnotation: true when using non-reloadable parameters so that a rolling restart applies them

Motivation

With the default configChecksumAnnotation: false, the reloader signals SIGHUP on config changes. For non-reloadable parameters, the server rejects the reload and the new values never take effect but there is also no visible error to the user. This has been a source of confusion.

@synadia-claude-reviewer
Copy link
Copy Markdown

Claude Code is working…

I'll analyze this and get back to you.

View job run

Copy link
Copy Markdown
Member

@wallyqs wallyqs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, maybe file a separate server issue that those fields are not reloadable and put
in the comment

Comment thread helm/charts/nats/values.yaml
@jtnats jtnats force-pushed the docs/clarify-config-checksum-annotation branch from 94ad6b3 to 3e6c5f4 Compare March 27, 2026 21:04
@jtnats
Copy link
Copy Markdown
Author

jtnats commented Mar 27, 2026

I added a link to the nats-server issue: nats-io/nats-server#7990

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