Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Enabled Service for Automated Startup on Reboot with valid grastate.dat

Description

Tyler Duzan
Jun 5, 2018
Discussion 18:58 UTC+1 June 5, 2018 w/ Krunal and Evgeniy:
Problem Statement:
Our current PXC packages do not meet Debian packaging standards, so breaking from them further is not a problem. There are issues which are caused by current behavior on Debian which do not exist on CentOS/RHEL and we seek consistency in how packaging works.
Decision Statement:
On all platforms, after installing PXC the service should be in the stopped and enabled state. On reboot, when the startup script is executed it will look for the existence and content of the grastate.dat. If it does not exist or it contains -1 then the service will not start, otherwise the value if valid will cause the service to start. Our systemd services will have restart-on-failure set to false.

Environment

None

Smart Checklist

Activity

Show:

Alex Miroshnychenko February 25, 2020 at 2:26 PM

> Decision Statement:
> On all platforms, after installing PXC the service should be in the stopped and enabled state.
> On reboot, when the startup script is executed it will look for the existence and content of the grastate.dat.
> If it does not exist or it contains -1 then the service will not start, otherwise the value if valid will cause the service to start.
> Our systemd services will have restart-on-failure set to false.

Done.

Done

Details

Assignee

Reporter

Time tracking

4d 7h logged

Components

Fix versions

Affects versions

Priority

Smart Checklist

Created February 12, 2020 at 2:57 PM
Updated March 6, 2024 at 9:48 PM
Resolved February 25, 2020 at 2:25 PM