Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prevent adhoc_kill_splunkd.yml from running by default when upgrading #171

Merged
merged 1 commit into from
Feb 10, 2023

Conversation

jewnix
Copy link
Collaborator

@jewnix jewnix commented Feb 6, 2023

This stops the adhoc_kill_splunkd.yml task from running during upgrade by default.

A few reasons for this change.

  1. In some cases killing it forcefully is not a safe way to go, especially if the instance is busy.
  2. There are also cases when there are multiple instances running on the same host with a different $SPLUNK_HOME, and this will kill all splunk processes
  3. If there are docker containers running the splunk process in them, this can cause some serious issues.

@jewnix jewnix changed the title prevent adhoc_kill_splunkd.yml when upgrading by default prevent adhoc_kill_splunkd.yml from running when upgrading by default Feb 6, 2023
@jewnix jewnix changed the title prevent adhoc_kill_splunkd.yml from running when upgrading by default prevent adhoc_kill_splunkd.yml from running by default when upgrading Feb 6, 2023
@dtwersky dtwersky merged commit 6a30f36 into splunk:master Feb 10, 2023
@jewnix jewnix deleted the disable_force_kill branch February 10, 2023 15:26
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.

None yet

3 participants