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

clean up ephemeral nodes #4

Closed
pH14 opened this issue May 18, 2019 · 2 comments
Closed

clean up ephemeral nodes #4

pH14 opened this issue May 18, 2019 · 2 comments

Comments

@pH14
Copy link
Owner

pH14 commented May 18, 2019

I think there are two broad pieces here, neither being too crazy:

  1. we need to write the code to clean up ephemeral nodes
  2. we need to figure out how we want to choose a client to execute (1)

For the latter piece, there were a few suggestions in https://forums.foundationdb.org/t/fdb-zk-rough-cut-of-zookeeper-api-layer/1278 to build out a simple leader election, or a cooperative clock and electing a given client to do the work for a given period of time. I think it could also make sense to optionally offload some of this work onto a dedicated client, so that app clients aren't cycling through unrelated background work.

@pH14
Copy link
Owner Author

pH14 commented Sep 14, 2019

We can track ephemeral nodes in a separate subspace: (ephemeral_nodes, session_id, zkPath)

When we identify a session that has expired, we can range clear (ephemeral_nodes, session_id, *)

@pH14
Copy link
Owner Author

pH14 commented Sep 20, 2019

#13 resolves this

@pH14 pH14 closed this as completed Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant