Open dushyantbangal opened 6 years ago
I have created a new store that could help: https://github.com/robertsLando/mqtt-jsonl-store
@robertsLando I might be wrong, but it looks like the db on which you have built this on is writing the data to a single file. In that case it might have the issue I have mentioned above.
I did use mqtt-level-store
extensively and didnt find any such limitation.
Is your problem related to offline packets storage? If so I personally create a custom store for them and handle my own. You can write them in all the files you want.
Also mind that a size limit is not really necessary as all mqtt storage db use messageId as key and that is a 16bit number. It means there could be at most 2^16-1 packets in your db then them will be overriden. This is why I use a custom store based on the one I have build
I am talking about the total size of data that I can have offline in base network connectivity is lost.
I was using
mqtt-nedb-store
butnedb
is does not support more than 256 MB as it needs to parse the file to json, and 256MB is the limit of js string.Here it looks like the data is being written to multiple small files, which I think avoids that issue.
So are there any limitations that I should know of?