[GitHub] storm issue #2502: new PR for STORM-2306 : Messaging subsystem redesign

[roshannaik]

Github user roshannaik commented on the issue:

https://github.com/apache/storm/pull/2502
  
I suspect this issue won’t show up on the setups I am using and will need 
to be triaged on your setup itself. Will work with you offline on that. 

BTW what version of Java are you using ? 


---

Re: [DISCUSS] consider EOL for version lines

[Jungtaek Lim]

Did download page being reverted only from published site? I can see
release notes are published (so I guess gitpubsub works well) but download
page doesn't represent current storm-site. Is it due to LGPL issue on Storm
1.2.0?

2018년 2월 17일 (토) 오전 2:18, P. Taylor Goetz 님이 작성:

> As part of the release process I updated the download page [1] to move
> older releases to archive.a.o as requested by INFRA. I also removed the
> “Current Release” sections for 0.9.x and 0.10.x to make it more clear that
> those lines are no longer supported.
>
> If we want to add a more explicit statement to the download page, we can
> certainly do that as well.
>
> -Taylor
>
> [1] http://storm.apache.org/downloads.html
>
> > On Feb 13, 2018, at 4:45 PM, Jungtaek Lim  wrote:
> >
> > We're in discussion to split out storm-kafka-client to have separate
> > release version and cycle. Since we have applied necessary changes to
> > storm-core of 1.1.x/1.0.x, unless storm-kafka-client needs more changes
> on
> > storm-core, storm-core 1.1.x/1.0.x should be compatible with
> > storm-kafka-client be compatible with storm-core 1.x.
> >
> > I'm OK to keep the 1.0.x version lines specifically for storm-mesos (and
> > then we would end up keeping 1.1.x version line too) if we can't avoid
> the
> > case, but I couldn't guarantee all the bug fixes should be ported back to
> > 1.0.x. We even often don't port back the bug fixes to 1.0.x version lines
> > when 1.1 is the active minor version of Storm unless the fixes are
> > critical. That means we may not port back the bug fixes to 1.1.x after
> > announcing 1.2.0 and 1.2.x-branch is cut. As we all know, it greatly
> > reduces the maintenance cost. It does make sense for storm-kafka-client
> to
> > do the backport for 1.1.x/1.0.x branches because huge changes are just
> > applied (though I guess the experiment described above may resolve such
> > issue), but not for others including storm-core except critical/blocker
> > issues.
> >
> > So in storm-mesos view, it would be better to catch up with highest
> > possible version (that's why I hope to adopt storm-mesos in storm repo,
> > maybe not likely to happen for now), and I understand storm-mesos can't
> for
> > now because of Storm's issue. I wish the investigation of "Storm on X"
> > would occur actively sooner than later, so that it can be included as
> > earlier version of Storm 2.x (ideally 2.0.0 but it is just an ideal
> view).
> >
> > Anyway, looks like there is no objection to announce 0.10.x/0.9.x
> > explicitly EOL.
> >
> > - Jungtaek Lim (HeartSaVioR)
> >
> > 2018년 2월 14일 (수) 오전 6:02, Erik Weathers  >님이
> > 작성:
> >
> >> Thanks for keeping storm-mesos in mind Stig. :)  I'd be most worried
> about
> >> any issues we might see with the backported storm-kafka-client and how
> we
> >> *might* need to fix bugs in 1.0.x.  At least it should be easy to
> >> cherry-pick fixes back into 1.0.x after the backport-stomping of
> >> STORM-2937.
> >>
> >> Look forward to working with Bobby to get a long term plan for storm to
> run
> >> on mesos in 2.x+.
> >>
> >> - Erik
> >>
> >> On Tue, Feb 13, 2018 at 11:26 AM, Stig Rohde Døssing <
> >> stigdoess...@gmail.com
> >>> wrote:
> >>
> >>> +1 to maintain 3 version lines, though we may want to look at what we
> can
> >>> do for storm mesos, which I think it currently stuck on 1.0.x.
> >>>
> >>> 2018-02-13 20:17 GMT+01:00 Hugo Da Cruz Louro  >:
> >>>
>  +1 to maintain 3 version lines. Let’s properly announce that in our
> >>> portal
>  and users list such that users know what’s coming.
> 
>  Agree with focusing on 2.0 which has a lot of improvements, rather
> than
>  1.x, x >= 3.
> 
> > On Feb 13, 2018, at 10:43 AM, Alexandre Vermeerbergen <
>  avermeerber...@gmail.com> wrote:
> >
> > +1 (non binding) to maintaining less version lines, provided that
> > 1.2.x branch is maintained long enough to allow progressive adoption
> > of 2.x
> >
> > Alexandre Vermeerbergen
> >
> > 2018-02-13 19:38 GMT+01:00 Priyank Shah :
> >> +1 to maintaining 3 version lines as suggested by Jungtaek.
> >>
> >> On 2/13/18, 9:51 AM, "Arun Iyer on behalf of Arun Mahadevan" <
>  ai...@hortonworks.com on behalf of ar...@apache.org> wrote:
> >>
> >>   +1 to maintain 3 version lines.
> >>
> >>   I think the next focus should be 2.0.0 than 1.3.0.
> >>
> >>
> >>
> >>
> >>   On 2/12/18, 11:40 PM, "Jungtaek Lim"  wrote:
> >>
> >>> Hi devs,
> >>>
> >>> I've noticed that we are providing 4 different version lines
> >> (1.1.x,
>  1.0.x,
> >>> 0.10.x, 0.9.x) in download page, and I expect we will add one more
> >>> for
> >>> 1.2.0. Moreover, we have one more develop version line (2.0.0 -
> >>> master)
> >>> which most of development happens there.
> >>>
> 

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

[Jungtaek Lim]

+1 (binding)

* verified src/bin with targz/zip archives
* checked the diff between extracted targz/zip (no difference)
* oncrpc.jar is not included in binary distribution

Thanks,
Jungtaek Lim (HeartSaVioR)

2018년 2월 17일 (토) 오전 10:07, P. Taylor Goetz 님이 작성:

> Thank you to all who have voted thus far. Although we have enough PMC +1’s
> to release, I’d like to hold the vote open until at least 24 hours have
> passed so those in other timezones have a chance to weigh in an understand
> what’s going on.
>
> -Taylor
>
> > On Feb 16, 2018, at 7:04 PM, Arun Mahadevan  wrote:
> >
> > +1 (binding)
> >
> > - Downloaded .zip/.tar.gz and verified md5.
> >
> > - Verified the oncrpc jar is not included in the distribution
> >
> > - Ran a few sample topologies, checked log viewer.
> >
> > - Built the source code from .zip file
> >
> >
> > Thanks,
> > Arun
> >
> >
> >
> > On 2/16/18, 3:27 PM, "Satish Duggana"  wrote:
> >
> >> +1 (binding)
> >>
> >> On Sat, Feb 17, 2018 at 3:03 AM, P. Taylor Goetz 
> wrote:
> >>
> >>> +1 (binding)
> >>>
> >>> Verified that the LGPL dependency is no longer included in the binary
> >>> distribution.
> >>>
> >>> -Taylor
> >>>
>  On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz 
> wrote:
> 
>  This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
> 
>  NOTE: The primary purpose of this release is to remove an
> LGPL-licensed
> >>> binary that was inadvertently included in the 1.2.0 binary release.
> 
>  Full list of changes in this release:
> 
>  https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> >>> 2.1-rc1/RELEASE_NOTES.html
> 
>  The tag/commit to be voted upon is v1.2.1:
> 
>  https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
> >>>
> 89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc347
> >>> 87f87ce684
> 
>  The source archive being voted upon can be found here:
> 
>  https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> >>> 2.1-rc1/apache-storm-1.2.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.2.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-1061
> 
>  Please vote on releasing this package as Apache Storm 1.2.1.
> 
>  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.1
>  [ ]  0 No opinion
>  [ ] -1 Do not release this package because...
> 
>  Thanks to everyone who contributed to this release.
> 
>  -Taylor
> >>>
> >>>
> >
>
>

[GitHub] storm issue #2502: new PR for STORM-2306 : Messaging subsystem redesign

[HeartSaVioR]

Github user HeartSaVioR commented on the issue:

https://github.com/apache/storm/pull/2502
  
@roshannaik 
Hmm... OK. Interesting result. Since you're planning to refresh numbers in 
doc before Storm 2.0.0, so we can revisit the number to see whether there's odd 
result shown or not.

FYI my desktop spec and OS here:

OS: Ubuntu 17.10, 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 
2018 x86_64 x86_64 x86_64
CPU: AMD Ryzen 5 1600 3.2Ghz 6 core (with hyper-thread = 12 logical cores)
RAM: Samsung DDR4 32G 19200
SSD: Samsung 850 Evo



---

[GitHub] storm issue #2502: new PR for STORM-2306 : Messaging subsystem redesign

[roshannaik]

Github user roshannaik commented on the issue:

https://github.com/apache/storm/pull/2502
  
@HeartSaVioR  
I am not seeing the reported excessive CPU usage behavior for 4 workers. 
First I tried taking some runs on my mid 2015 macbook pro (single cpu socket). 
Since no issue was seen, i reran the same on a linux server (2 sockets, 6 
physical cores per socket).

The below cmd was run.
{code}
bin/storm jar storm-loadgen-*.jar 
org.apache.storm.loadgen.ThroughputVsLatency --rate 85000 --spouts 4 
--splitters 4 --counters 4  -c topology.max.spout.pending=5000 -c 
topology.workers=4
{code}

All runs were similar so just posting results from one run for each. 


## Mac Book Runs:
**Master without 2306**  (#ab7b4ca)  [**Latency from UI =240ms**]

start(s) | end(s) | rate(tuple/s) | mean(ms) | 99%ile(ms) | 99.9%ile(ms) | 
cores | mem(MB)
-- | -- | -- | -- | -- | -- | -- | --
0 | 30 | 19,319.467 | 8,411.912 | 13,153.337 | 13,254.001 | 5.275 | 340.719
30 | 60 | 72,613.500 | 16,113.830 | 17,750.295 | 17,884.512 | 6.849 | 
364.807
60 | 90 | 75,519.067 | 19,671.741 | 21,474.836 | 21,558.723 | 6.755 | 
344.906
90 | 120 | 79,225.167 | 22,121.255 | 23,823.647 | 23,941.087 | 6.878 | 
222.115
120 | 150 | 80,967.567 | 23,784.484 | 25,585.254 | 25,652.363 | 6.889 | 
365.383
150 | 180 | 80,062.067 | 25,269.534 | 27,665.629 | 27,866.956 | 6.895 | 
343.674
180 | 210 | 78,306.300 | 27,560.823 | 30,467.424 | 30,551.310 | 7.025 | 
436.814
210 | 240 | 78,586.667 | 29,673.204 | 32,883.343 | 33,000.784 | 6.945 | 
293.014
240 | 270 | 80,500.667 | 31,513.715 | 34,795.946 | 34,829.500 | 6.818 | 
416.121
270 | 300 | 82,625.667 | 32,883.453 | 35,903.242 | 35,970.351 | 6.899 | 
364.058


**Master with 2306**  (#09e0123) [**Latency from UI =89ms**]

start(s) | end(s) | rate(tuple/s) | mean(ms) | 99%ile(ms) | 99.9%ile(ms) | 
cores | mem(MB)
-- | -- | -- | -- | -- | -- | -- | --
0 | 30 | 19,607.100 | 8,127.475 | 14,277.411 | 14,772.339 | 4.861 | 330.486
30 | 60 | 85,946.533 | 12,737.708 | 18,471.715 | 18,589.155 | 6.587 | 
418.567
60 | 90 | 91,256.133 | 12,276.112 | 17,901.289 | 18,001.953 | 6.527 | 
229.531
90 | 120 | 95,317.967 | 9,204.098 | 14,529.069 | 14,612.955 | 6.552 | 
432.803
120 | 150 | 97,220.233 | 5,221.476 | 9,865.003 | 10,125.050 | 6.551 | 
169.757
150 | 180 | 92,499.200 | 984.904 | 4,213.178 | 4,546.626 | 6.746 | 280.883
180 | 210 | 79,557.700 | 1,059.939 | 2,619.343 | 2,766.143 | 6.155 | 430.853
210 | 240 | 79,766.467 | 2,336.027 | 5,158.994 | 5,347.738 | 6.238 | 288.708
240 | 270 | 81,595.800 | 4,284.723 | 7,377.781 | 7,528.776 | 6.258 | 315.524
270 | 300 | 88,294.067 | 5,024.767 | 8,422.162 | 8,493.466 | 6.412 | 263.682


## Linux Server Runs:

**Master without 2306**  (#ab7b4ca)  [**Latency from UI =15ms**]

start_time(s) | end_time(s) | rate(tuple/s) | mean(ms) | 99%ile(ms) | 
99.9%ile(ms) | cores | mem(MB)
-- | -- | -- | -- | -- | -- | -- | --
0 | 30 | 56,704.80 | 1,194.20 | 3,867.15 | 3,978.30 | 11.294 | 978.701
30 | 60 | 85,001.70 | 12.018 | 21.479 | 26.837 | 11.931 | 897.105
60 | 90 | 85,007.17 | 11.84 | 21.152 | 26.345 | 11.575 | 950.129
90 | 120 | 85,008.13 | 11.781 | 20.447 | 24.986 | 11.688 | 882.768
120 | 150 | 85,009.57 | 11.841 | 21.021 | 25.592 | 11.735 | 921.339
150 | 180 | 84,997.60 | 11.763 | 20.791 | 25.199 | 11.476 | 961.395
180 | 210 | 85,005.57 | 11.824 | 20.66 | 25.281 | 11.798 | 1,000.03
210 | 240 | 85,008.00 | 11.75 | 20.611 | 25.706 | 11.354 | 1,120.33
240 | 271 | 82,259.16 | 11.916 | 20.955 | 25.117 | 11.517 | 939.918
271 | 301 | 85,003.57 | 11.719 | 20.398 | 24.822 | 11.322 | 980.654

 

**Master with 2306**  (#09e0123) [**Latency from UI =7.8ms**]

start_time(s) | end_time(s) | rate(tuple/s) | mean(ms) | 99%ile(ms) | 
99.9%ile(ms) | cores | mem(MB)
-- | -- | -- | -- | -- | -- | -- | --
0 | 30 | 56,701.03 | 426.534 | 2,673.87 | 2,793.41 | 7.693 | 290.006
30 | 60 | 85,004.40 | 3.387 | 8.294 | 14.655 | 5.89 | 231.328
60 | 90 | 85,002.20 | 3.332 | 7.66 | 10.945 | 5.791 | 247.683
90 | 121 | 82,259.87 | 3.33 | 7.516 | 9.839 | 5.591 | 264.324
121 | 151 | 85,004.37 | 3.349 | 7.737 | 10.969 | 5.819 | 272.916
151 | 181 | 85,001.07 | 3.323 | 7.434 | 9.961 | 5.747 | 203.54
181 | 211 | 85,002.57 | 3.335 | 7.586 | 10.281 | 5.794 | 304.567
211 | 241 | 85,005.03 | 3.326 | 7.475 | 9.921 | 5.836 | 317.026
241 | 271 | 85,003.27 | 3.339 | 7.565 | 10.527 | 5.723 | 251.676
271 | 301 | 85,002.00 | 3.351 | 7.799 | 12.394 | 5.716 | 377.182


## Summary:
**On Linux** Both CPU and mem usage was significantly better for 2306.  
Actual latency (taken from UI) was also much better for 2306.

**On Macbook:** Both CPU & mem usage were relatively close but slightly 
favoring 2306. Again, the 

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

[P. Taylor Goetz]

Thank you to all who have voted thus far. Although we have enough PMC +1’s to 
release, I’d like to hold the vote open until at least 24 hours have passed so 
those in other timezones have a chance to weigh in an understand what’s going 
on.

-Taylor

> On Feb 16, 2018, at 7:04 PM, Arun Mahadevan  wrote:
> 
> +1 (binding)
> 
> - Downloaded .zip/.tar.gz and verified md5.
> 
> - Verified the oncrpc jar is not included in the distribution
> 
> - Ran a few sample topologies, checked log viewer.
> 
> - Built the source code from .zip file
> 
> 
> Thanks,
> Arun
> 
> 
> 
> On 2/16/18, 3:27 PM, "Satish Duggana"  wrote:
> 
>> +1 (binding)
>> 
>> On Sat, Feb 17, 2018 at 3:03 AM, P. Taylor Goetz  wrote:
>> 
>>> +1 (binding)
>>> 
>>> Verified that the LGPL dependency is no longer included in the binary
>>> distribution.
>>> 
>>> -Taylor
>>> 
 On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz  wrote:
 
 This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
 
 NOTE: The primary purpose of this release is to remove an LGPL-licensed
>>> binary that was inadvertently included in the 1.2.0 binary release.
 
 Full list of changes in this release:
 
 https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>>> 2.1-rc1/RELEASE_NOTES.html
 
 The tag/commit to be voted upon is v1.2.1:
 
 https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
>>> 89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc347
>>> 87f87ce684
 
 The source archive being voted upon can be found here:
 
 https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>>> 2.1-rc1/apache-storm-1.2.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.2.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-1061
 
 Please vote on releasing this package as Apache Storm 1.2.1.
 
 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.1
 [ ]  0 No opinion
 [ ] -1 Do not release this package because...
 
 Thanks to everyone who contributed to this release.
 
 -Taylor
>>> 
>>> 
> 



signature.asc
Description: Message signed with OpenPGP

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

[Arun Mahadevan]

+1 (binding)

- Downloaded .zip/.tar.gz and verified md5.

- Verified the oncrpc jar is not included in the distribution

- Ran a few sample topologies, checked log viewer.

- Built the source code from .zip file


Thanks,
Arun



On 2/16/18, 3:27 PM, "Satish Duggana"  wrote:

>+1 (binding)
>
>On Sat, Feb 17, 2018 at 3:03 AM, P. Taylor Goetz  wrote:
>
>> +1 (binding)
>>
>> Verified that the LGPL dependency is no longer included in the binary
>> distribution.
>>
>> -Taylor
>>
>> > On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz  wrote:
>> >
>> > This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
>> >
>> > NOTE: The primary purpose of this release is to remove an LGPL-licensed
>> binary that was inadvertently included in the 1.2.0 binary release.
>> >
>> > Full list of changes in this release:
>> >
>> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>> 2.1-rc1/RELEASE_NOTES.html
>> >
>> > The tag/commit to be voted upon is v1.2.1:
>> >
>> > https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
>> 89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc347
>> 87f87ce684
>> >
>> > The source archive being voted upon can be found here:
>> >
>> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>> 2.1-rc1/apache-storm-1.2.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.2.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-1061
>> >
>> > Please vote on releasing this package as Apache Storm 1.2.1.
>> >
>> > 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.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.2.1 (rc1)

[Satish Duggana]

+1 (binding)

On Sat, Feb 17, 2018 at 3:03 AM, P. Taylor Goetz  wrote:

> +1 (binding)
>
> Verified that the LGPL dependency is no longer included in the binary
> distribution.
>
> -Taylor
>
> > On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz  wrote:
> >
> > This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
> >
> > NOTE: The primary purpose of this release is to remove an LGPL-licensed
> binary that was inadvertently included in the 1.2.0 binary release.
> >
> > Full list of changes in this release:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> 2.1-rc1/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v1.2.1:
> >
> > https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=
> 89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc347
> 87f87ce684
> >
> > The source archive being voted upon can be found here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
> 2.1-rc1/apache-storm-1.2.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.2.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-1061
> >
> > Please vote on releasing this package as Apache Storm 1.2.1.
> >
> > 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.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.2.1 (rc1)

[P. Taylor Goetz]

+1 (binding)

Verified that the LGPL dependency is no longer included in the binary 
distribution.

-Taylor

> On Feb 16, 2018, at 4:01 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
> 
> NOTE: The primary purpose of this release is to remove an LGPL-licensed 
> binary that was inadvertently included in the 1.2.0 binary release.
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.1:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc34787f87ce684
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/apache-storm-1.2.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.2.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-1061
> 
> Please vote on releasing this package as Apache Storm 1.2.1.
> 
> 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.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP

[GitHub] storm pull request #2559: STORM-2952: Deprecate storm-kafka

[srdo]

GitHub user srdo opened a pull request:

https://github.com/apache/storm/pull/2559

STORM-2952: Deprecate storm-kafka

https://issues.apache.org/jira/browse/STORM-2952

Please let this sit for a few days before merging, to give people time to 
object.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/srdo/storm STORM-2952

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/storm/pull/2559.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2559


commit f95000f2d7c6f0b62b50ea83ab476cf5c0c2255a
Author: Stig Rohde Døssing 
Date:   2018-02-16T21:20:00Z

STORM-2952: Deprecate storm-kafka




---

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

[Hugo Da Cruz Louro]

+1 (binding)

> On Feb 16, 2018, at 1:01 PM, P. Taylor Goetz  wrote:
> 
> This is a call to vote on releasing Apache Storm 1.2.1 (rc1)
> 
> NOTE: The primary purpose of this release is to remove an LGPL-licensed 
> binary that was inadvertently included in the 1.2.0 binary release.
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.1:
> 
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=89646c86c667e0a35aed45c8063d777ae1f32b30;hb=d156d25d991311eaa1f5131d3dc34787f87ce684
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/apache-storm-1.2.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.2.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-1061
> 
> Please vote on releasing this package as Apache Storm 1.2.1.
> 
> 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.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> -Taylor

[VOTE] Release Apache Storm 1.2.1 (rc1)

[P. Taylor Goetz]

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

NOTE: The primary purpose of this release is to remove an LGPL-licensed binary 
that was inadvertently included in the 1.2.0 binary release.

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v1.2.1:

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

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.1-rc1/apache-storm-1.2.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.2.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-1061

Please vote on releasing this package as Apache Storm 1.2.1.

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.1
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

-Taylor


signature.asc
Description: Message signed with OpenPGP

[GitHub] storm issue #2556: STORM-2946: Upgrade to HBase 2.0

[ptgoetz]

Github user ptgoetz commented on the issue:

https://github.com/apache/storm/pull/2556
  
@arunmahadevan Yes, I will share the results of my testing and will test 
for backward compatibility.

I don't have high hopes for backward compatibility based on 
https://hbase.apache.org/book.html#hbase.versioning

If it isn't compatible, we could either maintain separate storm-hbase 
modules, or start versioning/releasing storm-hbase independently of storm as 
we've discussed doing with storm-kafka-client. I'd lean toward the latter.


---

Re: [DISCUSS] consider EOL for version lines

[P. Taylor Goetz]

As part of the release process I updated the download page [1] to move older 
releases to archive.a.o as requested by INFRA. I also removed the “Current 
Release” sections for 0.9.x and 0.10.x to make it more clear that those lines 
are no longer supported.

If we want to add a more explicit statement to the download page, we can 
certainly do that as well.

-Taylor

[1] http://storm.apache.org/downloads.html

> On Feb 13, 2018, at 4:45 PM, Jungtaek Lim  wrote:
> 
> We're in discussion to split out storm-kafka-client to have separate
> release version and cycle. Since we have applied necessary changes to
> storm-core of 1.1.x/1.0.x, unless storm-kafka-client needs more changes on
> storm-core, storm-core 1.1.x/1.0.x should be compatible with
> storm-kafka-client be compatible with storm-core 1.x.
> 
> I'm OK to keep the 1.0.x version lines specifically for storm-mesos (and
> then we would end up keeping 1.1.x version line too) if we can't avoid the
> case, but I couldn't guarantee all the bug fixes should be ported back to
> 1.0.x. We even often don't port back the bug fixes to 1.0.x version lines
> when 1.1 is the active minor version of Storm unless the fixes are
> critical. That means we may not port back the bug fixes to 1.1.x after
> announcing 1.2.0 and 1.2.x-branch is cut. As we all know, it greatly
> reduces the maintenance cost. It does make sense for storm-kafka-client to
> do the backport for 1.1.x/1.0.x branches because huge changes are just
> applied (though I guess the experiment described above may resolve such
> issue), but not for others including storm-core except critical/blocker
> issues.
> 
> So in storm-mesos view, it would be better to catch up with highest
> possible version (that's why I hope to adopt storm-mesos in storm repo,
> maybe not likely to happen for now), and I understand storm-mesos can't for
> now because of Storm's issue. I wish the investigation of "Storm on X"
> would occur actively sooner than later, so that it can be included as
> earlier version of Storm 2.x (ideally 2.0.0 but it is just an ideal view).
> 
> Anyway, looks like there is no objection to announce 0.10.x/0.9.x
> explicitly EOL.
> 
> - Jungtaek Lim (HeartSaVioR)
> 
> 2018년 2월 14일 (수) 오전 6:02, Erik Weathers 님이
> 작성:
> 
>> Thanks for keeping storm-mesos in mind Stig. :)  I'd be most worried about
>> any issues we might see with the backported storm-kafka-client and how we
>> *might* need to fix bugs in 1.0.x.  At least it should be easy to
>> cherry-pick fixes back into 1.0.x after the backport-stomping of
>> STORM-2937.
>> 
>> Look forward to working with Bobby to get a long term plan for storm to run
>> on mesos in 2.x+.
>> 
>> - Erik
>> 
>> On Tue, Feb 13, 2018 at 11:26 AM, Stig Rohde Døssing <
>> stigdoess...@gmail.com
>>> wrote:
>> 
>>> +1 to maintain 3 version lines, though we may want to look at what we can
>>> do for storm mesos, which I think it currently stuck on 1.0.x.
>>> 
>>> 2018-02-13 20:17 GMT+01:00 Hugo Da Cruz Louro :
>>> 
 +1 to maintain 3 version lines. Let’s properly announce that in our
>>> portal
 and users list such that users know what’s coming.
 
 Agree with focusing on 2.0 which has a lot of improvements, rather than
 1.x, x >= 3.
 
> On Feb 13, 2018, at 10:43 AM, Alexandre Vermeerbergen <
 avermeerber...@gmail.com> wrote:
> 
> +1 (non binding) to maintaining less version lines, provided that
> 1.2.x branch is maintained long enough to allow progressive adoption
> of 2.x
> 
> Alexandre Vermeerbergen
> 
> 2018-02-13 19:38 GMT+01:00 Priyank Shah :
>> +1 to maintaining 3 version lines as suggested by Jungtaek.
>> 
>> On 2/13/18, 9:51 AM, "Arun Iyer on behalf of Arun Mahadevan" <
 ai...@hortonworks.com on behalf of ar...@apache.org> wrote:
>> 
>>   +1 to maintain 3 version lines.
>> 
>>   I think the next focus should be 2.0.0 than 1.3.0.
>> 
>> 
>> 
>> 
>>   On 2/12/18, 11:40 PM, "Jungtaek Lim"  wrote:
>> 
>>> Hi devs,
>>> 
>>> I've noticed that we are providing 4 different version lines
>> (1.1.x,
 1.0.x,
>>> 0.10.x, 0.9.x) in download page, and I expect we will add one more
>>> for
>>> 1.2.0. Moreover, we have one more develop version line (2.0.0 -
>>> master)
>>> which most of development happens there.
>>> 
>>> Recently we're releasing 3 version lines (1.0.6 / 1.1.2 / 1.2.0)
>>> simultaneously and it took heavy effort to track all the RCs and
 verify all
>>> of them. I guess release manager would take more overhead of
 releasing, and
>>> it doesn't make sense for me if we continue maintaining all of
>> them.
>>> 
>>> Ideally I'd like to propose maintaining three version lines: 2.0.0
 (next
>>> major) / 1.3.0 (next minor - may not happen) / 1.2.1 (next bugfix)
>>> and

[ANNOUNCE] Apache Storm 1.2.0 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.2.0.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/15/storm120-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.2.0

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.2.0/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[ANNOUNCE] Apache Storm 1.1.2 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.1.2.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/15/storm112-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.1.2

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.1.2/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM

[ANNOUNCE] Apache Storm 1.0.6 Released

[P. Taylor Goetz]

The Apache Storm community is pleased to announce the release of Apache Storm 
version 1.0.6.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2018/02/14/storm106-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 1.0.5

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: http://www.us.apache.org/dist/storm/apache-storm-1.0.6/RELEASE_NOTES.html
[2]: https://issues.apache.org/jira/browse/STORM