You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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 fromselect
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.
The text was updated successfully, but these errors were encountered: