influxdata / influxdata/kapacitor

Solidify contract that all accepted points are processed

Open
#275 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

In the current implementation when the server is shutdown in-flight requests are dropped.

The correct design should be that all tasks run to completion but to reload a task its source is cut off, and is then allowed to run to completion. Once all tasks run to completion we need to add an explicit abort method that can kill a running task without allowing it to run to completion.

This is going to need some careful design and API specification.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Begin by mapping shutdown, reload, and in-flight task handling, then define the lifecycle and API behavior for completion versus explicit abort; done means the design is specified and accepted.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.