influxdata / influxdata/influxdb-client-python
Best strategy for queueing when network/server is down
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 793
- Forks
- 186
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 1
Description
I have InfluxDB running on a server, and several raspberry pi's collecting data IoT style. When the network connection is lost between PIs and server, how should the client queue data for later retry/batch submission so as to not lose any data? Additionally, PIs have small amounts of RAM, so this queue would need to be disk-based. What is the best strategy here? Just keep appending wire-line strings to a file, or is there something better?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue does not name a file, test, or entry point; it asks for a strategy for disk-backed queuing and retry when Raspberry Pis cannot reach the InfluxDB server. Begin by identifying the client’s existing write and retry behavior, then define the queue’s persistence, batching, retry, and completion criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, raspberry-pi
- Domain
- databases, distributed-systems, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100