Re: [VOTE] Release Apache Storm 2.2.0 (RC2)

[Kishorkumar Patil]

+1

I compiled from the source code tar.gz , unit test passed.
The *ThroughputVsLatency* check and other manual checks for Basic DRPC
works fine.
UI functionality - search/profile actions work.
LogViewer - search functionality works.

-Kishor

On Thu, Jun 18, 2020 at 2:18 PM Govind Menon  wrote:

> This is a call to vote on releasing Apache Storm 2.2.0 (As a personal note
> I would like to thank P. Taylor Goetz and Ethan Li for all the
> documentation they have set up to make releasing easier)
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc2/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v2.2.0:
>
>
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=de1f107e58bfe61aa43ae87e26f657f76e004a19
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc2/apache-storm-2.2.0-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc2/
>
> The release artifacts are signed with the following key:
>
> https://www.apache.org/dist/storm/KEYS
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1095
>
> Please vote on releasing this package as Apache Storm 2.2.0.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.2.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>

Re: [VOTE] Release Apache Storm 2.2.0 (RC2)

[Kishorkumar Patil]

+1

I compiled from the source code tar.gz , unit test passed.
The *ThroughputVsLatency* check and other manual checks for Basic DRPC
works fine.
UI functionality - search/profile actions work.
LogViewer - search functionality works.


-Kishor

On Thu, Jun 18, 2020 at 2:18 PM Govind Menon  wrote:

> This is a call to vote on releasing Apache Storm 2.2.0 (As a personal note
> I would like to thank P. Taylor Goetz and Ethan Li for all the
> documentation they have set up to make releasing easier)
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc2/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v2.2.0:
>
>
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=de1f107e58bfe61aa43ae87e26f657f76e004a19
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc2/apache-storm-2.2.0-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc2/
>
> The release artifacts are signed with the following key:
>
> https://www.apache.org/dist/storm/KEYS
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1095
>
> Please vote on releasing this package as Apache Storm 2.2.0.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.2.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>

Re: [VOTE] Release Apache Storm 2.2.0 (RC1)

[Kishorkumar Patil]

Thanks Govind.

-Kishor

On Mon, Jun 15, 2020 at 2:03 PM Govind Menon 
wrote:

> Will close the vote and start a new one.
>
> On Mon, 15 Jun 2020 at 12:57, Ethan Li  wrote:
>
>> I cherry-picked the change to 2.2.x-branch. This unit test should be more
>> stable in environments with low cpu resources now. Thanks.
>>
>> > On Jun 15, 2020, at 12:34 PM, Kishorkumar Patil <
>> kishorvpa...@apache.org> wrote:
>> >
>> > The rest of the tests are working fine. Manual running of throughput vs
>> > latency and other manual checks for DRPC work fine.
>> > The unit test *ExecutorTransferMultiThreadingTest* we added fails
>> > consistently for me on VM/mac for low CPU. So -1 on this release
>> candidate.
>> > Ethan has a patch to fix this -
>> > https://github.com/apache/storm/pull/3286/files. We  should cut the
>> next
>> > release candidate with this patch.
>> >
>> > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time
>> > elapsed: 1.582 s <<< FAILURE! - in
>> > org.apache.storm.executor.ExecutorTransferMultiThreadingTest
>> > [ERROR] testExecutorTransfer  Time elapsed: 1.582 s  <<< FAILURE!
>> > java.lang.AssertionError: expected:<10> but was:<0>
>> >   at org.junit.Assert.fail(Assert.java:88)
>> >   at org.junit.Assert.failNotEquals(Assert.java:834)
>> >   at org.junit.Assert.assertEquals(Assert.java:645)
>> >   at org.junit.Assert.assertEquals(Assert.java:631)
>> >   at
>> org.apache.storm.executor.ExecutorTransferMultiThreadingTest$SingleThreadedConsumer.finalCheck(ExecutorTransferMultiThreadingTest.java:187)
>> >   at
>> org.apache.storm.executor.ExecutorTransferMultiThreadingTest.testExecutorTransfer(ExecutorTransferMultiThreadingTest.java:136)
>> >   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >
>> > -Kishor
>> >
>> >
>> > On Mon, Jun 15, 2020 at 1:55 AM Julien Nioche <
>> lists.digitalpeb...@gmail.com>
>> > wrote:
>> >
>> >> +1 (non binding)
>> >>
>> >> I have been running a crawl with StormCrawler successfully for the
>> last 2
>> >> days, no errors or exceptions to report. Thanks everyone!
>> >>
>> >> On Fri, 12 Jun 2020 at 00:03, Govind Menon  wrote:
>> >>
>> >>> This is a call to vote on releasing Apache Storm 2.2.0 (As a personal
>> >> note
>> >>> I would like to thank P. Taylor Goetz and Ethan Li for all the
>> >>> documentation they have set up to make releasing easier)
>> >>>
>> >>> Full list of changes in this release:
>> >>>
>> >>>
>> >>>
>> >>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc1/RELEASE_NOTES.html
>> >>>
>> >>> The tag/commit to be voted upon is v2.2.0:
>> >>>
>> >>>
>> >>>
>> >>
>> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=de1f107e58bfe61aa43ae87e26f657f76e004a19
>> >>>
>> >>> The source archive being voted upon can be found here:
>> >>>
>> >>>
>> >>>
>> >>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc1/apache-storm-2.2.0-src.tar.gz
>> >>>
>> >>> Other release files, signatures and digests can be found here:
>> >>>
>> >>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc1/
>> >>>
>> >>> The release artifacts are signed with the following key:
>> >>>
>> >>> https://www.apache.org/dist/storm/KEYS
>> >>>
>> >>> The Nexus staging repository for this release is:
>> >>>
>> >>>
>> https://repository.apache.org/content/repositories/orgapachestorm-1094
>> >>>
>> >>> Please vote on releasing this package as Apache Storm 2.2.0.
>> >>>
>> >>> When voting, please list the actions taken to verify the release.
>> >>>
>> >>> This vote will be open for at least 72 hours.
>> >>>
>> >>> [ ] +1 Release this package as Apache Storm 2.2.0
>> >>> [ ]  0 No opinion
>> >>> [ ] -1 Do not release this package because...
>> >>>
>> >>> Thanks to everyone who contributed to this release.
>> >>>
>> >>
>> >>
>> >> --
>> >>
>> >> *Open Source Solutions for Text Engineering*
>> >>
>> >> http://www.digitalpebble.com
>> >> http://digitalpebble.blogspot.com/
>> >> #digitalpebble <http://twitter.com/digitalpebble>
>> >>
>>
>>

Re: [VOTE] Release Apache Storm 2.2.0 (RC1)

[Kishorkumar Patil]

The rest of the tests are working fine. Manual running of throughput vs
latency and other manual checks for DRPC work fine.
The unit test *ExecutorTransferMultiThreadingTest* we added fails
consistently for me on VM/mac for low CPU. So -1 on this release candidate.
Ethan has a patch to fix this -
https://github.com/apache/storm/pull/3286/files. We  should cut the next
release candidate with this patch.

[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time
elapsed: 1.582 s <<< FAILURE! - in
org.apache.storm.executor.ExecutorTransferMultiThreadingTest
[ERROR] testExecutorTransfer  Time elapsed: 1.582 s  <<< FAILURE!
java.lang.AssertionError: expected:<10> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at 
org.apache.storm.executor.ExecutorTransferMultiThreadingTest$SingleThreadedConsumer.finalCheck(ExecutorTransferMultiThreadingTest.java:187)
at 
org.apache.storm.executor.ExecutorTransferMultiThreadingTest.testExecutorTransfer(ExecutorTransferMultiThreadingTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

-Kishor


On Mon, Jun 15, 2020 at 1:55 AM Julien Nioche 
wrote:

> +1 (non binding)
>
> I have been running a crawl with StormCrawler successfully for the last 2
> days, no errors or exceptions to report. Thanks everyone!
>
> On Fri, 12 Jun 2020 at 00:03, Govind Menon  wrote:
>
> > This is a call to vote on releasing Apache Storm 2.2.0 (As a personal
> note
> > I would like to thank P. Taylor Goetz and Ethan Li for all the
> > documentation they have set up to make releasing easier)
> >
> > Full list of changes in this release:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc1/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v2.2.0:
> >
> >
> >
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=de1f107e58bfe61aa43ae87e26f657f76e004a19
> >
> > The source archive being voted upon can be found here:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc1/apache-storm-2.2.0-src.tar.gz
> >
> > Other release files, signatures and digests can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0-rc1/
> >
> > The release artifacts are signed with the following key:
> >
> > https://www.apache.org/dist/storm/KEYS
> >
> > The Nexus staging repository for this release is:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1094
> >
> > Please vote on releasing this package as Apache Storm 2.2.0.
> >
> > When voting, please list the actions taken to verify the release.
> >
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 2.2.0
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
>
>
> --
>
> *Open Source Solutions for Text Engineering*
>
> http://www.digitalpebble.com
> http://digitalpebble.blogspot.com/
> #digitalpebble 
>

Re: [VOTE] Release Apache Storm 2.2.0

[Kishorkumar Patil]

Hi Govid/Ethan,

Since the patch https://github.com/apache/storm/pull/3280 is merged, can we
create the next release candidate?

-Kishor

On Fri, Jun 5, 2020 at 8:12 AM Julien Nioche 
wrote:

> That's great thanks Ethan
>
> On Thu, 4 Jun 2020 at 19:02, Ethan Li  wrote:
>
> > The fix is ready. Please review
> https://github.com/apache/storm/pull/3280
> > <https://github.com/apache/storm/pull/3280>
> >
> > > On Jun 4, 2020, at 11:34 AM, Kishorkumar Patil <
> kishorvpa...@apache.org>
> > wrote:
> > >
> > > Hi Julian,
> > >
> > > I agree with you on this. Ethan has a fix that will resolve both these
> > > issues. We should get the change in and cut another RC.
> > >
> > > -Kishor
> > >
> > >
> > > On Thu, Jun 4, 2020 at 12:23 PM Julien Nioche <
> > lists.digitalpeb...@gmail.com>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> Great to see that there has been some work on Storm 2 recently but I
> am
> > >> afraid I'll have to cast a (non-binding) -1 because of STORM-3620
> > >> <https://issues.apache.org/jira/browse/STORM-3620> and STORM-3582
> > >> <https://issues.apache.org/jira/projects/STORM/issues/STORM-3582>.
> > >>
> > >> I have tried to get StormCrawler to work with Storm 2.x but the issues
> > >> above have prevented me from doing so. At least one other person has
> had
> > >> the same problems as you can see in the JIRAs above.
> > >>
> > >> I think these are serious issues and they should be addressed in the
> > next
> > >> release. I would be very happy to help if I can.
> > >>
> > >> Julien
> > >>
> > >> On Thu, 4 Jun 2020 at 00:00, Govind Menon  wrote:
> > >>
> > >>> This is a call to vote on releasing Apache Storm 2.2.0 (As a personal
> > >> note
> > >>> I would like to thank P. Taylor Goetz and Ethan Li for all the
> > >>> documentation they have set up to make releasing easier)
> > >>>
> > >>> Full list of changes in this release:
> > >>>
> > >>>
> > >>>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/RELEASE_NOTES.html
> > >>>
> > >>> The tag/commit to be voted upon is v2.2.0:
> > >>>
> > >>>
> > >>>
> > >>
> >
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=6326b0c783c0025440c629e17653c0c7577f27e6
> > >>>
> > >>> The source archive being voted upon can be found here:
> > >>>
> > >>>
> > >>>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/apache-storm-2.2.0-src.tar.gz
> > >>>
> > >>> Other release files, signatures and digests can be found here:
> > >>>
> > >>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/
> > >>>
> > >>> The release artifacts are signed with the following key:
> > >>>
> > >>> https://www.apache.org/dist/storm/KEYS
> > >>>
> > >>> The Nexus staging repository for this release is:
> > >>>
> > >>>
> https://repository.apache.org/content/repositories/orgapachestorm-1091
> > >>>
> > >>> Please vote on releasing this package as Apache Storm 2.2.0.
> > >>>
> > >>> When voting, please list the actions taken to verify the release.
> > >>>
> > >>> This vote will be open for at least 72 hours.
> > >>>
> > >>> [ ] +1 Release this package as Apache Storm 2.2.0
> > >>> [ ]  0 No opinion
> > >>> [ ] -1 Do not release this package because...
> > >>>
> > >>> Thanks to everyone who contributed to this release.
> > >>>
> > >>
> > >>
> > >> --
> > >>
> > >> *Open Source Solutions for Text Engineering*
> > >>
> > >> http://www.digitalpebble.com
> > >> http://digitalpebble.blogspot.com/
> > >> #digitalpebble <http://twitter.com/digitalpebble>
> > >>
> >
> >
>
> --
>
> *Open Source Solutions for Text Engineering*
>
> http://www.digitalpebble.com
> http://digitalpebble.blogspot.com/
> #digitalpebble <http://twitter.com/digitalpebble>
>

Re: [VOTE] Release Apache Storm 2.2.0

[Kishorkumar Patil]

Hi Julian,

I agree with you on this. Ethan has a fix that will resolve both these
issues. We should get the change in and cut another RC.

-Kishor


On Thu, Jun 4, 2020 at 12:23 PM Julien Nioche 
wrote:

> Hi,
>
> Great to see that there has been some work on Storm 2 recently but I am
> afraid I'll have to cast a (non-binding) -1 because of STORM-3620
>  and STORM-3582
> .
>
> I have tried to get StormCrawler to work with Storm 2.x but the issues
> above have prevented me from doing so. At least one other person has had
> the same problems as you can see in the JIRAs above.
>
> I think these are serious issues and they should be addressed in the next
> release. I would be very happy to help if I can.
>
> Julien
>
> On Thu, 4 Jun 2020 at 00:00, Govind Menon  wrote:
>
> > This is a call to vote on releasing Apache Storm 2.2.0 (As a personal
> note
> > I would like to thank P. Taylor Goetz and Ethan Li for all the
> > documentation they have set up to make releasing easier)
> >
> > Full list of changes in this release:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v2.2.0:
> >
> >
> >
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=6326b0c783c0025440c629e17653c0c7577f27e6
> >
> > The source archive being voted upon can be found here:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/apache-storm-2.2.0-src.tar.gz
> >
> > Other release files, signatures and digests can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/
> >
> > The release artifacts are signed with the following key:
> >
> > https://www.apache.org/dist/storm/KEYS
> >
> > The Nexus staging repository for this release is:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1091
> >
> > Please vote on releasing this package as Apache Storm 2.2.0.
> >
> > When voting, please list the actions taken to verify the release.
> >
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 2.2.0
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
>
>
> --
>
> *Open Source Solutions for Text Engineering*
>
> http://www.digitalpebble.com
> http://digitalpebble.blogspot.com/
> #digitalpebble 
>

Re: [VOTE] Release Apache Storm 2.1.0 (rc5)

[Kishorkumar Patil]

+1.

Built from code. Executed based wordcount and drpc topologies. I executed
and compared Based ThroughtputVsLatency and performance and resource uses
is same as 2.0.0 release.

-Kishor

On Wed, Oct 30, 2019 at 3:44 PM Aaron Gresch  wrote:

> +1
>
> Built and ran tests from source.
> Ran local WordCountTopology, ran a rebalance and kill and looked at logs
> for ERRORs.
> Validated storm blobstore list and jar command with -c option worked.
>
>
> On Fri, Oct 25, 2019 at 3:09 PM Ethan Li  wrote:
>
> > This is a call to vote on releasing Apache Storm 2.1.0 (rc5)
> >
> > Full list of changes in this release:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.0-rc5/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v2.1.0:
> >
> >
> >
> https://gitbox.apache.org/repos/asf?p=storm.git;a=tree;h=9a4a245efeb6d74dc01b0feac77bda0e5709b3f6;hb=79fc9b3e6aeec623b42d165536a936d28f2b12f1
> >
> > The source archive being voted upon can be found here:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.0-rc5/apache-storm-2.1.0-src.tar.gz
> >
> > Other release files, signatures and digests can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.0-rc5
> >
> > The release artifacts are signed with the following key:
> >
> > https://www.apache.org/dist/storm/KEYS
> >
> > The Nexus staging repository for this release is:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1089/
> >
> > Please vote on releasing this package as Apache Storm 2.1.0.
> >
> > When voting, please list the actions taken to verify the release.
> >
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 2.1.0
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
>

Re: Steps for Updating Storm Website

[Kishorkumar Patil]

Roshan,

Please find documentation for adding/updating site documentation
https://github.com/apache/storm/blob/master/DEVELOPER.md#contribute-documentation
.

Essentially, it comes down to updating the github:
https://git-wip-us.apache.org/repos/asf?p=storm-site.git;a=summary

-Kishor


On Mon, Sep 30, 2019 at 6:34 PM Roshan Naik 
wrote:

> Taylor,Could you please share the steps for updating the Storm
> website?
> -roshan

Re: [ANNOUNCE] New Committer/PMC Member Aaron Gresch

[Kishorkumar Patil]

Congratulations Aaron!

On Sat, Aug 10, 2019 at 8:14 PM Derek Dagit  wrote:

> Welcome, Aaron!
>
> On Sat, Aug 10, 2019 at 08:18:40AM -0500, Ethan Li wrote:
> >
> > Congratulations, Aaron!
> >
> > Ethan Li
> >
> > > On Aug 10, 2019, at 07:36, Alexandre Vermeerbergen <
> avermeerber...@gmail.com> wrote:
> > >
> > > This is great news (the more PMC members, the more healthly the Apache
> > > Storm project is), welcome Aaron!
> > >
> > > Alexandre Vermeerbergen
> > >
> > > Le sam. 10 août 2019 à 10:47, Stig Rohde Døssing
> > >  a écrit :
> > >>
> > >> I'm happy to announce that Aaron Gresch is now a member of the Storm
> PMC.
> > >>
> > >> Aaron has been active contributing to Storm for a while now. His
> > >> contributions have a good spread around the codebase, in particular
> having
> > >> to do with the blob store, metrics system and scheduling. He helped
> > >> implement metrics v2.
> > >>
> > >> Please join me in welcoming Aaron to the PMC.
>

Re: [VOTE] Release Apache Storm 1.2.3 (rc2)

[Kishorkumar Patil]

Thank you Taylor..

On Sat, Jun 15, 2019 at 12:15 PM P. Taylor Goetz  wrote:

> This vote is now closed and passes with 3 binding +1 votes and 1
> non-binding +1 vote.
>
> I will release the artifacts and create a release announcement.
>
> -Taylor
>
> > On May 10, 2019, at 12:20 PM, P. Taylor Goetz  wrote:
> >
> > This is a call to vote on releasing Apache Storm 1.2.3 (rc2)
> >
> > Full list of changes in this release:
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v1.2.3:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=ac0e39d7cad48b3ec863c8a3b711d36511d4daf6;hb=4e162a47c8219546ab9639401363a8f1b5e51119
> >
> > The source archive being voted upon can be found here:
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/apache-storm-1.2.3-src.tar.gz
> >
> > Other release files, signatures and digests can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/
> >
> > The release artifacts are signed with the following key:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> >
> > The Nexus staging repository for this release is:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1081
> >
> > Please vote on releasing this package as Apache Storm 1.2.3.
> >
> > When voting, please list the actions taken to verify the release.
> >
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 1.2.3
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > -Taylor
>
>

Re: [VOTE] Release Apache Storm 1.2.3 (rc2)

[Kishorkumar Patil]

+1 ( binding)
Jungtaek,
I am validated the release yesterday, Being PMC, my vote is binding.

-Kishor

On Fri, May 17, 2019 at 6:13 AM Jungtaek Lim  wrote:

> We have one binding vote needed to pass the RC. Could any PMC participate
> and finalize the vote?
>
> On Mon, May 13, 2019 at 7:06 PM Roshan Naik  >
> wrote:
>
> >  +1- verified binary distribution- setup local cluster - ran some perf
> > topos with two workers and acking enabled- basic checking of the UI
> > -roshan
> >
> >
> > On Saturday, May 11, 2019, 1:21:26 PM EDT, Alexandre Vermeerbergen <
> > avermeerber...@gmail.com> wrote:
> >
> >  Oh and I forgot to mention that all my tests are made using
> > AdoptOpenJDK11.0.3 with OpenJ9.
> > It all runs very fine with this Java version & VM type.
> > We just had to patch our Hadoop dependencies (for HDFS & HBase Bolts)
> > to fix badly written Java version detection code in these
> > dependencies.
> >
> >
> > Le sam. 11 mai 2019 à 19:18, Alexandre Vermeerbergen
> >  a écrit :
> > >
> > > +1 (non binding)
> > >
> > > - Downloaded binary distribution & used it to update my Storm cloud
> > service
> > > - Downloaded source distribution, compiled it and used the generated
> > > .jar files to update my Storm builder dependencies (storm-core.jar,
> > > storm-kafa-client.jar, flux*.jar)
> > > - Run my clusters with ~15 topologies
> > >
> > > Disclaimer : I have not yet ran test at big scale with this Storm
> > > 1.2.3 update, but I noticed from release notes that I was already
> > > running for several months with a Storm 1.2.3 pre-version updated my
> > > all commits that sounded useful to us (in particular the ones allowing
> > > to use recent Kafka brokers), so basically I'm confident to run 1.2.3
> > > final at scale within very short time after it'll be released.
> > >
> > > Kind regards,
> > > Alexandre Vermeerbergen
> > >
> > > Le ven. 10 mai 2019 à 18:28, P. Taylor Goetz  a
> > écrit :
> > > >
> > > > This is a call to vote on releasing Apache Storm 1.2.3 (rc2)
> > > >
> > > > Full list of changes in this release:
> > > >
> > > >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/RELEASE_NOTES.html
> > > >
> > > > The tag/commit to be voted upon is v1.2.3:
> > > >
> > > >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=ac0e39d7cad48b3ec863c8a3b711d36511d4daf6;hb=4e162a47c8219546ab9639401363a8f1b5e51119
> > > >
> > > > The source archive being voted upon can be found here:
> > > >
> > > >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/apache-storm-1.2.3-src.tar.gz
> > > >
> > > > Other release files, signatures and digests can be found here:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc2/
> > > >
> > > > The release artifacts are signed with the following key:
> > > >
> > > >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> > > >
> > > > The Nexus staging repository for this release is:
> > > >
> > > >
> https://repository.apache.org/content/repositories/orgapachestorm-1081
> > > >
> > > > Please vote on releasing this package as Apache Storm 1.2.3.
> > > >
> > > > When voting, please list the actions taken to verify the release.
> > > >
> > > > This vote will be open for at least 72 hours.
> > > >
> > > > [ ] +1 Release this package as Apache Storm 1.2.3
> > > > [ ]  0 No opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks to everyone who contributed to this release.
> > > >
> > > > -Taylor
>
>
>
> --
> Name : Jungtaek Lim
> Blog : http://medium.com/@heartsavior
> Twitter : http://twitter.com/heartsavior
> LinkedIn : http://www.linkedin.com/in/heartsavior
>

Re: [VOTE] Release Apache Storm 2.0.0 RC7

[Kishorkumar Patil]

Built from the source code. All Unit tests passed.
Ran some basic tests with WordCountTopology, BasicDRPCTopology.
Run ThroughputVsLatency for comparison and it looks good- with 99.9% of
events processed within 5.4ms.
+1


On Tue, Apr 30, 2019 at 2:16 PM Derek Dagit  wrote:

> OK ran the distribution from the tarball, and built and ran from the src
> tarball on macOS with JDK8. Tested WordCountTopology on both and it seemed
> fine.
>
> +1
>
> On Tue, Apr 30, 2019 at 11:55 AM Derek Dagit  wrote:
>
> > Sent too soon:
> >
> > - I verified sigs and sums
> > - Built the source from the tarball on macOS
> >   - I saw a couple of test errors because the local stormconf.ser was
> gone
> > when the supervisor tried to open it, and this resulted in a crash. I
> > re-ran the tests and they passed.
> >   - I do not think this is a blocker, but it is probable worth looking
> > into.
> >
> > I'll continue to evaluate the RC, but wanted to send this out in case
> > anyone else has seen something similar.
> >
> > On Tue, Apr 30, 2019 at 11:52 AM Derek Dagit  wrote:
> >
> >> - I verified sigs and sums
> >>
> >> On Mon, Apr 29, 2019 at 5:49 PM P. Taylor Goetz 
> >> wrote:
> >>
> >>> This is a call to vote on releasing Apache Storm 2.0.0 (rc7)
> >>>
> >>> Full list of changes in this release:
> >>>
> >>>
> >>>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/RELEASE_NOTES.html
> >>>
> >>> The tag/commit to be voted upon is v2.0.0:
> >>>
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=007863edd95e838b3df414928c6fa3f28244ab49;hb=2ba95bbd1c911d4fc6363b1c4b9c4c6d86ac9aae
> >>>
> >>> The source archive being voted upon can be found here:
> >>>
> >>>
> >>>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/apache-storm-2.0.0-src.tar.gz
> >>>
> >>> Other release files, signatures and digests can be found here:
> >>>
> >>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc7/
> >>>
> >>> The release artifacts are signed with the following key:
> >>>
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> >>>
> >>> The Nexus staging repository for this release is:
> >>>
> >>> https://repository.apache.org/content/repositories/orgapachestorm-1079
> >>>
> >>> Please vote on releasing this package as Apache Storm 2.0.0.
> >>>
> >>> When voting, please list the actions taken to verify the release.
> >>>
> >>> This vote will be open for at least 72 hours.
> >>>
> >>> [ ] +1 Release this package as Apache Storm 2.0.0
> >>> [ ]  0 No opinion
> >>> [ ] -1 Do not release this package because...
> >>>
> >>> Thanks to everyone who contributed to this release.
> >>>
> >>> -Taylor
> >>
> >>
>

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

[Kishorkumar Patil]

Aaron,
Thank you for patch and suggesting the work around in the mean time. The PR
for STORM-3317 is merged into master now.
Considering the work around exists for STORM-3317, I am open to either go
ahead with current RC or create a new one.

Thanks,
Kishor

On Tue, Jan 29, 2019 at 11:19 AM Aaron Gresch  wrote:

> The workaround for STORM-3317 is to force your
> java.security.auth.login.config file on the launcher box to remain in the
> same location as where it is hosted on the supervisors.
>
>
> On Mon, Jan 28, 2019 at 10:10 AM Aaron Gresch  wrote:
>
> >
> > Not sure if it affects the release, but STORM-3317 is a new bug in 2.0
> > where if your launcher box has the java.security.auth.login.config  file
> in
> > a different location than the supervisors, uploading credentials will not
> > work.
> >
> > A PR is available that fixes the issue.
> >
> >
> >
> > On Tue, Jan 8, 2019 at 1:03 PM P. Taylor Goetz 
> wrote:
> >
> >> This is a call to vote on releasing Apache Storm 2.0.0 (rc4)
> >>
> >> Full list of changes in this release:
> >>
> >>
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/RELEASE_NOTES.html
> >>
> >> The tag/commit to be voted upon is v2.0.0:
> >>
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=1eece73e8c9ed7f41d2f20f727bc7f644c499360;hb=ddee8decac57d1a4a0aa23cc76066609a2abc8d2
> >>
> >> The source archive being voted upon can be found here:
> >>
> >>
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/apache-storm-2.0.0-src.tar.gz
> >>
> >> Other release files, signatures and digests can be found here:
> >>
> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/
> >>
> >> The release artifacts are signed with the following key:
> >>
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> >>
> >> The Nexus staging repository for this release is:
> >>
> >> https://repository.apache.org/content/repositories/orgapachestorm-1073
> >>
> >> Please vote on releasing this package as Apache Storm 2.0.0.
> >>
> >> When voting, please list the actions taken to verify the release.
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> [ ] +1 Release this package as Apache Storm 2.0.0
> >> [ ]  0 No opinion
> >> [ ] -1 Do not release this package because...
> >>
> >> Thanks to everyone who contributed to this release.
> >>
> >> -Taylor
> >
> >
>

Re: [VOTE] Migration of git repos to gitbox.apache.org

[Kishorkumar Patil]

+1

On Fri, Jan 18, 2019 at 10:47 AM Ethan Li  wrote:

> This is a call to vote on migration of git repos to gitbox.apache.org <
> http://gitbox.apache.org/>.
>
> The following repositories on git-wip-us belong to our project:
> - storm-site.git
> - storm.git
>
> All repositories not migrated on February 7th will be mass migrated
> without warning. It’s better to work with the infrastructure team to avoid
> the mass that day.
>
> The notice email is at
> https://lists.apache.org/thread.html/2bb953946ee6652a054329df2814f512f9186e863ec841555f9cc26a@%3Cdev.storm.apache.org%3E
> <
> https://lists.apache.org/thread.html/2bb953946ee6652a054329df2814f512f9186e863ec841555f9cc26a@%3Cdev.storm.apache.org%3E
> >
>
> This vote will be open for at least 24 hours.
>
> Thanks
>
> - Ethan

-- 
-Kishor

Re: New Storm Committer and PMC Member

[Kishorkumar Patil]

Congratulations Govind!

-Kishor


On Wed, Jan 9, 2019 at 1:00 PM Stig Rohde Døssing 
wrote:

> Congratulations.
>
> Den ons. 9. jan. 2019 kl. 19.55 skrev Roshan Naik
> :
>
> > Congratulations Govind. Roshan
> >
> >
> > Sent from Yahoo Mail for iPhone
> >
> >
> > On Wednesday, January 9, 2019, 10:47 AM, Ethan Li <
> > ethanopensou...@gmail.com> wrote:
> >
> > Congratulations! Govind. Well deserved!
> >
> > Ethan
> >
> > > On Jan 9, 2019, at 12:40 PM, Hugo Louro  wrote:
> > >
> > > Congratulations Govind. Very well deserved. Thank you for all your
> > > contributions and dedication to the Storm project.
> > >
> > > Best,
> > > Hugo
> > >
> > > On Wed, Jan 9, 2019 at 10:36 AM Bobby Evans  wrote:
> > >
> > >> I am happy to announce that Govind Menon has just been added as the
> > latest
> > >> Committer and PMC member to the Apache Storm Project.  Please join me
> in
> > >> congratulating him on this and thanking him for his contributions so
> > far.
> > >>
> > >> Thanks,
> > >>
> > >> Bobby Evans
> > >>
> >
> >
> >
> >
> >
>

Re: [VOTE] Release Apache Storm 1.2.3 (rc1)

[Kishorkumar Patil]

+1.

build from source, unit tests and basic topologies test works.

-Kishor


On Wed, Jan 9, 2019 at 10:29 AM Bobby Evans  wrote:

> +1 built from the tag.  All the unit tests passed and I ran some manual
> tests as well.
>
> Thanks,
>
> Bobby
>
> On Wed, Jan 9, 2019 at 1:16 AM Julien Nioche <
> lists.digitalpeb...@gmail.com>
> wrote:
>
> > Non-binding +1. Launched a Storm cluster in pseudo distributed mode and
> > successfully ran a StormCrawler topology.
> >
> >  Thanks
> >
> > Julien
> >
> > On Tue, 8 Jan 2019 at 20:20, P. Taylor Goetz  wrote:
> >
> > > This is a call to vote on releasing Apache Storm 1.2.3 (rc1)
> > >
> > > Full list of changes in this release:
> > >
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/RELEASE_NOTES.html
> > >
> > > The tag/commit to be voted upon is v1.2.3:
> > >
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=5eaaa51591f2e4dc3e31f22bcc581af4a1f39c03;hb=6ba98b215857656e0186887b5d1a6a5aceee10c4
> > >
> > > The source archive being voted upon can be found here:
> > >
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/apache-storm-1.2.3-src.tar.gz
> > >
> > > Other release files, signatures and digests can be found here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.3-rc1/
> > >
> > > The release artifacts are signed with the following key:
> > >
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> > >
> > > The Nexus staging repository for this release is:
> > >
> > > https://repository.apache.org/content/repositories/orgapachestorm-1074
> > >
> > > Please vote on releasing this package as Apache Storm 1.2.3.
> > >
> > > When voting, please list the actions taken to verify the release.
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache Storm 1.2.3
> > > [ ]  0 No opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks to everyone who contributed to this release.
> > >
> > > -Taylor
> >
> >
> >
> > --
> >
> > *Open Source Solutions for Text Engineering*
> >
> > http://www.digitalpebble.com
> > http://digitalpebble.blogspot.com/
> > #digitalpebble 
> >
>

Re: [VOTE] Release Apache Storm 2.0.0 (rc4)

[Kishorkumar Patil]

+1

 - built from source code and deployment works.
 -  Ran some of the tests for UI, DRPC, ThroughputVsLatency
 -  Validated UI bugs reported in the recent past are fixed in this version

-Kishor


On Tue, Jan 8, 2019 at 2:29 PM Arun Mahadevan  wrote:

> +1
>
> - Downloaded the binaries and validated signatures.
> - Deployed the binaries, ran some sample topologies and checked the UI.
> - Ran top level build using the source zip.
>
> Thanks,
> Arun
>
>
> On Tue, 8 Jan 2019 at 11:03, P. Taylor Goetz  wrote:
>
> > This is a call to vote on releasing Apache Storm 2.0.0 (rc4)
> >
> > Full list of changes in this release:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v2.0.0:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=1eece73e8c9ed7f41d2f20f727bc7f644c499360;hb=ddee8decac57d1a4a0aa23cc76066609a2abc8d2
> >
> > The source archive being voted upon can be found here:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/apache-storm-2.0.0-src.tar.gz
> >
> > Other release files, signatures and digests can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc4/
> >
> > The release artifacts are signed with the following key:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> >
> > The Nexus staging repository for this release is:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1073
> >
> > Please vote on releasing this package as Apache Storm 2.0.0.
> >
> > When voting, please list the actions taken to verify the release.
> >
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 2.0.0
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > -Taylor
>

Re: Storm 2.0.0 release?

[Kishorkumar Patil]

+1


On Sat, Jan 5, 2019 at 5:04 AM Stig Rohde Døssing 
wrote:

> +1
>
> Den lør. 5. jan. 2019 kl. 07.42 skrev Govind Menon <
> govindappume...@gmail.com>:
>
> > +1
> >
> > On Jan 4, 2019 23:46, "Roshan Naik" 
> wrote:
> >
> > +1
> >
> >
> > Sent from Yahoo Mail for iPhone
> >
> >
> >
> > On Friday, January 4, 2019, 9:02 PM, Ethan Li  >
> > wrote:
> >
> > +1 on this
> >
> > Ethan Li
> >
> > > On Jan 4, 2019, at 20:19, P. Taylor Goetz  wrote:
> > >
> > > If no one objects, I’ll kick off a release candidate.
> > >
> > > -Taylor
> > >
> > >> On Jan 4, 2019, at 9:06 PM, saurabh mimani 
> > wrote:
> > >>
> > >> Hey, Any approximate date for 2.0 release given there are no blockers?
> > >>
> > >>
> > >>
> > >> Best Regards
> > >>
> > >> Saurabh Kumar Mimani
> > >>
> > >>
> > >>
> > >>
> > >> On Sat, Dec 22, 2018 at 1:13 AM Stig Rohde Døssing <
> > stigdoess...@gmail.com>
> > >> wrote:
> > >>
> > >>> Looks good to me, the blockers list in JIRA is empty for 2.0.0.
> > >>>
> >  Den fre. 21. dec. 2018 kl. 19.52 skrev Bobby Evans <
> bo...@apache.org
> > >:
> > 
> >  I think all of the blockers are in now.  Please take a look and
> > >>> hopefully,
> >  we can get a release out soon.
> > 
> >  Thanks,
> > 
> >  Bobby
> > 
> > 
> > > On Fri, Dec 14, 2018 at 9:02 AM Bobby Evans 
> > wrote:
> > >
> > > Sorry I was out at a conference for the past week, and have been
> > heads
> >  down
> > > on a different project for a while before that.  I'll respond to
> the
> >  JIRA.
> > > I am happy to let it go in.
> > >
> > > Thanks,
> > >
> > > Bobby
> > >
> > > On Thu, Dec 13, 2018 at 1:07 PM Stig Rohde Døssing <
> >  stigdoess...@gmail.com
> > >>
> > > wrote:
> > >
> > >> I think STORM-2990/3279 is ready. Bobby had a question (
> > >> https://github.com/apache/storm/pull/2907#discussion_r234329136)
> > > regarding
> > >> whether Kafka offsets loop, but I wasn't sure where he was going
> > with
> >  it,
> > >> so I didn't want to merge prematurely.
> > >>
> > >> I agree that we can postpone STORM-2720. As far as I know it's
> > >>> waiting
> > > for
> > >> STORM-2990 to go in, since it's going to be touching the same
> code.
> > >>
> > >> Den tor. 13. dec. 2018 kl. 19.54 skrev Roshan Naik
> > >> :
> > >>
> > >>> Sounds like -  https://github.com/apache/storm/pull/2913
> >  (STORM-3290)
> > >> is
> > >>> merged -  https://github.com/apache/storm/pull/2908 (STORM-3276)
> > >>> is
> > >>> nearly complete and may need some small tweaks. -
> > >>> https://github.com/apache/storm/pull/2907  (STORM-2990,
> > >>> STORM-3279)
> > >>> appears ready to be committed ?
> > >>>
> > >>> and- https://github.com/apache/storm/pull/2911   - (STORM-2720)
> > > seems a
> > >>> bit inactive and may not be critical enough to wait on.
> > >>>
> > >>> -roshan
> > >>>  On Monday, November 26, 2018, 9:49:30 AM PST, Stig Rohde
> > >>> Døssing
> >  <
> > >>> stigdoess...@gmail.com> wrote:
> > >>>
> > >>> I would like to get at least
> > > https://github.com/apache/storm/pull/2913
> > >>> (breaking changes) and https://github.com/apache/storm/pull/2908
> > >>> (regression) in.
> > >>>
> > >>> I think it would be nice to also get
> > >>> https://github.com/apache/storm/pull/2907 and
> > >>> https://github.com/apache/storm/pull/2911 in, but if we're in a
> >  hurry
> > >> they
> > >>> could go in the next release.
> > >>>
> > >>> Den man. 26. nov. 2018 kl. 17.37 skrev Julien Nioche <
> > >>> lists.digitalpeb...@gmail.com>:
> > >>>
> >  Hi devs,
> > 
> >  Is there anything blocking the release of Storm 2.0? Any idea of
> >  when
> > >> it
> >  could happen?
> > 
> >  Thanks
> > 
> >  Julien
> > 
> >  --
> > 
> >  *Open Source Solutions for Text Engineering*
> > 
> >  http://www.digitalpebble.com
> >  http://digitalpebble.blogspot.com/
> >  #digitalpebble 
> > 
> > >>>
> > >>
> > >
> > 
> > >>>
> >
>
-- 
-Kishor

Re: [VOTE] Release Apache Storm 2.0.0 (rc3)

[Kishorkumar Patil]

+1  to release this package.

I ran unit tests, some basic functionality test,  tested manually some of
the UI features and profiling issues reported as part of the blockers. I
did not notice any silent failures either - or any failures/exception in
the logs. Also verified packaging is using zookeeper 3.4.6.

Regards
-Kishor

On Tue, Oct 16, 2018 at 3:48 PM P. Taylor Goetz  wrote:

> This is a call to vote on releasing Apache Storm 2.0.0 (rc3)
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v2.0.0:
>
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=commit;h=d2d6f40344e6cc92ab07f3a462d577ef6b61f8b1
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/apache-storm-2.0.0-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc3/
>
> The release artifacts are signed with the following key:
>
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1072
>
> Please vote on releasing this package as Apache Storm 2.0.0.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> -Taylor
>

Re: [CANCELED] [VOTE] Release Apache Storm 2.0.0 (rc2)

[Kishorkumar Patil]

Agreed. We should deprecate repl and make STORM-3253 part of 2.0 RC.

-Kishor


On Fri, Oct 12, 2018 at 12:14 PM Derek Dagit 
wrote:

> On Fri, Oct 12, 2018 at 9:53 AM Kishorkumar Patil  >
> wrote:
>
> > We need to fix the possible  leaking of slot in
> > https://issues.apache.org/jira/browse/STORM-3254.
> > The patch is upIhttps://github.com/apache/storm/pull/2876
> > -Kishor
> >
> >
> STORM-3253: Deprecates the storm repl subcommand #2875
>
> We may as well do this too if it is no trouble.
>

Re: [CANCELED] [VOTE] Release Apache Storm 2.0.0 (rc2)

[Kishorkumar Patil]

We need to fix the possible  leaking of slot in
https://issues.apache.org/jira/browse/STORM-3254.
The patch is up https://github.com/apache/storm/pull/2876
-Kishor


On Thu, Oct 11, 2018 at 1:47 PM P. Taylor Goetz  wrote:

> Canceling so blockers can be fixed for the 2.0.0 release.
>
> -Taylor
>
> > On Oct 9, 2018, at 4:03 PM, P. Taylor Goetz  wrote:
> >
> > This is a call to vote on releasing Apache Storm 2.0.0 (rc2)
> >
> > Full list of changes in this release:
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v2.0.0:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=f8d04910dc3fd14534c186232ecf7882d8916f67;hb=f8d04910dc3fd14534c186232ecf7882d8916f67
> >
> > The source archive being voted upon can be found here:
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/apache-storm-2.0.0-src.tar.gz
> >
> > Other release files, signatures and digests can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/
> >
> > The release artifacts are signed with the following key:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> >
> > The Nexus staging repository for this release is:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1071
> >
> > Please vote on releasing this package as Apache Storm 2.0.0.
> >
> > When voting, please list the actions taken to verify the release.
> >
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 2.0.0
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > -Taylor
>
>

Re: [VOTE] Release Apache Storm 2.0.0 (rc2)

[Kishorkumar Patil]

Yes, we need fix for security bug -  STORM-3251.

-Kishor


On Thu, Oct 11, 2018 at 12:26 PM Derek Dagit 
wrote:

> I agree with Aaron, we should fix STORM-3251 first.
> -1
>
> On Thu, Oct 11, 2018 at 11:22 AM Aaron Gresch  wrote:
>
> > -1 (non-binding?) https://issues.apache.org/jira/browse/STORM-3251
> >
> > Just found a security-related issue related to a change I recently made
> > (original change causing the bug:
> >
> >
> https://github.com/apache/storm/commit/06a64949c8c5b764a33a10beb6088cdd8f182aa0
> > ).
> >
> >
> > On Wed, Oct 10, 2018 at 6:46 PM Jungtaek Lim  wrote:
> >
> > > Thanks all for the quick turnaround! Here's my +1 (binding).
> > >
> > > > source
> > >
> > > - verify file (signature, MD5, SHA)
> > > -- source, tar.gz : OK
> > > -- source, zip : OK
> > >
> > > - extract file
> > > -- source, tar.gz : OK
> > > -- source, zip : OK
> > >
> > > - diff-ing extracted files between tar.gz and zip : OK
> > >
> > > - build source with JDK 8 (-Pall-tests && -Pexternals)
> > > -- source, tar.gz : OK
> > >
> > > - build source dist
> > > -- source, tar.gz : OK
> > >
> > > - build binary dist
> > > -- source, tar.gz : OK
> > >
> > > > binary
> > >
> > > - verify file (signature, MD5, SHA)
> > > -- binary, tar.gz : OK
> > > -- binary, zip : OK
> > >
> > > - extract file
> > > -- binary, tar.gz : OK
> > > -- binary, zip : OK
> > >
> > > - diff-ing extracted files between tar.gz and zip : OK
> > >
> > > - launch daemons : OK
> > >
> > > - run RollingTopWords (local) : OK
> > >
> > > - run RollingTopWords (remote) : OK
> > >   - activate / deactivate / rebalance / kill : OK
> > >   - logviewer (worker dir, daemon dir) :OK
> > >   - change log level : OK
> > >   - thread dump, heap dump, restart worker : OK
> > >   - log search :OK
> > >
> > > Note that "profiling worker" and "topology log search" works now which
> > were
> > > failing in RC1.
> > >
> > > Thanks,
> > > Jungtaek Lim (HeartSaVioR)
> > >
> > > 2018년 10월 11일 (목) 오전 3:02, Stig Rohde Døssing  >님이
> > > 작성:
> > >
> > > > +1
> > > >
> > > > Built and ran unit tests from the tag.
> > > > Ran ExclamationTopology locally using the Storm tar, verified that UI
> > > looks
> > > > as expected, that logviewer works, and that there were no errors in
> the
> > > > logs.
> > > > Verified the signature and SHA512 for the source and binary tars.
> > > >
> > > > We should consider deleting the md5 files, Apache's release policy
> > > > recommends against including them in a release
> > > > https://www.apache.org/dev/release-distribution#sigs-and-sums.
> > > >
> > > >
> > > > Den ons. 10. okt. 2018 kl. 17.02 skrev Bobby Evans  >:
> > > >
> > > > > +1
> > > > >
> > > > > built and ran all of the unit tests from the tag.
> > > > > Ran some small perf tests on a single node cluster.  Things look
> > really
> > > > > good there.
> > > > >
> > > > >
> > > > > On a side note our CI pipeline has been running and passing builds
> > very
> > > > > close to this release too.  (we are following master currently) and
> > it
> > > is
> > > > > looking good.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Bobby
> > > > >
> > > > > On Tue, Oct 9, 2018 at 4:02 PM Kishorkumar Patil
> > >  > > > >
> > > > > wrote:
> > > > >
> > > > > > +1  to release this package.
> > > > > >
> > > > > > I ran basic tests, and fucntionality tested manually some of the
> UI
> > > > > > features and profiling issues reported as part of the blockers. I
> > did
> > > > not
> > > > > > notice any silent failures either - or any failures/exception in
> > the
> > > > > logs.
> > > > > >
> > > > > > Regards
> > > > > > -Kishor
> > > > > >
> > > > > >
> > > &

Re: [VOTE] Release Apache Storm 2.0.0 (rc2)

[Kishorkumar Patil]

+1  to release this package.

I ran basic tests, and fucntionality tested manually some of the UI
features and profiling issues reported as part of the blockers. I did not
notice any silent failures either - or any failures/exception in the logs.

Regards
-Kishor


On Tue, Oct 9, 2018 at 4:05 PM P. Taylor Goetz  wrote:

> This is a call to vote on releasing Apache Storm 2.0.0 (rc2)
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v2.0.0:
>
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=f8d04910dc3fd14534c186232ecf7882d8916f67;hb=f8d04910dc3fd14534c186232ecf7882d8916f67
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/apache-storm-2.0.0-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc2/
>
> The release artifacts are signed with the following key:
>
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1071
>
> Please vote on releasing this package as Apache Storm 2.0.0.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.0.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> -Taylor
>

Re: Cleaning Up Old Pull Requests STORM-3250

[Kishorkumar Patil]

+1.
It would be nice to clean up old clutter while we are getting ready for
days past 2.x

-Kishor


On Mon, Oct 8, 2018 at 3:52 PM Bobby Evans  wrote:

> +1
>
> Sounds good to me
>
> On Mon, Oct 8, 2018 at 2:50 PM Derek Dagit 
> wrote:
>
> > Currently there are over 150 open pull requests on the Apache Storm
> GitHub
> > project. Over 100 of these have not been modified in 2018.
> >
> > It seems we are unlikely to handle each one of these without significant
> > effort and time. Looking at many of them, they seem to be abandoned by
> the
> > requester.
> >
> > I propose in STORM-3250 that we close all pull requests that have not
> been
> > updated in 2018 and leave any corresponding Jira issues as they are. If
> > there are any pull requests among these should remain open, please let me
> > know. I plan to wait at least a week before requesting any changes.
> >
> >
> >
> >
> https://github.com/apache/storm/pulls?utf8=%E2%9C%93=is%3Apr+is%3Aopen+updated%3A%3C2018-01-01
> >
> > --
> > Derek
> >
>

Re: [VOTE] Release Apache Storm 2.0.0 (rc1)

[Kishorkumar Patil]

I have patch up for  WorkerToken Auto renewal fix. I think this should be
added to 2.x RC.

https://issues.apache.org/jira/browse/STORM-3235
https://github.com/apache/storm/pull/2850

-Kishor

On Tue, Sep 25, 2018 at 8:04 PM P. Taylor Goetz  wrote:

> Jungtaek, can you elaborate on the issues you ran into when testing the rc
> and/or file JIRAs?
>
> -Taylor
>
> > On Sep 25, 2018, at 4:02 PM, Bobby Evans  wrote:
> >
> > Nope.  I plan to start looking into them, unless someone else is already
> > doing so.
> >
> > Thanks,
> >
> > Bobby
> >
> > On Tue, Sep 25, 2018 at 2:48 PM P. Taylor Goetz 
> wrote:
> >
> >> Thanks for the update. I will cancel the vote.
> >>
> >> Do the fixes you merged cover the bugs that Jungtaek pointed out?
> >>
> >> -Taylor
> >>
> >>> On Sep 25, 2018, at 1:56 PM, Bobby Evans  wrote:
> >>>
> >>> Just FYI Taylor I just merged in 3 JIRA to the master branch and will
> >>> probably merge in the fix for the UI that Govind mentioned, but all of
> >> them
> >>> would be okay to go into 2.0.0 as well.  Since this RC looks like it is
> >> not
> >>> going to pass if you want to move the tag up on the master branch, that
> >>> would be fine, once we have the fixes in.
> >>>
> >>> Thanks,
> >>>
> >>> Bobby
> >>>
> >>> On Tue, Sep 25, 2018 at 9:31 AM Govind Menon 
> >>> wrote:
> >>>
>  Hi all,
> 
>  I introduced a bug with the visualization as part of the UI migration
> >> with
>  the following fix - https://github.com/apache/storm/pull/2849. It's
> >> not a
>  show stopper by any means and there's a workaround (specifically
> hiding
>  system stats on the UI). I think we should include this in the RC.
> 
>  Thanks,
>  Govind.
> 
> 
>  On Mon, Sep 24, 2018 at 3:09 PM Alexandre Vermeerbergen <
>  avermeerber...@gmail.com> wrote:
> 
> > Hello All,
> >
> > I will need a little bit time to test this new release with our 15+
> > topologies, but it's definitely worth and exiting !
> > "stay tuned" :)
> >
> > Best regards,
> > Alexandre Vermeerbergen
> >
> > Le ven. 21 sept. 2018 à 20:23, P. Taylor Goetz 
> a
> > écrit :
> >>
> >> This is a call to vote on releasing Apache Storm 2.0.0 (rc1)
> >>
> >> Full list of changes in this release:
> >>
> >>
> >
> 
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/RELEASE_NOTES.html
> >>
> >> The tag/commit to be voted upon is v2.0.0:
> >>
> >>
> >
> 
> >>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88;hb=062bb2f158a66b802a3ad7bdda14fb8f70cf9b88
> >>
> >> The source archive being voted upon can be found here:
> >>
> >>
> >
> 
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/apache-storm-2.0.0-src.tar.gz
> >>
> >> Other release files, signatures and digests can be found here:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.0.0-rc1/
> >>
> >> The release artifacts are signed with the following key:
> >>
> >>
> >
> 
> >>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> >>
> >> The Nexus staging repository for this release is:
> >>
> >>
> >> https://repository.apache.org/content/repositories/orgapachestorm-1070
> >>
> >> Please vote on releasing this package as Apache Storm 2.0.0.
> >>
> >> When voting, please list the actions taken to verify the release.
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> [ ] +1 Release this package as Apache Storm 2.0.0
> >> [ ]  0 No opinion
> >> [ ] -1 Do not release this package because...
> >>
> >> Thanks to everyone who contributed to this release.
> >>
> >> -Taylor
> >
> 
> >>
> >>
>
>

Re: Regarding releasing Apache Storm 2.0.0

[Kishorkumar Patil]

Looking into all issues reported under epic
https://issues.apache.org/jira/browse/STORM-2714 are resolved/closed. I
don't see any open issues/blockers at this point for going ahead with 2.x
release.

I am +1 to 2.0 release.

Regards,
-Kishor

On Mon, Sep 10, 2018 at 2:24 PM, P. Taylor Goetz  wrote:

> I agree, and looking through the JIRAs against 2.0, I would say a majority
> of the ones marked critical are not critical.
>
> I’m +1 on moving forward with a 2.0 release, but will give others time to
> respond with any JIRAs they think should be included.
>
> > p.s. I don't want to create branch-2.x or branch-2.0.x until absolutely
> > necessary, I don't see any major features with pull requests up but if
> you
> > do run across one please send something out before merging it in, so we
> can
> > set up the branches properly at that time.
>
>
> Agree. We can always branch off the release tag/commit.
>
> -Taylor
>
>
> > On Sep 10, 2018, at 12:25 PM, Bobby Evans  wrote:
> >
> > It has been nearly a month since this was originally sent out, and this
> is
> > not the first of these kinds of emails to go out about a 2.0.0 release.
> I
> > think we have made a lot of really good progress on getting ready for a
> 2.0
> > release, and I really would like to see it happen before another month
> > passes.
> >
> > We have a 2.0 based deploy in some of our staging clusters, currently
> > following the master branch with a little that is Yahoo specific on top.
> We
> > would like to start pushing towards production with it soon.
> >
> > There are a few issues that we are aware of.
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20STORM%20AND%
> 20affectedVersion%20in%20(2.0.0)%20AND%20resolution%20%3D%
> 20Unresolved%20ORDER%20BY%20priority%20DESC
> >
> > There are no blockers still open, and only 4 issues listed as critical.
> >
> > If others have any open issues that feel need to be addressed prior to a
> > 2.0.0 release please respond to this with the JIRA number.  I would like
> to
> > set a goal/tentative date of Sep 17th (one week from today) to put
> together
> > a release candidate for a 2.0.0 release, and unless there are major
> > blockers that show up I think we can do it.
> >
> > Thanks,
> >
> > Bobby Evans
> >
> > p.s. I don't want to create branch-2.x or branch-2.0.x until absolutely
> > necessary, I don't see any major features with pull requests up but if
> you
> > do run across one please send something out before merging it in, so we
> can
> > set up the branches properly at that time.
> >
> >
> > On Wed, Jul 18, 2018 at 10:47 PM Jungtaek Lim  wrote:
> >
> >> I'd like to say first, thanks Stig to take up remaining issues. Thanks
> to
> >> his efforts, according to the epic, we have only one major issue left:
> >> porting UI to Java [1], and pull request [2] is available for that.
> >> There're another issues [3] [4] targeting 2.0.0 (since it is backward
> >> incompatible) but they are all about removing deprecated things, so
> easier
> >> to be reviewed and make decisions.
> >>
> >> Once we have a patch for that now, IMHO it would be good to review and
> ship
> >> in 2.0.0 if it wouldn't take a month or so. We could do some sanity
> tests
> >> in parallel, so waiting for UI port would not block much time on
> releasing
> >> Storm 2.0.0.
> >>
> >> - Jungtaek Lim (HeartSaVioR)
> >>
> >> 1. https://issues.apache.org/jira/browse/STORM-1311
> >> 2. https://github.com/apache/storm/pull/2752
> >> 3. https://issues.apache.org/jira/browse/STORM-2947
> >> 4. https://issues.apache.org/jira/browse/STORM-3156
> >>
> >>
> >> 2018년 7월 11일 (수) 오전 5:12, Alexandre Vermeerbergen <
> >> avermeerber...@gmail.com>님이
> >> 작성:
> >>
> >>> +1 would love to try it when an RC is avail!
> >>>
> >>> Alexandre Vermeerbergen
> >>>
> >>> 2018-07-10 21:15 GMT+02:00 Arun Mahadevan :
>  +1 to get it out soon.
> 
> 
> 
> 
>  On 7/10/18, 11:52 AM, "P. Taylor Goetz"  wrote:
> 
> > +1 Sounds good to me.
> >
> > -Taylor
> >
> >> On Jul 10, 2018, at 2:18 AM, Jungtaek Lim 
> wrote:
> >>
> >> Hi devs,
> >>
> >> I hopefully have a time to sort out issues regarding Storm 2.0.0 and
> >>> link
> >> to epic issue.
> >>
> >> https://issues.apache.org/jira/browse/STORM-2714
> >> (require login to Apache JIRA to see issues in epic)
> >>
> >> I guess we are close to the release, mostly left reviewing some
> >> pending
> >> pull requests, and some manual sanity tests.
> >>
> >> Given that master branch is relatively stabilized for Travis CI
> >> build,
> >>> as
> >> well as style check and Java port make codebase better (at least for
> >>> me), I
> >> would really want to make Storm 2.0.0 released sooner than later,
> and
> >>> rely
> >> majorly on 2.x version line.
> >>
> >> So I would propose dev folks to concentrate on remaining tasks for
> >>> Storm
> >> 2.0.0 till we announce release. WDYT?
> >>
> >> 

Re: Running tests via Clojure REPL

[Kishorkumar Patil]

Please run
On master branch, please run `mvn install -DskipTests;` before running *
./dev-tools/test-ns.py org.apache.storm.drpc-test*.

main:
[INFO] Executed tasks
[INFO]
[INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ storm-core ---
[INFO]
[INFO] --- clojure-maven-plugin:1.7.1:test (test-clojure) @ storm-core ---
Running org.apache.storm.drpc-test
Tests run: 7, Passed: 14, Failures: 0, Errors: 0




Kishor

On Thu, Jun 7, 2018 at 1:11 PM, Vivian Kong  wrote:

> Thanks Kishor! I tried the script but it didn't seem to be working. It
> didn't find any tests to run:
>
> ...
> main:
> [INFO] Executed tasks
> [INFO]
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ storm-core
> ---
> [INFO]
> [INFO] --- clojure-maven-plugin:1.7.1:test (test-clojure) @ storm-core ---
> Picked up _JAVA_OPTIONS: -Xmx4096m
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> ...
>
> Regards,
>
> Vivian Kong
> Linux on z Systems Open Source Ecosystem
> IBM Canada Toronto Lab
>
> [image: Inactive hide details for Kishorkumar Patil ---2018/06/07 11:28:00
> AM---Try *./dev-tools/test-ns.py org.apache.storm.drcp_test*]Kishorkumar
> Patil ---2018/06/07 11:28:00 AM---Try *./dev-tools/test-ns.py
> org.apache.storm.drcp_test*
>
> From: Kishorkumar Patil 
> To: dev@storm.apache.org
> Date: 2018/06/07 11:28 AM
> Subject: Re: Running tests via Clojure REPL
> --
>
>
>
> Try
>
> *./dev-tools/test-ns.py org.apache.storm.drcp_test*
>
>
>
> Kishor
>
> On Thu, Jun 7, 2018 at 11:00 AM, Vivian Kong  wrote:
>
> >
> >
> > Hi,
> >
> > I am following
> >
> https://github.com/apache/storm/blob/master/DEVELOPER.md#testing-1 to try
>
> > to run a subset of storm-core tests via the Clojure REPL but I couldn't
> > figured out how to do that.  Tried the following but hit an exception
> (see
> > below).  I appreciate any pointers/examples on how to set up and run the
> > tests.  Thanks!
> >
> >
> > # clojure storm-core/test/clj/org/apache/storm/drpc_test.clj
> > Picked up _JAVA_OPTIONS: -Xmx4096m
> > Exception in thread "main" java.lang.ClassNotFoundException:
> > org.apache.storm.drpc.ReturnResults,
> > compiling:(/root/storm/storm-core/test/clj/org/apache/
> > storm/drpc_test.clj:1:1)
> > at clojure.lang.Compiler.load(Compiler.java:7526)
> > at clojure.lang.Compiler.loadFile(Compiler.java:7452)
> > at clojure.main$load_script.invokeStatic(main.clj:278)
> > at clojure.main$script_opt.invokeStatic(main.clj:338)
> > at clojure.main$script_opt.invoke(main.clj:333)
> > at clojure.main$main.invokeStatic(main.clj:424)
> > at clojure.main$main.doInvoke(main.clj:387)
> > at clojure.lang.RestFn.applyTo(RestFn.java:137)
> > at clojure.lang.Var.applyTo(Var.java:702)
> > at clojure.main.main(main.java:37)
> > Caused by: java.lang.ClassNotFoundException:
> > org.apache.storm.drpc.ReturnResults
> > at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> > at clojure.lang.DynamicClassLoader.findClass
> > (DynamicClassLoader.java:69)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> > at clojure.lang.DynamicClassLoader.loadClass
> > (DynamicClassLoader.java:77)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> > at java.lang.Class.forName0(Native Method)
> > at java.lang.Class.forName(Class.java:348)
> > at clojure.lang.RT.classForName(RT.java:2204)
> > at clojure.lang.RT.classForNameNonLoading(RT.java:2217)
> > at org.apache.storm.drpc_test$eval147
> > $loading__6434__auto148.invoke(drpc_test.clj:16)
> > at org.apache.storm.drpc_test$eval147.invokeStatic
> > (drpc_test.clj:16)
> > at org.apache.storm.drpc_test$eval147.invoke(drpc_test.clj:16)
> > at clojure.lang.Compiler.eval(Compiler.java:7062)
> > at clojure.lang.Compiler.eval(Compiler.java:7051)
> > at clojure.lang.Compiler.load(Compiler.java:7514)
> > ... 9 more
> >
> >
> >
> > Regards,
> >
> > Vivian Kong
> > Linux on z Systems Open Source Ecosystem
> > IBM Canada Toronto Lab
> >
>
>
>
>

Re: Running tests via Clojure REPL

[Kishorkumar Patil]

Try

*./dev-tools/test-ns.py org.apache.storm.drcp_test*


Kishor

On Thu, Jun 7, 2018 at 11:00 AM, Vivian Kong  wrote:

>
>
> Hi,
>
> I am following
> https://github.com/apache/storm/blob/master/DEVELOPER.md#testing-1 to try
> to run a subset of storm-core tests via the Clojure REPL but I couldn't
> figured out how to do that.  Tried the following but hit an exception (see
> below).  I appreciate any pointers/examples on how to set up and run the
> tests.  Thanks!
>
>
> # clojure storm-core/test/clj/org/apache/storm/drpc_test.clj
> Picked up _JAVA_OPTIONS: -Xmx4096m
> Exception in thread "main" java.lang.ClassNotFoundException:
> org.apache.storm.drpc.ReturnResults,
> compiling:(/root/storm/storm-core/test/clj/org/apache/
> storm/drpc_test.clj:1:1)
> at clojure.lang.Compiler.load(Compiler.java:7526)
> at clojure.lang.Compiler.loadFile(Compiler.java:7452)
> at clojure.main$load_script.invokeStatic(main.clj:278)
> at clojure.main$script_opt.invokeStatic(main.clj:338)
> at clojure.main$script_opt.invoke(main.clj:333)
> at clojure.main$main.invokeStatic(main.clj:424)
> at clojure.main$main.doInvoke(main.clj:387)
> at clojure.lang.RestFn.applyTo(RestFn.java:137)
> at clojure.lang.Var.applyTo(Var.java:702)
> at clojure.main.main(main.java:37)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.storm.drpc.ReturnResults
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at clojure.lang.DynamicClassLoader.findClass
> (DynamicClassLoader.java:69)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at clojure.lang.DynamicClassLoader.loadClass
> (DynamicClassLoader.java:77)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2204)
> at clojure.lang.RT.classForNameNonLoading(RT.java:2217)
> at org.apache.storm.drpc_test$eval147
> $loading__6434__auto148.invoke(drpc_test.clj:16)
> at org.apache.storm.drpc_test$eval147.invokeStatic
> (drpc_test.clj:16)
> at org.apache.storm.drpc_test$eval147.invoke(drpc_test.clj:16)
> at clojure.lang.Compiler.eval(Compiler.java:7062)
> at clojure.lang.Compiler.eval(Compiler.java:7051)
> at clojure.lang.Compiler.load(Compiler.java:7514)
> ... 9 more
>
>
>
> Regards,
>
> Vivian Kong
> Linux on z Systems Open Source Ecosystem
> IBM Canada Toronto Lab
>

Re: [VOTE] Release Apache Storm 1.1.3 (rc2)

[Kishorkumar Patil]

+1


Kishor

On Wed, May 23, 2018 at 4:54 PM, Jungtaek Lim  wrote:

> REMINDER: The vote has been opened from 5 days ago, and still has only one
> binding +1s. Please verify the release candidate and vote.
>
> 2018년 5월 19일 (토) 오전 10:49, Jungtaek Lim 님이 작성:
>
> > This release candidate contains md5/sha for src archives, unlike 1.2.2
> > RCs. May worth to check that.
> >
> > +1 (binding)
> >
> > On top to my verification on 1.2.3 rc1 (was +1),
> >
> > - verification on source/binary dist succeeded
> > - build succeeded on source
> > - spinning single cluster from binary dist succeeded
> > - ran RollingTopWords
> >
> > The difference between rc1 and rc2 is regarding storm-kafka-client patch,
> > so skipped checking storm-core features.
> >
> > Thanks,
> > Jungtaek Lim (HeartSaVioR)
> >
> > 2018년 5월 19일 (토) 오전 4:39, P. Taylor Goetz 님이 작성:
> >
> >> This is a call to vote on releasing Apache Storm 1.1.3 (rc2)
> >>
> >> Full list of changes in this release:
> >>
> >>
> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> 1.3-rc2/RELEASE_NOTES.html
> >>
> >> The tag/commit to be voted upon is v1.1.3:
> >>
> >>
> >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
> e983fef3d4dcd35a821cecb462e198505458d1a4;hb=c51c8fc251856291597a5007a07e43
> 3f26951464
> >>
> >> The source archive being voted upon can be found here:
> >>
> >>
> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> 1.3-rc2/apache-storm-1.1.3-src.tar.gz
> >>
> >> Other release files, signatures and digests can be found here:
> >>
> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.3-rc2/
> >>
> >> The release artifacts are signed with the following key:
> >>
> >>
> >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_
> plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> >>
> >> The Nexus staging repository for this release is:
> >>
> >> https://repository.apache.org/content/repositories/orgapachestorm-1069
> >>
> >> Please vote on releasing this package as Apache Storm 1.1.3.
> >>
> >> When voting, please list the actions taken to verify the release.
> >>
> >> This vote will be open for 72 hours or until at least 3 PMC members vote
> >> +1.
> >>
> >> [ ] +1 Release this package as Apache Storm 1.1.3
> >> [ ]  0 No opinion
> >> [ ] -1 Do not release this package because...
> >>
> >> Thanks to everyone who contributed to this release.
> >>
> >> -Taylor
> >>
> >
>

Re: [VOTE] Release Apache Storm 1.2.2 (rc3)

[Kishorkumar Patil]

+1.
LGTM.

Kishor

On Wed, May 23, 2018 at 4:54 PM, Jungtaek Lim  wrote:

> REMINDER: The vote has been opened from 6 days ago, and still has only two
> binding +1s. Please verify the release candidate and vote.
>
> 2018년 5월 21일 (월) 오후 11:16, Julien Nioche 님이
> 작성:
>
> > +1 non binding
> >
> > compiled + ran StormCrawler topology without problems
> >
> > Thanks
> >
> > Julien
> >
> >
> >
> > On 17 May 2018 at 20:59, P. Taylor Goetz  wrote:
> >
> > > This is a call to vote on releasing Apache Storm 1.2.2 (rc3)
> > >
> > > Full list of changes in this release:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> > > 2.2-rc3/RELEASE_NOTES.html
> > >
> > > The tag/commit to be voted upon is v1.2.2:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
> > >
> > d29eaa70280dd0ac4b7d393387fab4a91eee9e9d;hb=
> d2d6f40344e6cc92ab07f3a462d577
> > > ef6b61f8b1
> > >
> > > The source archive being voted upon can be found here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> > > 2.2-rc3/apache-storm-1.2.2-src.tar.gz
> > >
> > > Other release files, signatures and digests can be found here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.2-rc3/
> > >
> > > The release artifacts are signed with the following key:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_
> > > plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> > >
> > > The Nexus staging repository for this release is:
> > >
> > > https://repository.apache.org/content/repositories/orgapachestorm-1068
> > >
> > > Please vote on releasing this package as Apache Storm 1.2.2.
> > >
> > > When voting, please list the actions taken to verify the release.
> > >
> > > This vote will be open for 72 hours or until at least 3 PMC members
> vote
> > > +1.
> > >
> > > [ ] +1 Release this package as Apache Storm 1.2.2
> > > [ ]  0 No opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks to everyone who contributed to this release.
> > >
> > > -Taylor
> > >
> >
> >
> >
> > --
> >
> > *Open Source Solutions for Text Engineering*
> >
> > http://www.digitalpebble.com
> > http://digitalpebble.blogspot.com/
> > #digitalpebble 
> >
>

Re: [VOTE] Release Apache Storm 1.1.1 (rc1)

[Kishorkumar Patil]

I built and ran some manual tests. 
+1 to release this package. 

-Kishor


On Tuesday, July 25, 2017, 12:08:32 PM EDT, Stig Rohde Døssing 
 wrote:

Is it on purpose that this is cut from 1.x-branch and not 1.1.x-branch?

2017-07-25 17:09 GMT+02:00 P. Taylor Goetz :

> This is a call to vote on releasing Apache Storm 1.1.1 (rc1)
>
> Full list of changes in this release:
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_
> plain;f=CHANGELOG.md;hb=88f0b8a45553ea960164fab18c736a5cdbae8e58
>
> The tag/commit to be voted upon is v1.1.1:
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
> 89bf57855806d84dba8d9b7fe6e76f9074a6aa19;hb=88f0b8a45553ea960164fab18c736a
> 5cdbae8e58
>
> The source archive being voted upon can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> 1.1-rc1/apache-storm-1.1.1-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.1-rc1/
>
> The release artifacts are signed with the following key:
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_
> plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1049
>
> Please vote on releasing this package as Apache Storm 1.1.1.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 1.1.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> -Taylor

Re: [VOTE] Release Apache Storm 1.0.4 (rc1)

[Kishorkumar Patil]

I built and I ran manual tests. It looks good to me. 
I am +1 on the release.
-Kishor


On Tuesday, July 25, 2017, 11:19:46 AM EDT, Bobby Evans 
 wrote:

I built from source (v1.0.4 a5e1c154b5b2ae74fd78bf10d4c130afb1ad4513), ran all 
of the unit tests, and ran a few manual tests on my laptop.
I am +1 on the release.


- Bobby


On Tuesday, July 25, 2017, 6:27:18 AM CDT, Stig Rohde Døssing 
 wrote:

The linked changelog (https://git-wip-us.apache.org/repos/asf?p=storm.git;a=
blob_plain;f=CHANGELOG.md;h=50878fab679973a1230466920006dc0746ffddd5;hb=
eac433b0beb3798c4723deb39b3c4fad446378f4) seems to contain only changes up
to 1.0.3. It's just a problem with the link, the changelog in the src tar
is correct.

Unpacked the binary tar to a new directory.
Started Nimbus, a supervisor and the UI daemon via the storm.cmd script.
The cluster was using the default configuration.
Unpacked the src tar, and built ExclamationTopology and the
storm-kafka-client KafkaSpoutTopologyMainNamedTopics against the Nexus
staging repository.
Submitted storm-starter ExclamationTopology
* Changed log level and verified that the log level changed
* Tried to use Logviewer, but this fails on Windows due to
"java.util.regex.PatternSyntaxException:
Unexpected internal error near index 1
 \
 ...
 at org.apache.storm.daemon.logviewer$get_topo_port_
workerlog.invoke(logviewer.clj:123)". This bug isn't new, so it's not a
blocker IMO. I think it's probably fixed on master with
https://github.com/apache/storm/pull/2204
* Deactivated/activated and killed the topology, this worked as expected
Submitted storm-kafka-client KafkaSpoutTopologyMainNamedTopics using the
directions at https://github.com/apache/storm/tree/v1.0.4/external/
storm-kafka-client#build-and-run-bundled-examples, running against a local
Kafka instance.

The topologies seemed to run fine once I got past a few Windows specific
bugs:
* https://issues.apache.org/jira/browse/STORM-2451 which has a workaround
listed on the issue. I don't know if it makes sense to pull the bugfix back
into 1.0.x?
* There's an error log when log files are rolled, seemingly due to Windows'
file locking behavior. Seems like more of an annoyance than a real issue,
since the files appear to roll correctly. The log is "STDERR Thread-2
[INFO] 2017-07-25 13:00:45,639 Thread-5-exclaim2-executor[7 7] ERROR Unable
to delete file E:\apache-storm-1.0.4\logs\workers-artifacts\production-
topology-1-1500978841\6700\worker.log: java.nio.file.FileSystemException
E:\apache-storm-1.0.4\logs\workers-artifacts\production-
topology-1-1500978841\6700\worker.log: The process cannot access the file
because it is being used by another process."

Other minor issues:
* Noticed in the src tar that the integration-test pom is pointing to
1.0.3-SNAPSHOT instead of 1.0.4. This is also an issue on the 1.0.x-branch
branch on github.
* Non-HA Nimbus won't start when previously deployed topologies are not in
storm-local, giving the message "o.a.s.zookeeper main-EventThread [INFO]
code for all active topologies not available locally, giving up
leadership.". This is annoying when trying to do a rolling upgrade, since
it is easy to screw up by installing the new Storm version in a new
directory rather than overwriting the old installation. I think we should
add storm.local.dir to the comments in conf/storm.yaml and encourage people
to set it to a directory outside the storm dir.
* It looks like the blob store may be using the wrong base path when
storm.local.dir is relative. I get the directory
STORM_HOME/bin/storm-local/blobs
in addition to the expected STORM_HOME/storm-local. I'm guessing the path
is based on which working directory "storm nimbus/supervisor" is being run
from.

I think since most of these issues have workarounds and were likely present
in 1.0.3, they shouldn't block the release.

It might make sense to fix the integration-test pom and maybe pull
STORM-2451 back too. Since those issues are so minor I don't want to block
the release for that alone though. +1

2017-07-24 20:24 GMT+02:00 P. Taylor Goetz :

> This is a call to vote on releasing Apache Storm 1.0.4 (rc1)
>
> Full list of changes in this release:
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_
> plain;f=CHANGELOG.md;h=50878fab679973a1230466920006dc0746ffddd5;hb=
> eac433b0beb3798c4723deb39b3c4fad446378f4
>
> The tag/commit to be voted upon is v1.0.4:
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_
> plain;f=CHANGELOG.md;hb=a5e1c154b5b2ae74fd78bf10d4c130afb1ad4513
>
> The source archive being voted upon can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> 0.4-rc1/apache-storm-1.0.4-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.4-rc1/
>
> The release artifacts are signed with the following key:
>
> 

Re: [VOTE] Java Code Style Standard for Apache Storm.

[Kishorkumar Patil]

[1] Google Java Style Guide

[2] Sun Java Code 
Conventions

[3] HBase 
style
 (sorry all I could find was an eclipse XML config)

[4] Hadoop style which is 
described as java but with 2 spaces instead of 4. 

-Kishor


On Thursday, April 27, 2017 10:01 PM, Satish Duggana  
wrote:
 

 [1] Google Java Style Guide

[2] Hadoop style which
is described as java but with 2 spaces instead of 4.

[3] Sun Java Code Conventions

[4] HBase style (sorry all I could find was an eclipse
XML config)

Thanks,
~Satish.

On Thu, Apr 27, 2017 at 7:50 PM, Kyle Nusbaum <
knusb...@yahoo-inc.com.invalid> wrote:

> [1] Google Java Style Guide io/styleguide/javaguide.html>
>
> [2] Sun Java Code Conventions codeconventions-150003.pdf>
>
> [3] HBase style support/hbase_eclipse_formatter.xml> (sorry all I could find was an
> eclipse XML config)
>
> [4] Hadoop style
> which is described as java but with 2 spaces instead of 4.
> Thanks,
> -- Kyle
>
> On Thursday, April 27, 2017, 3:51:25 AM CDT, Julien Nioche <
> lists.digitalpeb...@gmail.com> wrote:Non-binding : [1 ] Google Java Style
> Guide
>
> On 26 April 2017 at 19:50, Bobby Evans 
> wrote:
>
> > We would like to adopt a code style standard for Apache Storm.  Please
> > rank the following with 1 being the most desired and 4 being the least
> > desired (5 if you have a write in choice).  This is not an official vote
> as
> > per the ByLaws, but we will probably go with whichever wins the most 1
> > votes (unless it is really close and then we may go with some STeVe like
> > ranking, but I want to avoid it because it is hard and I might get the
> math
> > wrong) This is open to everyone so please vote.
> >
> >
> > [ ] Google Java Style Guide > io/styleguide/javaguide.html>
> >
> > [ ] Sun Java Code Conventions > codeconventions-150003.pdf>
> >
> > [ ] HBase style > support/hbase_eclipse_formatter.xml> (sorry all I could find was an
> > eclipse XML config)
> >
> > [ ] Hadoop style
> > which is described as java but with 2 spaces instead of 4.
> >
> > [ ] Other (Please specify)
> >
> >
> > I apologize if the formatting is bad I am forced to use a corporate
> > sponsored mail client that somehow messed up plain text formatting.  I
> > don't know how.
> >
> >
> > - Bobby
>
>
>
>
> --
>
> *Open Source Solutions for Text Engineering*
>
> http://www.digitalpebble.com
> http://digitalpebble.blogspot.com/
> #digitalpebble 
>


   

Re: [VOTE] Release Apache Storm 1.0.3 (RC2)

[Kishorkumar Patil]

Thanks Taylor, I was little late I guess. :)

-Kishor
 

On Monday, February 13, 2017 3:52 PM, P. Taylor Goetz <ptgo...@gmail.com> 
wrote:
 

 They’ve been moved over to release now that the vote has passed:

https://dist.apache.org/repos/dist/release/storm/apache-storm-1.0.3/ 
<https://dist.apache.org/repos/dist/release/storm/apache-storm-1.0.3/>

-Taylor

> On Feb 13, 2017, at 3:41 PM, Kishorkumar Patil <kpa...@yahoo-inc.com.INVALID> 
> wrote:
> 
> The files are missing from dist. I am getting 404.
> -Kishor
> 
> 
>    On Monday, February 13, 2017 2:36 PM, P. Taylor Goetz <ptgo...@gmail.com> 
>wrote:
> 
> 
> +1
> 
> Performed my typical checks and verified topology visualization fix and local 
> shutdown issue.
> 
> -Taylor
> 
>> On Feb 7, 2017, at 3:51 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>> This is a call to vote on releasing Apache Storm 1.0.3 (rc2)
>> 
>> Full list of changes in this release:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;h=50878fab679973a1230466920006dc0746ffddd5;hb=eac433b0beb3798c4723deb39b3c4fad446378f4
>> 
>> The tag/commit to be voted upon is v1.0.3:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=9c337dade6ed9cffc2d893768ea8866824596b0f;hb=eac433b0beb3798c4723deb39b3c4fad446378f4
>> 
>> The source archive being voted upon can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.3-rc2/apache-storm-1.0.3-src.tar.gz
>> 
>> Other release files, signatures and digests can be found here:
>> 
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.3-rc2/
>> 
>> The release artifacts are signed with the following key:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>> 
>> The Nexus staging repository for this release is:
>> 
>> https://repository.apache.org/content/repositories/orgapachestorm-1044
>> 
>> Please vote on releasing this package as Apache Storm 1.0.3.
>> 
>> When voting, please list the actions taken to verify the release.
>> 
>> This vote will be open for at least 72 hours.
>> 
>> [ ] +1 Release this package as Apache Storm 1.0.3
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>> 
>> Thanks to everyone who contributed to this release.
>> 
>> -Taylor
> 
> 


   

Re: [VOTE] Release Apache Storm 1.0.3 (RC2)

[Kishorkumar Patil]

The files are missing from dist. I am getting 404.
-Kishor
 

On Monday, February 13, 2017 2:36 PM, P. Taylor Goetz  
wrote:
 

 +1

Performed my typical checks and verified topology visualization fix and local 
shutdown issue.

-Taylor

> On Feb 7, 2017, at 3:51 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.0.3 (rc2)
> 
> Full list of changes in this release:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;h=50878fab679973a1230466920006dc0746ffddd5;hb=eac433b0beb3798c4723deb39b3c4fad446378f4
> 
> The tag/commit to be voted upon is v1.0.3:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=9c337dade6ed9cffc2d893768ea8866824596b0f;hb=eac433b0beb3798c4723deb39b3c4fad446378f4
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.3-rc2/apache-storm-1.0.3-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.3-rc2/
> 
> The release artifacts are signed with the following key:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1044
> 
> Please vote on releasing this package as Apache Storm 1.0.3.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.0.3
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor


   

Re: [VOTE] Release Apache Storm 1.0.3 (rc1)

[Kishorkumar Patil]

+1 I ran some sample tests. LGTM.
-Kishor
 

On Saturday, February 4, 2017 12:15 PM, Alexandre Vermeerbergen 
 wrote:
 

 Hello again,

I confirm +1 (non binding), with the following setup (modifed yesterday to
use Kafka Brokers 0.10.1 instead of Kafka Brokers 0.9.2 after good behavior
observed with my previously reported setup):

Using storm 1.0.3rc1 binaries artifacts, I installed our supervision system
(currently made of 11 topologies), with java 8 update 92 on CentOS 6.5 ;
with a cluster type of install (2 big VMs with Supervisors, another VM with
Nimbus, and other VMs for Zookeeper nodes) and connected KafkaSpouts &
KafkaBolts to a Kafka 0.10.1 cluster.

Please note that I have built our topologies with Kafka 0.9.2 libs ; and I
am not yet using the new Storm Kafka client.

Best regards,
Alexandre

2017-02-02 21:54 GMT+01:00 Alexandre Vermeerbergen :

> Hello all,
>
> Using storm 1.0.3rc1 binaries artifacts, I installed our supervision
> system (currently made of 11 topologies), with java 8 update 92 on CentOS
> 6.5 ; with a cluster type of install (2 big VMs with Supervisors, another
> VM with Nimbus, and other VMs for Zookeeper nodes).
>
> So far so good => +1 (non binding)
>
> It's been running for only 1 hour, I may update if I see issues in the
> coming days. I'll pay attention to stability & performance (too early to
> tell).
>
> Thanks,
>
> Alexandre Vermeerbergen
>
>
>
> 2017-01-31 21:55 GMT+01:00 P. Taylor Goetz :
>
>> This is a call to vote on releasing Apache Storm 1.0.3 (rc1)
>>
>> Full list of changes in this release:
>>
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h
>> =6cb735d18ec11eccd3e80bab8f879c989a9b3967;hb=a81ec2580fce1f2
>> ee6349a9028dcb75763798bec
>>
>> The tag/commit to be voted upon is v1.0.3:
>>
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_p
>> lain;f=CHANGELOG.md;h=b8adddc6aa20107288e59cba6a2976c0951742
>> fb;hb=a81ec2580fce1f2ee6349a9028dcb75763798bec
>>
>> The source archive being voted upon can be found here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>> 0.3-rc1/apache-storm-1.0.3-src.tar.gz
>>
>> Other release files, signatures and digests can be found here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.0.3-rc1/
>>
>> The release artifacts are signed with the following key:
>>
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_p
>> lain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>
>> The Nexus staging repository for this release is:
>>
>> https://repository.apache.org/content/repositories/orgapachestorm-1043
>>
>> Please vote on releasing this package as Apache Storm 1.0.3.
>>
>> When voting, please list the actions taken to verify the release.
>>
>> This vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache Storm 1.0.3
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>>
>> Thanks to everyone who contributed to this release.
>>
>> -Taylor
>
>
>


   

Re: Is this the list of metrics reported by storm in JMX?

[Kishorkumar Patil]

Alessandro,
One caution is "num-getClusterInfo-calls" is not strictly number of thrift 
calls but # of times method was invoked. We do not have separate thrift entry 
method from rest of the internal calls to getClusterInfo 

Regards,
-Kishor
 

On Friday, October 14, 2016 8:31 AM, Alessandro Bellina 
 wrote:
 

 T.I.

I ran jconsole and ended up with the same result for a worker.

That said, if you turn on JMX for the daemons you end up with a new MBean 
"metrics" (as given by storm.daemon.metrics.reporter.plugin.domain).  This is 
coming from: JmxPreparableReporter.


- For nimbus I see stuff like: num-getClusterInfo-calls for thrift calls. 
- For ui, I see metrics around the REST calls.
- For supervisor, currently I only see "num-slots-used-gauge".

Someone else please correct me if I've missed something.

Thanks

Alessandro





On Friday, October 14, 2016 12:58 AM, Tech Id  wrote:
Hi,

I know there are plans to revamp the current metrics system.
But until then, I just wanted to confirm the metrics I have got through JMX
and if that is expected.

I added the following to *worker.options*:

-Dcom.sun.management.jmxremote \
-Dcom.sun.management.jmxremote.port=1%ID% \
-Dcom.sun.management.jmxremote.authenticate=false \
-Dcom.sun.management.jmxremote.ssl=false

And I used  cmdline-jmxclient
's jar file as:
java -jar /tmp/cmdline-jmxclient-0.10.3.jar -:- 127.0.0.1:16700 | grep -v log4j
| sort -u


The metrics I got were:
com.sun.management:type=DiagnosticCommand
com.sun.management:type=HotSpotDiagnostic
java.lang:name=CodeCacheManager,type=MemoryManager
java.lang:name=Code Cache,type=MemoryPool
java.lang:name=Compressed Class Space,type=MemoryPool
java.lang:name=Metaspace Manager,type=MemoryManager
java.lang:name=Metaspace,type=MemoryPool
java.lang:name=PS Eden Space,type=MemoryPool
java.lang:name=PS MarkSweep,type=GarbageCollector
java.lang:name=PS Old Gen,type=MemoryPool
java.lang:name=PS Scavenge,type=GarbageCollector
java.lang:name=PS Survivor Space,type=MemoryPool
java.lang:type=ClassLoading
java.lang:type=Compilation
java.lang:type=Memory
java.lang:type=OperatingSystem
java.lang:type=Runtime
java.lang:type=Threading
java.nio:name=direct,type=BufferPool
java.nio:name=mapped,type=BufferPool
java.util.logging:type=Logging
JMImplementation:type=MBeanServerDelegate

None of these seems to be storm-specific and that is kind of expected
because storm does not report those metrics to JMX.
Can someone confirm if those really are the metrics I should expect or are
there more I can get from JMX?

Thanks
T.I.


   

Re: Auto-generating documentation site..

[Kishorkumar Patil]

Thanks HeartSaVioR, Taylor,

I would  have preferred code and documentation be on the same branch - 
specially considering documentation and generated JavaDocs.  Secondly, it would 
be ideal to have same branch generate docs by release version and one pointing 
to the current version tagged by version.
I don't fully understand the reasons for separating docs from code. Is there as 
reason we want to make it separate?
-Kishor
 


 On Thursday, November 5, 2015 10:32 AM, P. Taylor Goetz 
<ptgo...@gmail.com> wrote:
   

 That’s my fault. I forgot to delete the docs directory after converting over 
to the asf-site branch.

I will take care of this.

-Taylor

> On Nov 5, 2015, at 10:46 AM, Bobby Evans <ev...@yahoo-inc.com.INVALID> wrote:
> 
> I followed my own comment to generate the site in the docs directory, and I 
> tried to copy it over to subversion, but didn't check it in because things 
> had changed. I didn't use the branch asf-site, I didn't know it was there 
> because we still have the docs directory with instructions on how to use it.  
> Having a separate branch in git for the site and still having the docs 
> directory is very confusing.  We have had a few pull requests update docs 
> recently which is why I was updating the site.  Are we planning on keeping 
> separate releases for the site from the code?  I am fine with that but we 
> should remove the docs directory from all development branches then, and have 
> someone look at the recent changes and pull them in to asf-site.
> 
> - Bobby
> 
> 
> 
> On Thursday, November 5, 2015 8:54 AM, 임정택 <kabh...@gmail.com> wrote:
> Kishor and Bobby,
> Did you use the branch 'asf-site'?
> I checked but nothing is changed in 'asf-site' branch.
> 
> Kishor,
> Maybe Bobby's explanation for me could help you too, since seems like git
> based publishing is not enabled yet.
> https://github.com/apache/storm/pull/771#issuecomment-144726893
> 
> Best,
> Jungtaek Lim (HeartSaVioR)
> 
> 
> 
> 
> 2015-11-05 3:20 GMT+09:00 Bobby Evans <ev...@yahoo-inc.com.invalid>:
> 
>> I just tried to update it and the source under docs using the version of
>> jekyll I have installed (2.5.2) is generating something that looks totally
>> different from what we have on http://storm.apache.org/  Are there new
>> instructions or a new version required for this?  - Bobby
>> 
>> 
>>    On Wednesday, November 4, 2015 11:35 AM, Kishorkumar Patil
>> <kpa...@yahoo-inc.com.INVALID> wrote:
>> 
>> 
>> Hello Taylor,
>> I have pushed some more updates to the documentation in the git. But I am
>> not sure how to update Storm Documentation site.
>> 
>> Can you point me to steps on how to update this. Also,  I am wondering if
>> we have any planned/in progress(JIRA) automation to generate and publish
>> this documentation?
>> 
>> Regards,Kishor
>> 
>> 
>> 
> 
> 
> 
> --
> Name : 임 정택
> Blog : http://www.heartsavior.net / http://dev.heartsavior.net
> Twitter : http://twitter.com/heartsavior
> LinkedIn : http://www.linkedin.com/in/heartsavior


  

Re: Welcome JStorm Community!

[Kishorkumar Patil]

Welcome! Looking forward to working with integrated Storm team!
Special Kudos to Taylor and others who are helping accomplish this.

Regards,Kishor 


 On Wednesday, November 4, 2015 11:35 AM, Priyank Shah 
 wrote:
   

 Welcome everyone from JStorm community. Look forward to working with you all.




On 11/4/15, 8:49 AM, "Hugo Da Cruz Louro"  wrote:

>Welcome to the Community! It’s exciting to have JStorm as part of the Apache 
>family. Looking forward to working and getting to meet you all sometime during 
>our Apache contributors journey.
>
>Please feel free to reach out in case you need anything.
>
>Best,
>Hugo
>
>On Nov 3, 2015, at 2:05 PM, P. Taylor Goetz 
>> wrote:
>
>For those who may not be aware, Alibaba has donated JStorm to Apache Storm, 
>and we have completed the IP Clearance process. JStorm is a fork of Storm with 
>the clojure components reimplemented in Java, and includes a number of 
>enhancements in terms of performance and features. JStorm is used widely in 
>production at Alibaba across many different areas.
>
>Of equal importance is the JStorm community, which has expressed a commitment 
>to join forces with the Apache Storm community to bring JStorm’s improvements 
>to Apache Storm and collaborate on new features and improvements.
>
>Over the coming days and weeks we will have a number of discussions on the 
>dev@ list regarding how to best approach merging both the incoming code and 
>associated community.
>
>Please join me in welcoming the JStorm contributors to the Apache Storm 
>community.
>
>
>JStorm community:
>
>Welcome abord! We’re glad you’re here.
>
>As you’ve probably noticed, all discussions and decision making at Apache 
>takes place on the mailing list in English. I understand that might be a 
>burden for non-English speakers, but there a number of Apache Storm 
>contributors that speak both English and Chinese that would likely be willing 
>to help translate. Google translate, while not perfect, is also helpful in 
>some cases. We don’t expect perfect translation — just enough to get your 
>point across is fine.
>
>When signing your name on an email, etc., please use the western name of 
>yourself and others. This makes it easier for those of us who can't read Asian 
>characters to identify individuals.
>
>If you’re new to Apache and the way it works, here is a good starting point 
>for learning “The Apache Way”:
>
>https://community.apache.org/contributors/
>
>Feel free to introduce yourself to the Storm community by replying to this 
>thread and letting us know a little more about yourself.
>
>Again, thank you and welcome!
>
>-Taylor
>


  

Re: [VOTE] Release Apache Storm 0.10.0 (rc1)

[Kishorkumar Patil]

+1.
Verified by running some sample tests.
-Kishor 


 On Monday, October 26, 2015 1:17 PM, Derek Dagit 
 wrote:
   

 apache-storm-0.10.0-src.tar.gz.sha
apache-storm-0.10.0.tar.gz.sha

I found these two files are gzipped, but the other *sha files are OK.

 -- 
Derek


- Original Message -
From: P. Taylor Goetz 
To: dev@storm.apache.org
Cc: 
Sent: Friday, October 23, 2015 3:26 PM
Subject: [VOTE] Release Apache Storm 0.10.0 (rc1)

This is a call to vote on releasing Apache Storm 0.10.0 (rc1)

Full list of changes in this release:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=d02f94268dec229d1125a24fdf53fa303cbc2b29

The tag/commit to be voted upon is v0.10.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=45b1b148401fd05f0f79cc7abdf6b5c7fc43df20;hb=d02f94268dec229d1125a24fdf53fa303cbc2b29

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-0.10.0/apache-storm-0.10.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-0.10.0/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1025

Please vote on releasing this package as Apache Storm 0.10.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 0.10.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor 


  

Re: [DISCUSS] How about releasing 0.9.6 and 0.10.0?

[Kishorkumar Patil]

Taylor,
The patch for blocker is STORM-1106 is merged into master and 0.10.x-branch. So 
we should be good for release on 0.10.0.
-Kishor
 


 On Monday, October 12, 2015 11:46 AM, P. Taylor Goetz <ptgo...@gmail.com> 
wrote:
   

 Thanks for the heads up. I’ll proceed with he 0.9.6 release and hold off on 
0.10.0 until STORM-1106 is ready for merge.

-Taylor

> On Oct 12, 2015, at 12:36 PM, Kishorkumar Patil 
> <kpa...@yahoo-inc.com.INVALID> wrote:
> 
> The patch is available here.
> 
> https://github.com/apache/storm/pull/795
> -Kishor
> 
> 
> 
>    On Monday, October 12, 2015 11:34 AM, Bobby Evans <ev...@yahoo-inc.com> 
>wrote:
> 
> 
> OK I was wrong.  As of *now* I don't expect there to be any more blockers :)
>  - Bobby
> 
> 
>    On Monday, October 12, 2015 11:27 AM, Kishorkumar Patil 
><kpa...@yahoo-inc.com.INVALID> wrote:
> 
> 
> I don't want to be a buzzkill, but found that netty client gives up after 
> certain attempts and that can put the worker in really bad state - not 
> talking to another worker at all.
> Actually there is another critical blocker for 0.10.0 release.
> https://issues.apache.org/jira/browse/STORM-1106
> 
> I have the patch ready. I will put up the PR now.
> -Kishor
> 
> 
> 
>    On Saturday, October 10, 2015 9:28 AM, 임정택 <kabh...@gmail.com> wrote:
> 
> 
> Hi all,
> 
> Finally there's no critical / blocker issue on 0.10.0 again.
> (Thanks Bobby for resolving headache issues!)
> 
> And we pushed some bugfix commits into 0.9.x branch which can make users
> suffer.
> 
> I think we can try to release 0.10.0 for current 0.10.x branch, and 0.9.6
> for current 0.9.x branch.
> 
> What do you think? Did I miss some issues for 0.10.0 or 0.9.6?
> 
> Thanks,
> Jungtaek Lim (HeartSaVioR)
> 
> 
> 
> 
> 
> 


  

Re: [DISCUSS] How about releasing 0.9.6 and 0.10.0?

[Kishorkumar Patil]

I don't want to be a buzzkill, but found that netty client gives up after 
certain attempts and that can put the worker in really bad state - not talking 
to another worker at all.
Actually there is another critical blocker for 0.10.0 release.
https://issues.apache.org/jira/browse/STORM-1106

I have the patch ready. I will put up the PR now.
-Kishor
 


 On Saturday, October 10, 2015 9:28 AM, 임정택  wrote:
   

 Hi all,

Finally there's no critical / blocker issue on 0.10.0 again.
(Thanks Bobby for resolving headache issues!)

And we pushed some bugfix commits into 0.9.x branch which can make users
suffer.

I think we can try to release 0.10.0 for current 0.10.x branch, and 0.9.6
for current 0.9.x branch.

What do you think? Did I miss some issues for 0.10.0 or 0.9.6?

Thanks,
Jungtaek Lim (HeartSaVioR)


  

Re: [DISCUSS] How about releasing 0.9.6 and 0.10.0?

[Kishorkumar Patil]

The patch is available here. 

https://github.com/apache/storm/pull/795
-Kishor



 On Monday, October 12, 2015 11:34 AM, Bobby Evans <ev...@yahoo-inc.com> 
wrote:
   

 OK I was wrong.  As of *now* I don't expect there to be any more blockers :)
 - Bobby 


 On Monday, October 12, 2015 11:27 AM, Kishorkumar Patil 
<kpa...@yahoo-inc.com.INVALID> wrote:
   

 I don't want to be a buzzkill, but found that netty client gives up after 
certain attempts and that can put the worker in really bad state - not talking 
to another worker at all.
Actually there is another critical blocker for 0.10.0 release.
https://issues.apache.org/jira/browse/STORM-1106

I have the patch ready. I will put up the PR now.
-Kishor
 


    On Saturday, October 10, 2015 9:28 AM, 임정택 <kabh...@gmail.com> wrote:
  

 Hi all,

Finally there's no critical / blocker issue on 0.10.0 again.
(Thanks Bobby for resolving headache issues!)

And we pushed some bugfix commits into 0.9.x branch which can make users
suffer.

I think we can try to release 0.10.0 for current 0.10.x branch, and 0.9.6
for current 0.9.x branch.

What do you think? Did I miss some issues for 0.10.0 or 0.9.6?

Thanks,
Jungtaek Lim (HeartSaVioR)




   

  

Re: A question about setup-default-uncaught-exception-handler function

[Kishorkumar Patil]

Hi Chuanlei,
The setup-default-uncaught-exception-handler fails fast in both OOM and other 
uncaught Exceptions. The difference in treatment is Runtime.halt vs 
Runtime.exist (Other uncaught exceptions handled here). 

If the OOM Error, we shutdown JVM using Runtime.halt. In other cases, we call 
Runtime.exit,  which invokes all registered shutdownhooks, giving other parts a 
chance to gracefully finalize. 

Calling Runtime.halt, is extreme caution - as it shutdowns the system without 
calling any shutdownHooks. This extreme steps is essential for OOM as attempt 
to handle that itselt can rethrow more of OOMs.
So to answer your question in short, we are failing fast - running other 
shutdownhooks or not is the only difference.

-Kishor




 


 On Tuesday, July 14, 2015 10:40 AM, Chuanlei Ni nichuan...@gmail.com 
wrote:
   

 Hi,
  I want to know why setup-default-uncaught-exception-handler just deal
with the OOM error, since the fast fail is the philosophy of Storm design.
When a thread crashes in one Storm process, the process will lost its
functionality mostly.
Why not exit the whole process when an uncaught exception happens? If we
deal exception in that way, we can remove a lot of labor for ops of storm.

Thanks in advance!


  

Re: [VOTE] Release Apache Storm 0.10.0-beta

[Kishorkumar Patil]

+1
-Kishor 


 On Wednesday, June 10, 2015 12:06 PM, Kyle Nusbaum 
knusb...@yahoo-inc.com.INVALID wrote:
   

 +1 -- Kyle
 


    On Wednesday, June 10, 2015 9:40 AM, Bobby Evans 
ev...@yahoo-inc.com.INVALID wrote:
  

 +1 - Bobby
 


    On Wednesday, June 10, 2015 6:52 AM, 임정택 kabh...@gmail.com wrote:
  

 +1 (non-binding)

- test passed : OK
-- extract source tar
-- build via mvn clean install”
- topology tests via storm-starter : OK
-- run WordCounts and RollingTopWords, local mode and remote mode
- test REST APIs (upload / activate / deactivate / kill) : OK
-- upload / activate / deactivate / rebalance / kill works fine
-- confirmed that STORM-853 was fixed
- kill topology and restart nimbus immediately : OK
-- confirmed that STORM-856 was fixed

Looks good overall.

Thanks!
Jungtaek Lim (HeartSaVioR)


2015-06-10 11:18 GMT+09:00 P. Taylor Goetz ptgo...@apache.org:

 This is a call to vote on releasing Apache Storm 0.10.0-beta.

 Full list of changes in this release:


 https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=d1e10ceecba4f87f1e70bf02ec63094eef4f4bb3

 The tag/commit to be voted upon is v0.10.0-beta:


 https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=b965da3a244806eb9bfd8d7d943f72891c362cbf;hb=d1e10ceecba4f87f1e70bf02ec63094eef4f4bb3

 The source archive being voted upon can be found here:


 http://people.apache.org/~ptgoetz/apache-storm-0.10.0-beta-rc1/apache-storm-0.10.0-beta-src.tar.gz

 Other release files, signatures and digests can be found here:

 http://people.apache.org/~ptgoetz/apache-storm-0.10.0-beta-rc1/

 The release artifacts are signed with the following key:


 https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

 The Nexus staging repository for this release is:

 https://repository.apache.org/content/repositories/orgapachestorm-1017

 Please vote on releasing this package as Apache Storm 0.10.0-beta.

 When voting, please list the actions taken to verify the release.

 This vote will be open for at least 72 hours.

 [ ] +1 Release this package as Apache Storm 0.10.0-beta
 [ ]  0 No opinion
 [ ] -1 Do not release this package because...

 Thanks,
 Taylor




-- 
Name : 임 정택
Blog : http://www.heartsavior.net / http://dev.heartsavior.net
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior





  

Re: [VOTE] Release Apache Storm 0.10.0

[Kishorkumar Patil]

Sorry about the delay on this.But pull request [STORM-848] Shade external 
dependencies is up for review.

Regards,Kishor 


 On Thursday, June 4, 2015 9:01 AM, Bobby Evans 
ev...@yahoo-inc.com.INVALID wrote:
   

 Sorry to do this so late, but I actually have few things I really want to get 
in, in addition to https://github.com/apache/storm/pull/574

Can we please pull in STORM-833.  It has all the +1s it needs, we just need to 
merge it in.  It should be backwards compatible, but pulling it into a major 
version change makes it more likely that if there are issues it will not be 
that big of a deal.
Additionally Kishor has been working on shading more jars and cleaning up the 
dependencies a little bit, but waited too long to file a JIRA and put up a pull 
request.  Again I would really like to see this go into 0.10.0, because it 
pulls in all of the rolling upgrade changes.  The more things we can shade the 
more likely it is that we will not need to break binary compatibility going 
forward, but it is technically an incompatible change.  We should have a pull 
request up in a few hours.

Similarly I would love to see STORM-760 go in.  It should really help in doing 
rolling upgrades as well, although this is less critical, because it really 
only is important for upgrading the version of clojure used.  I just pushed a 
new version that resolved the merge conflicts.
I understand if you don't want to wait for some/all of these though.

- Bobby
 


    On Wednesday, June 3, 2015 10:55 PM, P. Taylor Goetz ptgo...@gmail.com 
wrote:
  

 This is a call to vote on releasing Apache Storm 0.10.0.

Full list of changes in this release:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=2154048fd123a0960a4f5854ec4dd436bb775329

The tag/commit to be voted upon is v0.10.0:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=98bb958c1707c25f8344dd3941c51859b2691c2b;hb=e995febc2dc94e91d024137c12bb74d1c543d9b1

The source archive being voted upon can be found here:

http://people.apache.org/~ptgoetz/apache-storm-0.10.0/apache-storm-0.10.0-src.tar.gz

Other release files, signatures and digests can be found here:

http://people.apache.org/~ptgoetz/apache-storm-0.10.0/

The release artifacts are signed with the following key:

https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1015/

Please vote on releasing this package as Apache Storm 0.10.0. 

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours. 

[ ] +1 Release this package as Apache Storm 0.10.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks,
Taylor



  

Re: New Committer/PMC Member: Parth Brahmbhatt

[Kishorkumar Patil]

Congratulations Parth!

-Kishor 
 


 On Wednesday, April 1, 2015 12:34 PM, Parth Brahmbhatt 
pbrahmbh...@hortonworks.com wrote:
   

 Thanks everyone.

Thanks
Parth

On 4/1/15, 10:29 AM, Kyle Nusbaum knusb...@yahoo-inc.com.INVALID wrote:

Congratulations! -- Kyle
 


    On Tuesday, March 31, 2015 6:08 PM, Bobby Evans bo...@apache.org
wrote:
  

 Congratulations Parth.

On Mon, Mar 30, 2015 at 3:59 PM P. Taylor Goetz ptgo...@apache.org
wrote:

 Please join me in welcoming Parth Brahmbhatt as a new Apache Storm
 Committer/PMC member.

 Parth has demonstrated a strong commitment to the Apache Storm community
 through active participation and mentoring on the Storm mailing lists.
 Furthermore, he has authored many enhancements and bug fixes spanning
both
 Storm¹s core codebase, as well as a numerous integration components.

 Congratulations and welcome Parth!

 -Taylor


  


  

Re: New Committer/PMC Member: Thomas Becker

[Kishorkumar Patil]

congratulations Thomas

-Kishor 

 On Tuesday, March 10, 2015 1:49 PM, Derek Dagit 
der...@yahoo-inc.com.INVALID wrote:
   

 Welcome!


 
-- 
Derek 



- Original Message -
From: Harsha st...@harsha.io
To: dev@storm.apache.org; P. Taylor Goetz ptgo...@apache.org
Cc: 
Sent: Tuesday, March 10, 2015 1:11 PM
Subject: Re: New Committer/PMC Member: Thomas Becker

Congrats Thomas and Welcome :)
-- 
Harsha



On March 10, 2015 at 11:09:05 AM, P. Taylor Goetz (ptgo...@apache.org) wrote:

Please join me in welcoming Thomas Becker (wurstmeister) as a new Apache Storm 
Committer/PMC member.  

Thomas has made significant contributions to the Storm codebase, particularly 
in the area of Kafka integration, and shown dedication to advancing the Storm 
community.  

Congratulations and welcome Thomas!  

-Taylor