Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Received-SPF: pass (nike.apache.org: domain of josh.accumulo@gmail.com
 designates 209.85.161.169 as permitted sender)
MIME-Version: 1.0
Date: Thu, 29 Nov 2012 09:59:08 -0500
Message-ID: 
 <CAPJzM_vvyk1MnX0S8zph34tW1voq1Mcj2SMRxJJ=jTmCn0-VNg@mail.gmail.com>
Subject: Accumulo Junit Concurrency/Latency issues ( Accumulo 1.3 )
From: Joe Berk <josh.accumulo@gmail.com>
To: user <user@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=20cf300e55556ecb4804cfa3862b

--20cf300e55556ecb4804cfa3862b
Content-Type: text/plain; charset=ISO-8859-1

Good morning all,

I'm experiencing some "weirdness" when executing JUnit tests for my classes
that operate with Accumulo. I can best describe it as latency.
Basically, when I write my object to Accumulo & then immediately retrieve
it to inspect the values, the values are not always updated to what I just
saved them as.

Problem:
  part 1:
    - I create an object that has some primitive types.
    - I set the primitive variables to acceptable values.
    - I serialize the object (the "Value")
    - I write the Value to Accumulo ( Entry )
    - I retrieve the Object from Accumulo & inspect. The primitive values
are equal to what they were set to.

  part 2:
    - I retrieve the object from Accumulo
    - I set the primitive variables to different values
    - I serialize the object
    - I write the Value to Accumlo ( Entry )
    - I retrieve the Object from Accumulo & inspect. The primitive values
are *not equal* to what they were just set to

This only seems to be happening during the JUnit.

I have a method that performs the above task, in a JUnit test, and when I
repeatedly run the JUnit test, it will intermittently fail.
I have the same exact method, but it is in a regular class, and I can run
it as much as I want, with no failure.

for the non-JUnit test, MockInstances and  "real" instances succeed every
time
for the JUnit test, MockInstances and "real" instances both fail
intermittently.

sidenotes:
- I am definitely using the same key to update and retrieve the data. I
also inspected the entries that I was writing to Accumulo, every time, and
can confirm that they are being "sent"/"written" to Accumulo as I intend
them to be. In summary, I am positive that I am sending the correct data to
be written. This is doubly verified by my ability to intermittently succeed
when JUnit and 100% succeed in a "normal" class.

Any assistance would be greatly appreciated.

Best Regards,

Josh

--20cf300e55556ecb4804cfa3862b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Good morning all,<div><br></div><div>I&#39;m experiencing some &quot;weirdn=
ess&quot; when executing JUnit tests for my classes that operate with Accum=
ulo. I can best describe it as latency.</div><div>Basically, when I write m=
y object to Accumulo &amp; then immediately retrieve it to inspect the valu=
es, the values are not always updated to what I just saved them as.</div>
<div><br></div><div>Problem:</div><div>=A0 part 1:</div><div>=A0 =A0 - I cr=
eate an object that has some primitive types.</div><div>=A0 =A0 - I set the=
 primitive variables to acceptable values.</div><div>=A0 =A0 - I serialize =
the object (the &quot;Value&quot;)</div>
<div>=A0 =A0 - I write the Value to Accumulo ( Entry )</div><div>=A0 =A0 - =
I retrieve the Object from Accumulo &amp; inspect. The primitive values are=
 equal to what they were set to.</div><div><br></div><div>=A0 part 2:</div>=
<div>=A0 =A0 - I retrieve the object from Accumulo</div>
<div>=A0 =A0 - I set the primitive variables to different values</div><div>=
=A0 =A0 - I serialize the object</div><div>=A0 =A0 - I write the Value to A=
ccumlo ( Entry )=A0</div><div>=A0 =A0 - I retrieve the Object from Accumulo=
 &amp; inspect. The primitive values are <u>not equal</u>=A0to what they we=
re just set to</div>
<div><br></div><div>This only seems to be happening during the JUnit.=A0</d=
iv><div><br></div><div>I have a method that performs the above task, in a J=
Unit test, and when I repeatedly run the JUnit test, it will intermittently=
 fail.</div>
<div>I have the same exact method, but it is in a regular class, and I can =
run it as much as I want, with no failure.=A0</div><div><br></div><div>for =
the non-JUnit test, MockInstances and =A0&quot;real&quot; instances succeed=
 every time</div>
<div>for the JUnit test, MockInstances and &quot;real&quot; instances both =
fail intermittently.</div><div><br></div><div>sidenotes:</div><div>- I am d=
efinitely using the same key to update and retrieve the data. I also inspec=
ted the entries that I was writing to Accumulo, every time, and can confirm=
 that they are being &quot;sent&quot;/&quot;written&quot; to Accumulo as I =
intend them to be. In summary, I am positive that I am sending the correct =
data to be written. This is doubly verified by my ability to intermittently=
 succeed when JUnit and 100% succeed in a &quot;normal&quot; class.</div>
<div><br></div><div>Any assistance would be greatly appreciated.</div><div>=
<br></div><div>Best Regards,</div><div><br></div><div>Josh=A0</div><div><br=
></div><div><br></div><div>=A0 =A0</div><div><br></div><div><br></div><div>=
<br>
</div><div><br></div><div><br></div>

--20cf300e55556ecb4804cfa3862b--