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

[xcache] Find better loadbalancing solution then only using server red-xcache1.unl.edu #106

Open
oshadura opened this issue Apr 22, 2021 · 2 comments
Open

[xcache] Find better loadbalancing solution then only using server red-xcache1.unl.edu #106

oshadura opened this issue Apr 22, 2021 · 2 comments
Assignees
@gattebury @jthiltges @clundst
Milestone
2022-02-01

Comments

@oshadura
Copy link
Member

oshadura commented Apr 22, 2021 •
edited
Loading

Currently, coffea-casa is using only red-xcache1.unl.edu as a xcache server. If it is not working, then as told Garhan it becomes a 'single point of failure' for coffea-casa.

cc: @bbockelm @djw8605 @gattebury @clundst
@oshadura oshadura added this to the 2021-05-01 milestone Apr 22, 2021
@oshadura oshadura modified the milestones: 2021-05-01, 2021-09-01 Jun 25, 2021
@oshadura oshadura modified the milestones: 2021-09-01, 2022-02-01 Nov 12, 2021
@kenbloom
Copy link

kenbloom commented Jan 7, 2022

Planning on switching to xcache K8s as part of the token change. Once K8s pod is ready, need the server to be K8s.

@clundst
Copy link
Contributor

clundst commented Aug 17, 2022

xcache pod not correctly configured in cmsaf instances on flatiron.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gattebury gattebury

@jthiltges jthiltges

@clundst clundst

Labels
None yet
Projects
None yet
Milestone
2022-02-01
Development

No branches or pull requests
5 participants
@gattebury @jthiltges @kenbloom @oshadura @clundst