Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stateful jobs should be triggered automatically by the use of a stateful asset #3782

Open
godber opened this issue Oct 1, 2024 · 0 comments
Labels
enhancement k8s Applies to Teraslice in kubernetes cluster mode only. pkg/teraslice

Comments

@godber
Copy link
Member

godber commented Oct 1, 2024

We have this notion of "Stateful Workers" as described here:

https://terascope.github.io/teraslice/docs/configuration/clustering-k8s/#stateful-workers

In Teraslice jobs you can set the "stateful": true, property and the workers will be slightly different (see docs). I've realized that this is actually a property of the asset in use, and should probably be set automatically simply by using a "stateful" asset.

In general this is the stateful processor being used:

https://github.com/terascope/elasticsearch-assets/tree/master/asset/src/elasticsearch_state_storage

This probably needs some internal API added to Teraslice that the processor will use to indicate that it is stateful. Perhaps a property on the processor that Teraslice uses.

@godber godber added enhancement k8s Applies to Teraslice in kubernetes cluster mode only. pkg/teraslice labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement k8s Applies to Teraslice in kubernetes cluster mode only. pkg/teraslice
Projects
None yet
Development

No branches or pull requests

1 participant