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

Behavior for when connecting to already populated store #62

Open
TylerADavis opened this issue Jun 16, 2017 · 3 comments
Open

Behavior for when connecting to already populated store #62

TylerADavis opened this issue Jun 16, 2017 · 3 comments
Labels

Comments

@TylerADavis
Copy link
Collaborator

At the moment, all state about the store is kept locally. If a client connects to a remote store that already contains objects, it will have no knowledge of the ObjectIDs in the store or the Mem_addr/ peer_rkey + other information associated with them.

Should we implement some way for the client to get state from the server, and if so, how?

@TylerADavis
Copy link
Collaborator Author

As of the present, the TCP setup allows for a client to retrieve any item already on the server. However, the RDMA setup allows a client to retrieve only items that it has placed as it keeps track of items locally.

@TylerADavis
Copy link
Collaborator Author

Additionally, it seems that as a result of the aforementioned setup where the RDMA client keeps track of items locally, the server is not aware of the objectID associated with any object. As such, two RDMA clients are able to write to the same objectID without overwriting one another.

@TylerADavis
Copy link
Collaborator Author

This actually popped up as an issue in a test that I wrote for get_bulk as it attempted to access items before any had been put, which is an issue as the store does not know how large a segment of memory to allocate for receiving if no objects have been put previously.

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

No branches or pull requests

1 participant