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

Registry.select/2 does not filter out stale entries #136

Open
arjan opened this issue Jul 12, 2019 · 2 comments
Open

Registry.select/2 does not filter out stale entries #136

arjan opened this issue Jul 12, 2019 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@arjan
Copy link
Contributor

arjan commented Jul 12, 2019

Registry.lookup/2 checks whether the returned result is a) still member of the cluster and b) an alive process. However, Registry.select/2 does not do this, and this can lead to confusing results. However, scanning each result from select might be expensive as it can return many results.

This ticket is intended as a placeholder ticket as we don't have a good solution for this yet.

@derekkraan
Copy link
Owner

I think a good first pass solution (and possibly even a permanent solution) for this would be to filter out any entries that reside on disconnected nodes.

@derekkraan
Copy link
Owner

This is a lot trickier than I thought. Because the user has full control over what is returned from :ets, we can not know where the pid is, and in fact the user can also elect to simply not return pid at all!

If anyone has a suggestion on how to make this work, would be much appreciated.

@derekkraan derekkraan added the help wanted Extra attention is needed label Dec 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants