You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "J. Mark Owens" <jm...@gmail.com> on 2018/03/22 19:20:14 UTC
Re[2]: [VOTE] Accumulo 1.7.4-rc1
I know that Christopher has been looking into the KerberosRenewalIT
failures. Has anyone been having any additional issues with the Kerberos
IT tests? I have been unsuccessful in getting through any of the four
Kerberos related ITs.
I've attempted to run each of the four Kerberos-related tests
individually.
KerberosIT tests fails with all 11 tests timing out after the allotted 5
minutes per test.
KerberosReplicationIT times out after 180 seconds.
KerberosRenewalIT fails after 540 seconds.
KerberosProxyIT is failing as well.
I've been using the following command for the tests with the appropriate
Kerberos IT proved for to the -Dit.test= argument.
mvn clean verify -Dtest=NoSuchTestExists -Dit.test=KerberosIT
-DfailIfNoTests=false
Should I chalk it up to my testing setup not being robust enough to
handle the tests or has anyone else experienced related failures?
------ Original Message ------
From: "Mike Miller" <mi...@gmail.com>
To: dev@accumulo.apache.org
Cc: "Josh Elser" <el...@apache.org>
Sent: 3/20/2018 4:02:32 PM
Subject: Re: [VOTE] Accumulo 1.7.4-rc1
>Well, just in case:
>Verified sha1, md5 and asc signatures for binary and source tarballs:
>gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
>gpg: using RSA key
>8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
>gpg: Good signature from "Christopher L Tubbs II (Christopher) <
>ctubbsii@gmail.com>" [unknown]
>gpg: aka "Christopher L Tubbs II (Developer) <
>ctubbsii@apache.org>" [unknown]
>gpg: WARNING: This key is not certified with a trusted signature!
>gpg: There is no indication that the signature belongs to the
>owner.
>Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B 835D 6F0C DAE7 00B6
>899D
>
>
>On Tue, Mar 20, 2018 at 2:32 PM, Christopher <ct...@apache.org>
>wrote:
>
>>I'm currently looking at the KerberosRenewalIT failures that seem to
>>be
>>persisting across branches. From the logs, it looks like the accumulo
>>services are trying to do ticket-cache based login renewals, instead
>>of
>>keytab-based renewals. This has been a problematic test for me before,
>>and
>>as such, I've gotten into the habit of ignoring it, but since I've not
>>been
>>able to get it to work on reruns, and it fails nearly 100% of the time
>>(if
>>not 100%) for me now, I decided to take a closer look. If it is doing
>>ticket-cache based renewals, that could indicate a bug in the Kerberos
>>authentication, and that would probably warrant a -1 from me... but I
>>will
>>continue to investigate first.
>>
>>Josh, you know more about the Kerberos stuff than anyone here, so if
>>you
>>have time/interest, I wouldn't mind getting your feedback on why this
>>test
>>might be failing for me.
>>
>>On Mon, Mar 19, 2018 at 3:44 PM Christopher <ct...@apache.org>
>>wrote:
>>
>> > Accumulo Developers,
>> >
>> > Please consider the following candidate for Accumulo 1.7.4.
>> >
>> > Git Commit:
>> > b2a59189108d736729432e81b3d5717000c6b891
>> > Branch:
>> > 1.7.4-rc1
>> >
>> > 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 \
>> > b2a59189108d736729432e81b3d5717000c6b891
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068
>> > Source (official release artifact):
>> > https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>4/accumulo-1.7.4-src.tar.gz
>> > Binary:
>> > https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/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://accumulo.apache.org/release/accumulo-1.7.4/
>> >
>> > 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 Thu Mar 22 20:00:00 UTC
>>2018
>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 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-1068/
>> > # note the trailing slash is needed
>> >
>> >
>>
Re: Re[2]: [VOTE] Accumulo 1.7.4-rc1
Posted by Keith Turner <ke...@deenlo.com>.
I successfully ran all test in 1.7.4rc1 that start with Kerberos,
except for KerberosRenewalIT which timed out after 541 secs. I am
going to try running KerberosRenewalIT in older 1.7 tags.
On Thu, Mar 22, 2018 at 3:20 PM, J. Mark Owens <jm...@gmail.com> wrote:
> I know that Christopher has been looking into the KerberosRenewalIT
> failures. Has anyone been having any additional issues with the Kerberos IT
> tests? I have been unsuccessful in getting through any of the four Kerberos
> related ITs.
>
> I've attempted to run each of the four Kerberos-related tests individually.
>
> KerberosIT tests fails with all 11 tests timing out after the allotted 5
> minutes per test.
> KerberosReplicationIT times out after 180 seconds.
> KerberosRenewalIT fails after 540 seconds.
> KerberosProxyIT is failing as well.
>
> I've been using the following command for the tests with the appropriate
> Kerberos IT proved for to the -Dit.test= argument.
>
> mvn clean verify -Dtest=NoSuchTestExists -Dit.test=KerberosIT
> -DfailIfNoTests=false
>
> Should I chalk it up to my testing setup not being robust enough to handle
> the tests or has anyone else experienced related failures?
>
>
>
>
> ------ Original Message ------
> From: "Mike Miller" <mi...@gmail.com>
> To: dev@accumulo.apache.org
> Cc: "Josh Elser" <el...@apache.org>
> Sent: 3/20/2018 4:02:32 PM
> Subject: Re: [VOTE] Accumulo 1.7.4-rc1
>
>> Well, just in case:
>> Verified sha1, md5 and asc signatures for binary and source tarballs:
>> gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
>> gpg: using RSA key 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
>> gpg: Good signature from "Christopher L Tubbs II (Christopher) <
>> ctubbsii@gmail.com>" [unknown]
>> gpg: aka "Christopher L Tubbs II (Developer) <
>> ctubbsii@apache.org>" [unknown]
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg: There is no indication that the signature belongs to the
>> owner.
>> Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B 835D 6F0C DAE7 00B6
>> 899D
>>
>>
>> On Tue, Mar 20, 2018 at 2:32 PM, Christopher <ct...@apache.org> wrote:
>>
>>> I'm currently looking at the KerberosRenewalIT failures that seem to be
>>> persisting across branches. From the logs, it looks like the accumulo
>>> services are trying to do ticket-cache based login renewals, instead of
>>> keytab-based renewals. This has been a problematic test for me before,
>>> and
>>> as such, I've gotten into the habit of ignoring it, but since I've not
>>> been
>>> able to get it to work on reruns, and it fails nearly 100% of the time
>>> (if
>>> not 100%) for me now, I decided to take a closer look. If it is doing
>>> ticket-cache based renewals, that could indicate a bug in the Kerberos
>>> authentication, and that would probably warrant a -1 from me... but I
>>> will
>>> continue to investigate first.
>>>
>>> Josh, you know more about the Kerberos stuff than anyone here, so if you
>>> have time/interest, I wouldn't mind getting your feedback on why this
>>> test
>>> might be failing for me.
>>>
>>> On Mon, Mar 19, 2018 at 3:44 PM Christopher <ct...@apache.org> wrote:
>>>
>>> > Accumulo Developers,
>>> >
>>> > Please consider the following candidate for Accumulo 1.7.4.
>>> >
>>> > Git Commit:
>>> > b2a59189108d736729432e81b3d5717000c6b891
>>> > Branch:
>>> > 1.7.4-rc1
>>> >
>>> > 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 \
>>> > b2a59189108d736729432e81b3d5717000c6b891
>>> >
>>> > Staging repo:
>>> > https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068
>>> > Source (official release artifact):
>>> > https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>> 4/accumulo-1.7.4-src.tar.gz
>>> > Binary:
>>> > https://repository.apache.org/content/repositories/
>>> orgapacheaccumulo-1068/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://accumulo.apache.org/release/accumulo-1.7.4/
>>> >
>>> > 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 Thu Mar 22 20:00:00 UTC 2018
>>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 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-1068/
>>> > # note the trailing slash is needed
>>> >
>>> >
>>>
>
RE: Re[2]: [VOTE] Accumulo 1.7.4-rc1
Posted by Ed Coleman <de...@etcoleman.com>.
This is historical information from when I was running tests against 1.7.3, but in case it helps with the current discussion. (File timestamps are last Feb / March of 2107)
I was using local / openbox VM and spun up a small AWS instance. I never got KerberosRenewalIT.testReadAndWriteThroughTicketLifetime » TestTimedOut test ti... to pass.
All other tests passed at least once.
This is the chart that I kept to keep track – fingers crossed that is get through in a readable form. The X indicates the test failed.
Instance Type
Test
AWS1
AWS2
AW3
OpenBox 1
OpenBox 2
OpenBox3
AssignmentThreadsIT.testConcurrentAssignmentPerformance:91
x
x
x
BadDeleteMarkersCreatedIT>AccumuloClusterIT.teardownCluster:223 » TestTimedOut
x
ChaoticBalancerIT.test:80->Object.wait:502->Object.wait:-2 » TestTimedOut test...
x
x
ConditionalWriterIT.testTrace:1476 » TestTimedOut test timed out after 60 seco...
x
DurabilityIT.testWriteSpeed:103 log should be faster than flush
x
x
x
x
FateStarvationIT.run:79 » Runtime java.lang.RuntimeException: org.apache.zooke...
x
KerberosRenewalIT.testReadAndWriteThroughTicketLifetime » TestTimedOut test ti...
x
x
x
x
x
x
ShellServerIT.trace:1444
x
x
TabletStateChangeIteratorIT.test:100 No tables should need attention expected:<0> but was:<1>
x
x
UnorderedWorkAssignerReplicationIT.dataWasReplicatedToThePeerWithoutDrain:548 » TableOffline
KerberosReplicationIT.dataReplicatedToCorrectTable:224 » TestTimedOut test tim...
x
-----Original Message-----
From: J. Mark Owens [mailto:jmarkowe@gmail.com]
Sent: Thursday, March 22, 2018 3:20 PM
To: dev@accumulo.apache.org
Subject: Re[2]: [VOTE] Accumulo 1.7.4-rc1
I know that Christopher has been looking into the KerberosRenewalIT failures. Has anyone been having any additional issues with the Kerberos IT tests? I have been unsuccessful in getting through any of the four Kerberos related ITs.
I've attempted to run each of the four Kerberos-related tests individually.
KerberosIT tests fails with all 11 tests timing out after the allotted 5 minutes per test.
KerberosReplicationIT times out after 180 seconds.
KerberosRenewalIT fails after 540 seconds.
KerberosProxyIT is failing as well.
I've been using the following command for the tests with the appropriate Kerberos IT proved for to the -Dit.test= argument.
mvn clean verify -Dtest=NoSuchTestExists -Dit.test=KerberosIT -DfailIfNoTests=false
Should I chalk it up to my testing setup not being robust enough to handle the tests or has anyone else experienced related failures?
------ Original Message ------
From: "Mike Miller" < <ma...@gmail.com> michaelpmiller@gmail.com>
To: <ma...@accumulo.apache.org> dev@accumulo.apache.org
Cc: "Josh Elser" < <ma...@apache.org> elserj@apache.org>
Sent: 3/20/2018 4:02:32 PM
Subject: Re: [VOTE] Accumulo 1.7.4-rc1
>Well, just in case:
>Verified sha1, md5 and asc signatures for binary and source tarballs:
>gpg: Signature made Mon 19 Mar 2018 03:38:42 PM EDT
>gpg: using RSA key
>8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D
>gpg: Good signature from "Christopher L Tubbs II (Christopher) <
> <ma...@gmail.com> ctubbsii@gmail.com>" [unknown]
>gpg: aka "Christopher L Tubbs II (Developer) <
> <ma...@apache.org> ctubbsii@apache.org>" [unknown]
>gpg: WARNING: This key is not certified with a trusted signature!
>gpg: There is no indication that the signature belongs to the
>owner.
>Primary key fingerprint: 8CC4 F8A2 B29C 2B04 0F2B 835D 6F0C DAE7 00B6
>899D
>
>
>On Tue, Mar 20, 2018 at 2:32 PM, Christopher < <ma...@apache.org> ctubbsii@apache.org>
>wrote:
>
>>I'm currently looking at the KerberosRenewalIT failures that seem to
>>be
>>persisting across branches. From the logs, it looks like the accumulo
>>services are trying to do ticket-cache based login renewals, instead
>>of
>>keytab-based renewals. This has been a problematic test for me before,
>>and
>>as such, I've gotten into the habit of ignoring it, but since I've not
>>been
>>able to get it to work on reruns, and it fails nearly 100% of the time
>>(if
>>not 100%) for me now, I decided to take a closer look. If it is doing
>>ticket-cache based renewals, that could indicate a bug in the Kerberos
>>authentication, and that would probably warrant a -1 from me... but I
>>will
>>continue to investigate first.
>>
>>Josh, you know more about the Kerberos stuff than anyone here, so if
>>you
>>have time/interest, I wouldn't mind getting your feedback on why this
>>test
>>might be failing for me.
>>
>>On Mon, Mar 19, 2018 at 3:44 PM Christopher < <ma...@apache.org> ctubbsii@apache.org>
>>wrote:
>>
>> > Accumulo Developers,
>> >
>> > Please consider the following candidate for Accumulo 1.7.4.
>> >
>> > Git Commit:
>> > b2a59189108d736729432e81b3d5717000c6b891
>> > Branch:
>> > 1.7.4-rc1
>> >
>> > 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 \
>> > b2a59189108d736729432e81b3d5717000c6b891
>> >
>> > Staging repo:
>> > <https://repository.apache.org/content/repositories/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068
>> > Source (official release artifact):
>> > <https://repository.apache.org/content/repositories/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/org/apache/accumulo/accumulo/1.7.
>>4/accumulo-1.7.4-src.tar.gz
>> > Binary:
>> > <https://repository.apache.org/content/repositories/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/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> https://www.apache.org/dist/accumulo/KEYS
>> > (Expected fingerprint: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
>> >
>> > Release notes (in progress) can be found at:
>> > <https://accumulo.apache.org/release/accumulo-1.7.4/> https://accumulo.apache.org/release/accumulo-1.7.4/
>> >
>> > 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 Thu Mar 22 20:00:00 UTC
>>2018
>> > (Thu Mar 22 16:00:00 EDT 2018 / Thu Mar 22 13:00:00 PDT 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/> https://repository.apache.org/content/repositories/
>>orgapacheaccumulo-1068/
>> > # note the trailing slash is needed
>> >
>> >
>>