Verification on the 24hr CI w/o agitation test completed successfully last night.
The CI w/ agitation test that I restarted hung again last night. Ran into the same HDFS issue w/ lease recovery. Maybe I should run w/o hdfs agitation. On Thu, May 14, 2015 at 7:15 PM, Keith Turner <[email protected]> wrote: > I am running two test on two 20 node EC2 clusters, CI w/ and w/o > agitation. For the agitation test I ran into HDFS-8406 which caused > Accumulo to flatline. I was able to get the test running again with a > special method devised by Eric N. We found the walog block in a datanode > dir and copied it into HDFS over the walog. After this the master was able > to recover the lease and continue running (w/ no data loss, ran an > intermediate verify). Unfortunately, this pushed back the completion time > for this CI w/ agitation test. Not sure if the test will complete before > the deadline. I really want to see the results of this test before voting. > > My cluster that was running CI w/ agitation has completed 24hr of ingest > and is currently verifying. > > On Thu, May 14, 2015 at 1:38 PM, Josh Elser <[email protected]> wrote: > >> Reminder, ~27hrs remaining on this vote. 5pm ET tmrw. >> >> I know some people are running tests. Please pull down the source >> tarball, run unit tests, build the code, poke at it locally. Any and all >> feedback is warmly welcomed. The more eyes we have looking at this the >> better. Thanks in advance. >> >> >> Josh Elser wrote: >> >>> You are correct. I forgot to update the SHA when I copied the contents. >>> >>> The correct SHA1=8cba8128fbc3238bdd9398cf5c36b7cb6dc3b61d >>> >>> Christopher wrote: >>> >>>> The SHA1 seems incorrect. The jars says they were built on >>>> 8cba8128fbc3238bdd9398cf5c36b7cb6dc3b61d, which I can't find in the RC >>>> branch. >>>> >>>> -- >>>> Christopher L Tubbs II >>>> http://gravatar.com/ctubbsii >>>> >>>> >>>> On Tue, May 12, 2015 at 3:08 PM, Josh Elser<[email protected]> >>>> wrote: >>>> >>>>> Devs, >>>>> >>>>> Please consider the following candidate for Apache Accumulo 1.7.0 >>>>> >>>>> Tag: 1.7.0-rc3 >>>>> SHA1: 76634fb2f1257abbb8ef745ea67a4f78e733a402 >>>>> Staging Repository: >>>>> >>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1032 >>>>> >>>>> >>>>> Source tarball: >>>>> >>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1032/org/apache/accumulo/accumulo/1.7.0/accumulo-1.7.0-src.tar.gz >>>>> >>>>> Binary tarball: >>>>> >>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1032/org/apache/accumulo/accumulo/1.7.0/accumulo-1.7.0-bin.tar.gz >>>>> >>>>> (Append ".sha1", ".md5" or ".asc" to download the signature/hash for an >>>>> artifact.) >>>>> >>>>> Signing keys available at: https://www.apache.org/dist/accumulo/KEYS >>>>> >>>>> 1.7.0 includes 693 resolved issues: >>>>> >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312121&version=12324607 >>>>> >>>>> >>>>> Testing: All unit and integration tests are passing. Completed 3-day >>>>> CI w/o >>>>> agitation or verification. Completed 24hr RandomWalk w/o agitation on 3 >>>>> nodes. 95% through 24hr CI and RW w/ agitation. >>>>> >>>>> API compatibility report for 1.6.2 to 1.7.0: >>>>> >>>>> http://people.apache.org/~elserj/accumulo-1.7.0-rc3/1.6.2_to_1.7.0/compat_report.html >>>>> >>>>> >>>>> API backwards compatibility report for 1.7.0 to 1.6.2: >>>>> >>>>> http://people.apache.org/~elserj/accumulo-1.7.0-rc3/1.7.0_to_1.6.2/compat_report.html >>>>> >>>>> >>>>> The vote will be open for 72hrs until Friday, May 16th 4:00PM ET. >>>>> Here's my >>>>> +1. >>>>> >>>> >
