server
server copied to clipboard
mochi-mqtt
How to enable storage simplify
I see the storage are implement using hooks, but I already have hooks how to make it more painless like out of box support for storage? the message a wipe out when server down, lost all messages inside. I even think this can be a builtin feature whcih can be enable by a simple flag.
@lucasjinreal, you can add multiple hooks, they will all run. Since you're already using hooks, you can add additional ones like you did.
@dgduncan and @mochi-co are working on a new file-based configuration for the broker (#351), which will enable hooks via configuration file.
I mean, the messages stores when program stop, and when start, it should resume old unsent messages, this should be a default bahavior
That's what the storage hooks can provide, select the one that's appropriate for your backend: Badger, Bolt or Redis.
@thedevop thanks, does the hooks provide in example with Badger can be used directly?
need install anything else and configuration anything else?
I personally have not used persistent storage hooks. I would recommend taking a look at Badger example in README.
@thedevop Can it work out of box without any further configurations? Enable the hook, and the unsent message can be automatically resumed?
@thedevop Oh, no, this make things worse, it introduce annoying yaml files to run the lib, can't it set as default behavior to restore messages?
@lucasjinreal the reason why this behavior isn't the default is that one of the most powerful parts of this project is that is an embeddable broker. The base assumption is that at default there is no guarantee that there is access to persistent storage between starts.
To enable something like badger it is as simple as
err := server.AddHook(new(badger.Hook), &badger.Options{ Path: badgerPath, }) if err != nil { log.Fatal(err) }
where badgerPath is the relative location on your system for the badger files to be written to. Do you have a need that this does not fulfill?
As per your comment on #351 this is for when users want the ability to run the broker without worrying about actually embedding it themselves i.e run in a docker container by just passing a config.
@dgduncan thanks, will this work?
err = server.AddHook(new(badger.Hook), &badger.Options{Path: "./uploads"})
if err != nil {
log.Fatal(err)
}
uploads are relative to root of my exe project.
@lucasjinreal That should work as long you have the correct permissions in order to read/write/delete from that location
@lucasjinreal There's also an example for badger in the examples/persistence/badger folder. Let me know if you have any further questions! 🙂
Hi, I tested th exmaple, it;s not work in production,
It produced 4GB bin files but my server can not handle it, and I think the message amount didn't get that high.
Can u help users find a more useable way to dump the unsent messages?
@werbenhu Hi, if enable v2.6.0, can the issue resolved? Have u guys tested with it? And the cache file would be how large?