Issue with persistent config EMQ 2.3.11

[imsbhatnagar]

I need to understand how the persistent conf works as defined in the emq.conf.

When my subscriber client is disconnected from the n/w (due to any failure), the msgs from the publisher are reported dropped by the EMQ broker. I require these msgs to be delivered to the subscriber once it comes back. Is there any other configuration which is needed to be taken care in conjunction.

/*
mqtt.mqueue.type = simple
mqtt.mqueue.max_length = 0
mqtt.mqueue.low_watermark = 20%
mqtt.mqueue.high_watermark = 60%
mqtt.mqueue.store_qos0 = true
*/

[gilbertwong96]

mqueue is not persistent config, it store the message in memory rather than disk for session, if you want persistent feature of emqx, please contact with @zhengyupan for enterprise edition.

[imsbhatnagar]

Thanks !!
@zhengyupan, I have already written @ contact@emqx.io to share the emqx-enterprise-centos6.8-v2.1.0.zip, there is no response.

[imsbhatnagar]

@gilbert-wong , At present I do not bother whether mqueue is in memory or writes to disk.. even if it is in-memory holding the msg - it should deliver to the subscriber once it is back. My EMQ broker instances does not restart so the in-memory should be intact to persist msgs. What are your comments on this ?

[gilbertwong96]

The numbers of message in mqueue is limited by you memory and if the session of your mqtt client has been expired , broker would not holding the msg ,the enterprise could solve this problem

[imsbhatnagar]

Thanks @gilbert-wong, appreciate your prompt response.
Memory is not an issue for me so I can hold lot of messages, to persist a session should I set the cleansession = false in the client ?
Meantime I am also awaiting an enterprise package from the emq team.

[imsbhatnagar]

With cleansession = false ; the in-memory persistent is still not working

[imsbhatnagar]

@gilbert-wong, thanks
cleansession = false worked for the in-memory persistent mqueue 👍

Now I am only awaiting the enterprise version so that I can also perform disk writes.

Thanks again for the help