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

[Andy Gross]

We also use pg2 heavily in our production network, and are also  
interested in seeing a resolution to this bug.  It hasn't popped up in  
production yet, but when we moved offices we spent a couple of days  
trying to purge our pg2 groups of old, stale pids running on IP  
addresses from the old office space, to no avail.  Eventually each  
developer just switched cookies to prevent whatever rogue pg2 instance  
was poisoning the group membership.

Could someone in-the-know describe the monitoring changes made to  
global mentioned below?   Would a patch from the community with a test  
suite be considered for inclusion in any R12-X release?

- Andy


On May 7, 2008, at 10:28 PM, Matthew Dempsky wrote:

> 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?  :-)
>>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions