With a lot of receivers only a small part of uploaded packets seems to be stored about habitat HOT 3 CLOSED

Unfortunately this is a downside of CouchDB. If a document merge is already in progress when your uploaded packet arrives, your packet will be rejected (I think with 409 Conflict). This already documented, and CouchDB behaves in this way so it can be used as a distributed database if required (it isn't for habitat).

As the docs say, if you receive a Conflict you should retry. For instance, dl-fldigi does this.

from habitat.

On 17 Aug 2016 11:10 p.m., "Richard Meadows" [email protected]
wrote:

Unfortunately this is a downside of CouchDB. If a document merge is
already in progress when your uploaded packet arrives, your packet will be
rejected (I think with 409 Conflict). This already documented, and CouchDB
behaves in this way so it can be used as a distributed database if required
(it isn't for habitat).

As the docs say, if you receive a Conflict you should retry. For
instance, dl-fldigi does this.

Indeed, the habitat python client does it too:
https://github.com/ukhas/habitat/blob/develop/habitat/uploader.py#L219

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

from habitat.

Thanks for the explanations. Indeed the windows tracker uses the python client. M0RJX is trying to take care of the LoRa part for repeating messages after being rejected I noticed.
Topic can be closed, big thanks for the great support !

from habitat.