[erlang-bugs] table referred to by foreign key does not have node pool properly cleaned up when a node is removed from the schema (fwd)

Hakan Mattsson hakan@REDACTED
Fri May 16 16:30:32 CEST 2008


FYI.

/Håkan
---
Håkan Mattsson (uabhams)
Erlang/OTP crew, Ericsson

---------- Forwarded message ----------
Date: Fri, 16 May 2008 16:19:13 +0200 (CEST)
From: Hakan Mattsson <hakan@REDACTED>
To: Paul Mineiro <paul-trapexit@REDACTED>
Cc: Dan Gudmundsson <dgud@REDACTED>
Subject: Re: [erlang-bugs] table referred to by foreign key does not have node
     pool properly cleaned up when a node is removed from the schema


Hi Paul!

Thank you for reporting this error.
It is now fixed and will be released in mnesia-4.4.3 (R12B-3).

Put the attached file in some directory in your code path
in order to get rid of the problem.

/Håkan
---
Håkan Mattsson (uabhams)
Erlang/OTP crew, Ericsson

On Thu, 15 May 2008, Dan Gudmundsson wrote:

-------- Original Message --------
Subject: [erlang-bugs] table referred to by foreign key does not have node
pool properly cleaned up when a node is removed from the schema
Date: Sat, 10 May 2008 11:22:38 -0700 (PDT)
From: Paul Mineiro <paul-trapexit@REDACTED>
To: erlang-bugs@REDACTED

the attachment has a minimal demonstration.

this bug causes substantial problems trying to maintain the table going
forward since (as indicated in the attachment), manual maintainence of the
node pool list is also not possible once this occurs.  if we had not been
able to create a machine that had the same node name as the one removed,
i'm not quite sure how we would have navigated around this in our
production system, short of restore from backup.

i'm using mnesia-4.3.5 and erlang-otp r11b5.

thanks,

-- p

In an artificial world, only extremists live naturally.

        -- Paul Graham
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mnesia_frag.beam
Type: application/octet-stream
Size: 49052 bytes
Desc: mnesia_frag.beam
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20080516/d71df319/attachment.obj>


More information about the erlang-bugs mailing list