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

remoting: RE client should access AC via store server not execution servers #10317

Closed
tdyas opened this issue Jul 10, 2020 · 2 comments
Closed

remoting: RE client should access AC via store server not execution servers #10317

tdyas opened this issue Jul 10, 2020 · 2 comments
Labels
bug

Comments

@tdyas
Copy link
Contributor

tdyas commented Jul 10, 2020

I was trying to get Buildgrid working with Pants. The configuration that I was using pointed the remote_execution_server and remote_store_server at two different servers. The Pants RE client attempts to access the Action Cache via the remote_execution_server and not remote_store_server, which does not work when the AC is accessed via the remote_store_server.

Solution: Use remote_store_server to access the Action Cache.
@tdyas tdyas mentioned this issue Jul 11, 2020
Merged
stuhood pushed a commit that referenced this issue Jul 16, 2020
access store server for action cache (#10329)
063401e 
### Problem

#10317 describes a bug where Pants looks for the Action Cache at the address of the remote execution servers instead of remote store servers, which causes Pants to not find the Action Cache when it is hosted on the store servers.

### Solution

Use the store server for the Action Cache location.

### Result

Pants is able to retrieve action results from the Action Cache in situations where the execution and store servers are different.
@stuhood
Copy link
Sponsor Member

stuhood commented Nov 25, 2020

I think that #10329 fixed this? Can reopen if not.

@stuhood stuhood closed this as completed Nov 25, 2020
@tdyas
Copy link
Contributor Author

tdyas commented Nov 25, 2020 •
edited

Yes, it should have. This was really only a problem with Buildgrid which ran those services on different endpoints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stuhood @tdyas