You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Keith Turner <ke...@deenlo.com> on 2017/03/01 20:30:01 UTC
Re: [Release Test - No Vote] Accumulo 1.7.3-rc0
I completed a successful 1 day run of CI+verification w/o agitation on
EC2 using Muchos using the staged ninary tar.
When the table got to 1K tablets, ingest slowed down a good bit. I
made the following config changes suggested in this post[1] and things
sped back up.
config -s table.durability=flush
config -t accumulo.metadata -d table.durability
config -t accumulo.root -d table.durability
Cluster info :
1 leader m3.xlarge
8 workers d2.xlarge
Centos 7
Hadoop 2.7.3
Zookeeper 3.4.9
open jdk 1.8 from Centos yum repo
Verification output
REFERENCED=36410538934
UNREFERENCED=7190163
Now I am going to start a run with agitation.
[1]: http://accumulo.apache.org/blog/2016/11/02/durability-performance.html
On Sun, Feb 26, 2017 at 10:31 AM, Ed Coleman <de...@etcoleman.com> wrote:
> I've run through the release process using:
>
> ./assemble/build.sh --create-release-candidate
>
> The artifacts have been published and the branch pushed to the Accumulo repository. This test release only contains the code for 1.7.3, other artifacts (release notes, web pages,...) have not be added / modified. I did this to 1) see if it would actually work for me, 2) to help determine what configuration / steps I have incorrect.
>
> Following the instructions for creating a release, I'm a little lost with the instructions versus what the build script did. For example,
>
> "One unwanted side-effect of this approach is that after creating this branch, but before invoking release:perform, you must edit the release.properties to add the -rcN suffix to the value of scm.tag."
>
> Is this something that I need to do between stages of the script? Answering the prompts seemed to push things through and did not require additional information.
>
> Looking at the referenced keys (https://www.apache.org/dist/accumulo/KEYS) my key is not in that file - is this something I need to add via a separate update / commit?
>
> Anyway, for reference, the unmodified, generated email message follows, not expecting a vote on this version:
>
> ============================================================
> Subject: [VOTE] Accumulo 1.7.3-rc0
> ============================================================
> Accumulo Developers,
>
> Please consider the following candidate for Accumulo 1.7.3.
>
> Git Commit:
> d5968ad78366658d76acfbc1ceb1878951c2567c
> Branch:
> 1.7.3-rc0
>
> If this vote passes, a gpg-signed tag will be created using:
> git tag -f -m 'Apache Accumulo 1.7.3' -s rel/1.7.3 d5968ad78366658d76acfbc1ceb1878951c2567c
>
> Staging repo: https://repository.apache.org/content/repositories/orgapacheaccumulo-1063
> Source (official release artifact): https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-src.tar.gz
> Binary: https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-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: D87F9F417753D0C88598437EFC4368E0864BCC36)
>
> Release notes (in progress) can be found at: https://accumulo.apache.org/release_notes/1.7.3
>
> 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.3 release of Apache Accumulo.
>
> This vote will end on Wed Mar 1 15:30:00 UTC 2017
> (Wed Mar 1 10:30:00 EST 2017 / Wed Mar 1 07:30:00 PST 2017)
>
> 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-1063/
> # note the trailing slash is needed
> ============================================================
>
Re: [Release Test - No Vote] Accumulo 1.7.3-rc0
Posted by Keith Turner <ke...@deenlo.com>.
I completed a successful 24hr CI run with agitation. Same env as the last test.
org.apache.accumulo.test.continuous.ContinuousVerify$Counts
REFERENCED=26528923694
UNREFERENCED=7165754
On Wed, Mar 1, 2017 at 3:30 PM, Keith Turner <ke...@deenlo.com> wrote:
> I completed a successful 1 day run of CI+verification w/o agitation on
> EC2 using Muchos using the staged ninary tar.
>
> When the table got to 1K tablets, ingest slowed down a good bit. I
> made the following config changes suggested in this post[1] and things
> sped back up.
>
> config -s table.durability=flush
> config -t accumulo.metadata -d table.durability
> config -t accumulo.root -d table.durability
>
> Cluster info :
>
> 1 leader m3.xlarge
> 8 workers d2.xlarge
> Centos 7
> Hadoop 2.7.3
> Zookeeper 3.4.9
> open jdk 1.8 from Centos yum repo
>
> Verification output
> REFERENCED=36410538934
> UNREFERENCED=7190163
>
> Now I am going to start a run with agitation.
>
> [1]: http://accumulo.apache.org/blog/2016/11/02/durability-performance.html
>
> On Sun, Feb 26, 2017 at 10:31 AM, Ed Coleman <de...@etcoleman.com> wrote:
>> I've run through the release process using:
>>
>> ./assemble/build.sh --create-release-candidate
>>
>> The artifacts have been published and the branch pushed to the Accumulo repository. This test release only contains the code for 1.7.3, other artifacts (release notes, web pages,...) have not be added / modified. I did this to 1) see if it would actually work for me, 2) to help determine what configuration / steps I have incorrect.
>>
>> Following the instructions for creating a release, I'm a little lost with the instructions versus what the build script did. For example,
>>
>> "One unwanted side-effect of this approach is that after creating this branch, but before invoking release:perform, you must edit the release.properties to add the -rcN suffix to the value of scm.tag."
>>
>> Is this something that I need to do between stages of the script? Answering the prompts seemed to push things through and did not require additional information.
>>
>> Looking at the referenced keys (https://www.apache.org/dist/accumulo/KEYS) my key is not in that file - is this something I need to add via a separate update / commit?
>>
>> Anyway, for reference, the unmodified, generated email message follows, not expecting a vote on this version:
>>
>> ============================================================
>> Subject: [VOTE] Accumulo 1.7.3-rc0
>> ============================================================
>> Accumulo Developers,
>>
>> Please consider the following candidate for Accumulo 1.7.3.
>>
>> Git Commit:
>> d5968ad78366658d76acfbc1ceb1878951c2567c
>> Branch:
>> 1.7.3-rc0
>>
>> If this vote passes, a gpg-signed tag will be created using:
>> git tag -f -m 'Apache Accumulo 1.7.3' -s rel/1.7.3 d5968ad78366658d76acfbc1ceb1878951c2567c
>>
>> Staging repo: https://repository.apache.org/content/repositories/orgapacheaccumulo-1063
>> Source (official release artifact): https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-src.tar.gz
>> Binary: https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-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: D87F9F417753D0C88598437EFC4368E0864BCC36)
>>
>> Release notes (in progress) can be found at: https://accumulo.apache.org/release_notes/1.7.3
>>
>> 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.3 release of Apache Accumulo.
>>
>> This vote will end on Wed Mar 1 15:30:00 UTC 2017
>> (Wed Mar 1 10:30:00 EST 2017 / Wed Mar 1 07:30:00 PST 2017)
>>
>> 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-1063/
>> # note the trailing slash is needed
>> ============================================================
>>
Re: [Release Test - No Vote] Accumulo 1.7.3-rc0
Posted by Michael Wall <mj...@gmail.com>.
Signatures checked out. Ran 'mvn verify -Psunny' successfully on my mac
with Java 1.7 in 43 min. Looks good Ed.
On Wed, Mar 1, 2017 at 4:21 PM Michael Wall <mj...@gmail.com> wrote:
> Awesome, thanks for starting this Keith. I talked with Ed and was going
> to start it up tomorrow if you hadn't already. Let me know if you need any
> help.
>
>
> On Wed, Mar 1, 2017 at 3:30 PM Keith Turner <ke...@deenlo.com> wrote:
>
> I completed a successful 1 day run of CI+verification w/o agitation on
> EC2 using Muchos using the staged ninary tar.
>
> When the table got to 1K tablets, ingest slowed down a good bit. I
> made the following config changes suggested in this post[1] and things
> sped back up.
>
> config -s table.durability=flush
> config -t accumulo.metadata -d table.durability
> config -t accumulo.root -d table.durability
>
> Cluster info :
>
> 1 leader m3.xlarge
> 8 workers d2.xlarge
> Centos 7
> Hadoop 2.7.3
> Zookeeper 3.4.9
> open jdk 1.8 from Centos yum repo
>
> Verification output
> REFERENCED=36410538934
> UNREFERENCED=7190163
>
> Now I am going to start a run with agitation.
>
> [1]:
> http://accumulo.apache.org/blog/2016/11/02/durability-performance.html
>
> On Sun, Feb 26, 2017 at 10:31 AM, Ed Coleman <de...@etcoleman.com> wrote:
> > I've run through the release process using:
> >
> > ./assemble/build.sh --create-release-candidate
> >
> > The artifacts have been published and the branch pushed to the Accumulo
> repository. This test release only contains the code for 1.7.3, other
> artifacts (release notes, web pages,...) have not be added / modified. I
> did this to 1) see if it would actually work for me, 2) to help determine
> what configuration / steps I have incorrect.
> >
> > Following the instructions for creating a release, I'm a little lost
> with the instructions versus what the build script did. For example,
> >
> > "One unwanted side-effect of this approach is that after creating this
> branch, but before invoking release:perform, you must edit the
> release.properties to add the -rcN suffix to the value of scm.tag."
> >
> > Is this something that I need to do between stages of the script?
> Answering the prompts seemed to push things through and did not require
> additional information.
> >
> > Looking at the referenced keys (
> https://www.apache.org/dist/accumulo/KEYS) my key is not in that file -
> is this something I need to add via a separate update / commit?
> >
> > Anyway, for reference, the unmodified, generated email message follows,
> not expecting a vote on this version:
> >
> > ============================================================
> > Subject: [VOTE] Accumulo 1.7.3-rc0
> > ============================================================
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.3.
> >
> > Git Commit:
> > d5968ad78366658d76acfbc1ceb1878951c2567c
> > Branch:
> > 1.7.3-rc0
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.3' -s rel/1.7.3
> d5968ad78366658d76acfbc1ceb1878951c2567c
> >
> > Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1063
> > Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-src.tar.gz
> > Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-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: D87F9F417753D0C88598437EFC4368E0864BCC36)
> >
> > Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.3
> >
> > 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.3 release of Apache Accumulo.
> >
> > This vote will end on Wed Mar 1 15:30:00 UTC 2017
> > (Wed Mar 1 10:30:00 EST 2017 / Wed Mar 1 07:30:00 PST 2017)
> >
> > 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-1063/
> > # note the trailing slash is needed
> > ============================================================
> >
>
>
Re: [Release Test - No Vote] Accumulo 1.7.3-rc0
Posted by Michael Wall <mj...@gmail.com>.
Awesome, thanks for starting this Keith. I talked with Ed and was going to
start it up tomorrow if you hadn't already. Let me know if you need any
help.
On Wed, Mar 1, 2017 at 3:30 PM Keith Turner <ke...@deenlo.com> wrote:
> I completed a successful 1 day run of CI+verification w/o agitation on
> EC2 using Muchos using the staged ninary tar.
>
> When the table got to 1K tablets, ingest slowed down a good bit. I
> made the following config changes suggested in this post[1] and things
> sped back up.
>
> config -s table.durability=flush
> config -t accumulo.metadata -d table.durability
> config -t accumulo.root -d table.durability
>
> Cluster info :
>
> 1 leader m3.xlarge
> 8 workers d2.xlarge
> Centos 7
> Hadoop 2.7.3
> Zookeeper 3.4.9
> open jdk 1.8 from Centos yum repo
>
> Verification output
> REFERENCED=36410538934
> UNREFERENCED=7190163
>
> Now I am going to start a run with agitation.
>
> [1]:
> http://accumulo.apache.org/blog/2016/11/02/durability-performance.html
>
> On Sun, Feb 26, 2017 at 10:31 AM, Ed Coleman <de...@etcoleman.com> wrote:
> > I've run through the release process using:
> >
> > ./assemble/build.sh --create-release-candidate
> >
> > The artifacts have been published and the branch pushed to the Accumulo
> repository. This test release only contains the code for 1.7.3, other
> artifacts (release notes, web pages,...) have not be added / modified. I
> did this to 1) see if it would actually work for me, 2) to help determine
> what configuration / steps I have incorrect.
> >
> > Following the instructions for creating a release, I'm a little lost
> with the instructions versus what the build script did. For example,
> >
> > "One unwanted side-effect of this approach is that after creating this
> branch, but before invoking release:perform, you must edit the
> release.properties to add the -rcN suffix to the value of scm.tag."
> >
> > Is this something that I need to do between stages of the script?
> Answering the prompts seemed to push things through and did not require
> additional information.
> >
> > Looking at the referenced keys (
> https://www.apache.org/dist/accumulo/KEYS) my key is not in that file -
> is this something I need to add via a separate update / commit?
> >
> > Anyway, for reference, the unmodified, generated email message follows,
> not expecting a vote on this version:
> >
> > ============================================================
> > Subject: [VOTE] Accumulo 1.7.3-rc0
> > ============================================================
> > Accumulo Developers,
> >
> > Please consider the following candidate for Accumulo 1.7.3.
> >
> > Git Commit:
> > d5968ad78366658d76acfbc1ceb1878951c2567c
> > Branch:
> > 1.7.3-rc0
> >
> > If this vote passes, a gpg-signed tag will be created using:
> > git tag -f -m 'Apache Accumulo 1.7.3' -s rel/1.7.3
> d5968ad78366658d76acfbc1ceb1878951c2567c
> >
> > Staging repo:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1063
> > Source (official release artifact):
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-src.tar.gz
> > Binary:
> https://repository.apache.org/content/repositories/orgapacheaccumulo-1063/org/apache/accumulo/accumulo/1.7.3/accumulo-1.7.3-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: D87F9F417753D0C88598437EFC4368E0864BCC36)
> >
> > Release notes (in progress) can be found at:
> https://accumulo.apache.org/release_notes/1.7.3
> >
> > 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.3 release of Apache Accumulo.
> >
> > This vote will end on Wed Mar 1 15:30:00 UTC 2017
> > (Wed Mar 1 10:30:00 EST 2017 / Wed Mar 1 07:30:00 PST 2017)
> >
> > 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-1063/
> > # note the trailing slash is needed
> > ============================================================
> >
>