The maxctrl show qc_cache is a slightly dangerous command to run in production as it causes the whole cached to be copied into memory multiple times. The peak memory usage will be more than three times the configured cache size and with the default cache size, this amounts to 45% of the total system memory. A non-default value that exceeds 30% of the system memory is almost guaranteed to cause an OOM scenario.

A better alternative for dumping the whole cache is described in MXS-4899 but the REST-API endpoint that the maxctrl command calls should limit the number of entries to some predetermined size.