Skip to content

Comments

Only Run SendSlackMessage From Primary VTorc Instances#597

Closed
makinje16 wants to merge 3 commits intoslack-19.0from
slack-19.0-vtorc-messages
Closed

Only Run SendSlackMessage From Primary VTorc Instances#597
makinje16 wants to merge 3 commits intoslack-19.0from
slack-19.0-vtorc-messages

Conversation

@makinje16
Copy link

Description

Currently VTorc sends 3x slack notifications when recovery succeeds or fails. This PR limits those messages to only be from the primary vtorc instances.

Related Issue(s)

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

@makinje16 makinje16 requested a review from a team as a code owner February 4, 2025 19:45
@github-actions github-actions bot added this to the v19.0.7 milestone Feb 4, 2025
if err != nil {
message := fmt.Sprintf("Recovery failed on %s for problem %s. Error: %s", analysisEntry.AnalyzedInstanceHostname, analysisEntry.Analysis, err.Error())
vtopsExec.SendSlackMessage(message, vtopsSlackChannel)
if analysisEntry.IsPrimary {

Choose a reason for hiding this comment

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

IsPrimary is an attribute of the vtorc analysis (i.e. diagnostic of the problem), not of the vtorc instance itself. So with this change, the recovery messages would only be used for primary vttablets, bout would still be sent by all vtorcs. Unlike classical Orchestrator, in vtorc there are no cluster leaders/primaries, they all operate independently of each other.

@github-actions
Copy link

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

  • Push additional commits to the associated branch.
  • Remove the stale label.
  • Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

@github-actions github-actions bot added the Stale label Mar 14, 2025
@github-actions
Copy link

This PR was closed because it has been stale for 7 days with no activity.

@github-actions github-actions bot closed this Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants