[erlang-bugs] [erlang-questions] Weird pg2 behavior

[Matthew Dempsky]

Has there been any progress on this?  This bug bit us again today. :-(

(A pid from a node on a machine that had been decommissioned and not
running any Erlang code for months now but still present on our
network was still lurking in one of our pg2 groups.  Yesterday we
finally repurposed this machine, removing it from our network, which
had the unexpected side effect of causing Pid ! Msg in some heavily
used code to start adding several seconds of delay due to the runtime
attempting to autoconnect to that long-dead node.)

On Fri, Apr 18, 2008 at 1:23 AM, Matthew Dempsky <matthew@REDACTED> wrote:
> On Wed, Apr 16, 2008 at 1:46 AM, Hans Bolinder
>
> <hans.bolinder@REDACTED> wrote:
>
> >  I think pg2 should monitor all pids rather than link to local pids
>  >  only. Carefully setting up monitors, like Global does since R11B-4,
>  >  should work.
>
>  Sounds good to me.  Can we hope to see this in R12B-3?  :-)
>