Table performance_schema.setup_consumers is reset on instance bounce
It appears that the settings in performance_schema.setup_consumers are not persisted across an instance bounce.
I enable the events:
-------------- SELECT * FROM performance_schema.setup_consumers -------------- +--------------------------------+---------+ | NAME | ENABLED | +--------------------------------+---------+ | events_stages_current | YES | | events_stages_history | YES | | events_stages_history_long | YES | | events_statements_current | YES | | events_statements_history | YES | | events_statements_history_long | YES | | events_waits_current | YES | | events_waits_history | YES | | events_waits_history_long | YES | | global_instrumentation | YES | | thread_instrumentation | YES | | statements_digest | YES | +--------------------------------+---------+
I bounce the instance. Most of the events are disabled:
-------------- SELECT * FROM performance_schema.setup_consumers -------------- +--------------------------------+---------+ | NAME | ENABLED | +--------------------------------+---------+ | events_stages_current | NO | | events_stages_history | NO | | events_stages_history_long | NO | | events_statements_current | YES | | events_statements_history | NO | | events_statements_history_long | NO | | events_waits_current | NO | | events_waits_history | NO | | events_waits_history_long | NO | | global_instrumentation | YES | | thread_instrumentation | YES | | statements_digest | YES | +--------------------------------+---------+
Is there a way to make this persist across bounces?
Answer Answered by Ian Gilfillan in this comment.
You can specify these at startup with options along the lines of
--performance-schema-consumer-events-waits-history=ON
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
