Atomic map ops appear to have relaxed ordering about hyperdex HOT 3 CLOSED

Lest one think "Ah, you're aliasing pointers at the beginning and ending of two arrays", here is some more output, showing a different set of errors:

  initial:   fromList [(-1457651,-53124),(-1429630,-2226610),(56924,-3413635),(116313,-2323970),(810848,-3094379),(1561988,2869724),(2929291,2800627)]
  operand:   fromList [(116313,-4007453),(1561988,-3575228),(2929291,3704487)]
  output:    fromList [(-1457651,-53124),(-1429630,-2226610),(56924,-3413635),(116313,-2323970),(810848,-3094379),(1561988,-705504),(2929291,2497661)]
  expected:  fromList [(-1457651,-53124),(-1429630,-2226610),(56924,-3413635),(116313,-6331423),(810848,-3094379),(1561988,-705504),(2929291,6505114)]

Here, one addition operation applied, but the other did not?

from hyperdex.

This was due to a garbage collector error, of all things, which in a minute number of cases would reclaim a piece of memory passed to libhyperdex-client, and thereby mangle it.

That is now fixed and the persons responsible for this error have been dealt with.

from hyperdex.

Hi Aaron,

Great to hear that this was due to the GC environment and not HyperDex.
Thanks for diligently catching, and then resolving it!

• egs

On Thu, Jul 23, 2015, 8:10 PM Aaron Friel [email protected] wrote:

This was due to a garbage collector error, of all things, which in a
minute number of cases would reclaim a piece of memory passed to
libhyperdex-client, and thereby mangle it.

That is now fixed and the persons responsible for this error have been
dealt with.

—
Reply to this email directly or view it on GitHub
#215 (comment).

from hyperdex.