Add a chaos endpoint that signals QUIT
What does this MR do?
Related to #326348 (closed)
We already have a chaos endpoint that signals KILL: https://docs.gitlab.com/ee/development/chaos_endpoints.html#kill
The problem is that KILL does not dump core; but this can be extremely useful to debug problems with the Ruby VM. We are preparing CI workers to be able to write core dumps in this MR: !58674 (closed)
With this MR we add a new chaos endpoint /quit which signals SIGQUIT instead. SIGQUIT instructs the kernel to also produce a core dump: https://man7.org/linux/man-pages/man7/signal.7.html
Tested this locally with a GCK web container and it worked fine.
I noticed that this container inherited my host system settings for producing core dumps (ulimits and core_pattern) so in order to use this, those properties need to be set up accordingly.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done