+0 Because the possibility that changes in 1.7.0 may be causing the lease recovery. I have no evidence of this. However I have done lots of testing with Accumulo 1.6.X on Hadoop 2.6.0 and have never seen this issue.
I was able to successfully build Fluo against 1.7.0 and run all of its test. On Tue, May 12, 2015 at 3:08 PM, Josh Elser <josh.el...@gmail.com> 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. >
