Skip to content

Conversation

@Combs7th
Copy link
Contributor

@Combs7th Combs7th commented Feb 3, 2026

Summary

Adds documentation for new debug log messages introduced in Mattermost v11.4.0 that help system admins understand cluster job execution behavior in high availability deployments.

Changes

  • Added new section in logging documentation for cluster job execution debug messages
  • Updated high availability cluster documentation with references to debug messages
  • Added tips in job configuration settings about verifying cluster behavior

These DEBUG-level messages indicate normal operation when non-leader nodes skip job execution, helping admins troubleshoot cluster behavior.

Resolves #8706

Generated with Claude Code

Add documentation for new debug log messages introduced in Mattermost
v11.4.0 that help system admins understand cluster job execution
behavior in high availability deployments.

Changes:
- Added new section in logging.rst documenting cluster job debug
  messages for scheduled posts, DND status reset, and post reminders
- Added notes in high-availability-cluster-based-deployment.rst about
  debug messages in leader election and job server sections
- Added tip in experimental-configuration-settings.rst about verifying
  cluster job execution with debug messages

These DEBUG-level messages indicate normal operation when non-leader
nodes skip job execution, helping admins troubleshoot cluster behavior.

Resolves #8706

Co-authored-by: Combs7th <[email protected]>
@Combs7th
Copy link
Contributor Author

Combs7th commented Feb 3, 2026

@harshilsharma63 - Do the above doc updates look accurate to you?

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Newest code from mattermost has been published to preview environment for Git SHA 91e9a11

@harshilsharma63
Copy link
Member

@Combs7th a limitation of those logs is that they were added only for a specific type of job called the Recurring Tasks and are valid only for Scheduled Posts, Post Reminders and DND Status Reset jobs and are not applicable to all jobs in general, just as Elasticsearch indexing job, SAML sync job etc. I think its important to specify this in the docs as otherwise an admin may incorrectly assume the lack of logs of any other job falsely means it is not running.

@cwarnermm cwarnermm changed the title Docs: Added debug log to indicate the job is not running as the node is not a leader node v11.4: Added debug log to indicate the job is not running as the node is not a leader node Feb 3, 2026
@cwarnermm cwarnermm changed the base branch from master to v11.4-documentation February 3, 2026 13:57
@cwarnermm cwarnermm added 1: Dev Review Requires review by a core commiter 2: Editor Review Requires review by an editor Guidance labels Feb 3, 2026
@cwarnermm cwarnermm added this to the v11.4.0 milestone Feb 3, 2026
@wiersgallak wiersgallak requested review from cwarnermm and removed request for wiersgallak February 3, 2026 19:47
@wiersgallak
Copy link
Contributor

Reassigning to Carrie to review once developer review has been completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1: Dev Review Requires review by a core commiter 2: Editor Review Requires review by an editor Guidance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v11.4 Docs: Added debug log to indicate the job is not running as the node is not a leader node

5 participants