I *think* I finally figured out the ChaoticBalancerIT...
https://github.com/apache/accumulo/pull/401

On Thu, Mar 15, 2018 at 12:27 PM, Christopher <ctubb...@apache.org> wrote:

> I think RollWALPerformanceIT was related to Eric's WAL improvements in 1.8.
>
> On Thu, Mar 15, 2018 at 12:09 PM Mike Miller <mmil...@apache.org> wrote:
>
> > I still have logs saved from last year when I was looking at
> > ChaoticBalancerIT and CyclicReplicationIT.  So they at the very least
> have
> > been flaky for a while.  But sadly I didn't get anywhere with them.  I
> can
> > revisit.
> >
> > I don't see RollWALPerformanceIT in 1.7.  It looks like this was added in
> > the 1.8/1.9 branch?
> >
> > On Wed, Mar 14, 2018 at 11:49 PM, Christopher <ctubb...@apache.org>
> wrote:
> >
> > > I'm still seeing some test failures in 1.7 and 1.8/1.9 branches that
> I'm
> > > trying to work through before I prepare another release candidate.
> > >
> > > The "hang forever" bug in (
> > > https://issues.apache.org/jira/browse/ACCUMULO-4847) that was presumed
> > to
> > > be a flaky test (https://issues.apache.org/jira/browse/ACCUMULO-4834)
> > left
> > > me a bit frustrated at the lack of attention to the remaining test
> > failures
> > > (no blame intended here... I also have been ignoring IT failures), so
> I'm
> > > going to try to spend some time fixing them, if I can. This include:
> > >
> > > TabletServerGivesUpIT appears to be failing across all branches
> > >
> > > ChaoticBalancerIT is consistently failing, but passes occasionally
> > > CyclicReplicationIT is flaky, but passes on reruns
> > > RollWALPerformanceIT is a flaky performance test that passes when rerun
> > >
> > > Any willing extra pairs of eyes on these tests (or any others which are
> > > failing) would be greatly appreciated.
> > >
> > > On Wed, Feb 28, 2018 at 1:28 PM Mike Miller <mmil...@apache.org>
> wrote:
> > >
> > > > I was able to run Randomwalk overnight against a 7 node EC2 Centos
> > > cluster
> > > > using Muchos with 4 walkers.  I disabled the replication test since
> it
> > > was
> > > > unstable, see ACCUMULO-4833
> > > > <https://issues.apache.org/jira/browse/ACCUMULO-4833>.  3 out of
> the 4
> > > > walkers failed reporting errors:
> > > > - 2 walkers reported false positives on concurrent/AddSplits.  Fixed
> > the
> > > > test in bcd2dc5
> > > > - 1 walker found a minor bug in client error handling, which I
> reported
> > > > with ACCUMULO-4835 <
> > https://issues.apache.org/jira/browse/ACCUMULO-4835>
> > > >
> > > > On Wed, Feb 28, 2018 at 9:46 AM, Keith Turner <ke...@deenlo.com>
> > wrote:
> > > >
> > > > > I completed a successful run of continuous ingest on 8 EC2 nodes
> > using
> > > > > this RC.  Ran ingest for about 21 to 22 hours and then verified.  I
> > > > > did not agitate.
> > > > >
> > > > >         org.apache.accumulo.test.continuous.ContinuousVerify$
> Counts
> > > > >                 REFERENCED=28627507418
> > > > >                 UNREFERENCED=8001142
> > > > >
> > > > > On Wed, Feb 21, 2018 at 6:10 PM, Christopher <ctubb...@apache.org>
> > > > wrote:
> > > > > > Accumulo Developers,
> > > > > >
> > > > > > The following is a **TEST** release candidate (no need to vote)
> for
> > > > > > Accumulo 1.7.4.
> > > > > > As recently discussed, it's time for a 1.7.4 release. This
> > candidate
> > > > > > represents my test of the build system as it currently exists.
> > Please
> > > > use
> > > > > > these artifacts to do any relevant testing.
> > > > > >
> > > > > > If there's no activity in the next few days, I'll create an rc1
> to
> > > vote
> > > > > on.
> > > > > > I'm also willing to pass off to another release manager if
> somebody
> > > > feels
> > > > > > strongly about taking on that task, but I've got my dev
> environment
> > > set
> > > > > up
> > > > > > for it, so I don't mind.
> > > > > >
> > > > > > Git Commit:
> > > > > >     dbeca4335c850750ef90c2086c19527c7d73e729
> > > > > > Branch:
> > > > > >     1.7.4-rc0
> > > > > >
> > > > > > If this vote passes, a gpg-signed tag will be created using:
> > > > > >     git tag -f -m 'Apache Accumulo 1.7.4' -s rel/1.7.4
> > > > > > dbeca4335c850750ef90c2086c19527c7d73e729
> > > > > >
> > > > > > Staging repo:
> > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapacheaccumulo-1066
> > > > > > Source (official release artifact):
> > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapacheaccumulo-1066/org/apache/accumulo/accumulo/1.7.
> > > > > 4/accumulo-1.7.4-src.tar.gz
> > > > > > Binary:
> > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapacheaccumulo-1066/org/apache/accumulo/accumulo/1.7.
> > > > > 4/accumulo-1.7.4-bin.tar.gz
> > > > > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash
> > > for a
> > > > > > given artifact.)
> > > > > >
> > > > > > All artifacts were built and staged with:
> > > > > >     mvn release:prepare && mvn release:perform
> > > > > >
> > > > > > Signing keys are available at
> > > > https://www.apache.org/dist/accumulo/KEYS
> > > > > > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
> > > > > >
> > > > > > Release notes (in progress) can be found at:
> > > > > > https://github.com/apache/accumulo-website/pull/58
> > > > > >
> > > > > > Please vote one of:
> > > > > > [ ] +1 - I have verified and accept...
> > > > > > [ ] +0 - I have reservations, but not strong enough to vote
> > > against...
> > > > > > [ ] -1 - Because..., I do not accept...
> > > > > > ... these artifacts as the 1.7.4 release of Apache Accumulo.
> > > > > >
> > > > > > This vote will remain open until at least Sat Feb 24 23:30:00 UTC
> > > 2018
> > > > > > (Sat Feb 24 18:30:00 EST 2018 / Sat Feb 24 15:30:00 PST 2018).
> > > > > > Voting continues until the release manager sends an email closing
> > the
> > > > > vote.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > P.S. Hint: download the whole staging repo with
> > > > > >     wget -erobots=off -r -l inf -np -nH \
> > > > > >
> > > > > > https://repository.apache.org/content/repositories/
> > > > > orgapacheaccumulo-1066/
> > > > > >     # note the trailing slash is needed
> > > > >
> > > >
> > >
> >
>

Reply via email to