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

Modify FATE to allow distributed workers #3822

Open
keith-turner opened this issue Oct 6, 2023 · 1 comment
Open

Modify FATE to allow distributed workers #3822

keith-turner opened this issue Oct 6, 2023 · 1 comment
Assignees
Milestone

Comments

@keith-turner
Copy link
Contributor

FATE could be modified to allow distributed workers to run FATE transactions. Currently FATE relies on the manager lock to ensure one FATE instance is running. That single instance uses a in memory synchronized java map to reserve FATE transaction so that only a single thread runs. Could move to a model of using a condition update (in ZK or metadata table if #3559 is implemented) to reserve a FATE transaction, setting the process lock id per transaction. Would need to have a process of deleting locks held by dead processes.

Distributing FATE could allow scalability of operations like bulk import. It may also be an alternative to using a distributed work queue for the problem of split computation #3560 and compaction file selection #3526. This may be a prerequisite for #3247

@keith-turner keith-turner converted this from a draft issue Oct 6, 2023
@keith-turner
Copy link
Contributor Author

keith-turner commented Oct 6, 2023

#3823 and #3560 are related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants