Replies: 3 comments 8 replies
-
The error message indicates that an Erlang process has run out of heap space, as you might have guessed. Max Heap Size: 6291456 means 6291456 words, which is roughly equal to 50 megabytes. This amount might seem substantial, but it could be insufficient if you have messages with a lot of data. I'm currently investigating whether we have a setting to control the max heap size of processes. Could you share any settings you have already tried to change? Links to documentation or online tutorials that you have attempted to follow would also be helpful. |
Beta Was this translation helpful? Give feedback.
-
No, because the max heap size is reported in words (one word is 8 bytes on a 64-bit machine). I believe the relevant setting in your emqx.conf file is max_heap_size. As the current setting is 32MB and it appears to be too low for your use case, you could try setting it to a higher value. You can try setting it to, for example, 512MB to see if the error goes away. |
Beta Was this translation helpful? Give feedback.
-
Can you open an emqx console (if you start emqx with |
Beta Was this translation helpful? Give feedback.
-
A message contains the base64 string of the image,
Problem:
Context: maximum heap size reached, Max Heap Size: 6291456, Total Heap Size: 9100325, Kill: true, Error Logger: true, Message Queue Len: 0, GC Info: [{old_heap_block_size,3581853},{heap_block_size,5472277},{mbuf_size,59456},{recent_size,822523},{stack_size,62},{old_heap_size,0},{heap_size,2474138},{bin_vheap_size,205405},{bin_vheap_block_size,220491},{bin_old_vheap_size,0},{bin_old_vheap_block_size,46422}]
Changing the configuration according to the documentation or online tutorials does not work
If must use base64, how should you solve this problem?
Beta Was this translation helpful? Give feedback.
All reactions