influxdata / influxdata/docs-v2
Update docs around tasks and _task bucket
@jstirnaman is already working on this.
Since Jul 19, 2022.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
Include info that addresses the following:
- Procedural content: what is the failure/recover behaviour of tasks surrounding task fails?
- If “the task engine” fails (an internal / 500 failure), the task is rescheduled.
- If the task itself fails (a user / 400 failure) fails 5 times in a row, the task is paused.
- Is there a certain number of failures in a certain period of time
cc @aanthony1243 for review/to verify functionality
- Conceptual/overview content: In general, design tasks to be idempotent and approach task processing as an at-least-once process (does this mean process at least once?). The task system as a set of processors taking scheduled tasks off a queue.
- In the context of preparing to 'migrate to cloud', why are tasks in 2.0 better and/or how can folks most easiely handle tasks coming from Enterprise or Cloud 1.x
Slack [discussion](https://influxdata.slack.com/archives/CDBJ35NBV/p1628674778026100)
##### Relevant URLs
- _task bucket reference doc: https://docs.influxdata.com/influxdb/cloud/reference/internals/system-buckets/
- tasks procedural (how to) docs: https://docs.influxdata.com/influxdb/cloud/process-data/manage-tasks/
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.
Assessment
This issue has not been assessed yet.