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.

Sign up for GitHub

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

Jump to bottom

Rubix will not store cache files on coordinator, even it serves as worker #3563

Closed
losipiuk opened this issue Apr 27, 2020 · 3 comments
Closed

Rubix will not store cache files on coordinator, even it serves as worker #3563

losipiuk opened this issue Apr 27, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@losipiuk
Copy link
Member

Even if we enable scheduling splits on coordinator via node-scheduler.include-coordinator Rubix will not store any cache files on it (unless it is only node in the cluster).
The reason for that is Rubix uses v1/nodes endpoint to enumerate nodes in the cluster and list returned there never contains coordinator (btw, @electrum, is that intended?).

cc: @stagraqubole
@losipiuk losipiuk added the bug Something isn't working label Apr 27, 2020
@losipiuk
Copy link
Member Author

I tagged it as bug. Please correct me if that is actually intended behavior :).

@shubhamtagra
Copy link
Member

This is a bug we never fixed given this was not a production scenario. For dev testing, rubix does support master-only mode.

@sopel39 sopel39 assigned sopel39 and unassigned sopel39 May 21, 2020
@hashhar
Copy link
Member

hashhar commented Feb 22, 2024

Rubix has been removed as of #20102 and replaced with file-system caching in #18719

@hashhar hashhar closed this as completed Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Milestone
No milestone
Development

No branches or pull requests
4 participants
@losipiuk @sopel39 @shubhamtagra @hashhar