[CANCELED] [VOTE] Release Apache Storm 1.2.0 (rc1)

Canceling in order to include a fix for https://issues.apache.org/jira/browse/STORM-2912 . -Taylor > On Jan 23, 2018, at 10:54 AM, P. Taylor Goetz wrote: > > This is a call to vote on releasing Apache Storm 1.2.0 (rc1) > >

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

I found the cause. Filed https://issues.apache.org/jira/browse/STORM-2912. Will craft patches for branches shortly. FYI, this issue affects all the RCs being opened now. I'll comment to other RCs as well. -Jungtaek Lim (HeartSaVioR) 2018년 1월 25일 (목) 오후 12:09, Jungtaek Lim 님이

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

Alexandre, As Priyank stated we're seeing odd numbers in storm-starter. I also found the odd value but it was not 1.2.0 but RC for another version. Maybe I missed to check for 1.2.0 here. I'm planning to test all the open release candidates as well and test with various topologies, but it would

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

Release looks good overall except for complete latency and capacity. Verified the md5, sha and asc Unzipped and untared the source and binary releases. Built from source and ran daemons from storm-dist binary release after packing from the same. Submitted FastWordCount and RollingTopWords Played

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

Hello Storm developers, One of my team member (Noureddine Chatti) found that the regression in "Assigned Memory (MB)" columns for our topologies with Storm 1.2.0rc1, where the 65 MB value is displayed regardless of our actual topologies's memory setting: We define our workers's max memory heap

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

+1 (binding) - Downloaded and deployed the tar.gz and .zip binary distribution. - Verified MD5. - Built the source with JDK 1.8 - Ran a few sample topologies and observed the output. - Viewed the worker logs via log viewer and did some basic sanity on the metrics. Thanks, Arun On 1/23/18,

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

Here is the correct URL for the changes in this release (Thanks Stig!): https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc1/RELEASE_NOTES.html -Taylor > On Jan 23, 2018, at 3:36 PM, P.

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

Let's back to verify the release and vote. +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 7 --

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

Alexandre, Please file an issue with screenshot and reproducible step (if only possible). It would be very appreciated if you could spend time to dive into the codebase and find the cause, and fix and submit a patch (only when you could get it). Open source community can't live without

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

Yes, that’s the same error I got, and I think we both just shaved the same yak. ;) I imagine infra is enforcing TLS > 1.0 now. -Taylor > On Jan 23, 2018, at 7:46 PM, Jungtaek Lim wrote: > > Stig, the script doesn't also work for me, but that's not because of script > or

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

Stig, I checked with Jungtaek, and he’s hitting the same issue I am. Could you send me the output for 1.2.0, 1.1.2, and 1.0.6 if you have a chance? Thanks in advance! -Taylor > On Jan 23, 2018, at 6:20 PM, Stig Rohde Døssing > wrote: > > Taylor, > > The release

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

Stig, the script doesn't also work for me, but that's not because of script or jira module error. I've encountered TLSV1_ALERT_PROTOCOL_VERSION error and my python2.7 is unfortunately coupled with OpenSSL 0.9.8zh which doesn't support TLSv1.2. My python3.6 is coupled with OpenSSL 1.0.2l but the

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

Taylor, The release notes script appears to work fine for me. There are a couple of issues with fix version 1.2.0 that are not resolved, which we should fix. Note that 2710 is the release 1.2.0 epic, we might want to not mark that with a fix version so it isn't included in the release notes.

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

Looks weird, at-least the storm-starter exclamation and word count topologies shows Assigned Mem: 2496 MB and capacity numbers in the range of “0.005 - 0.015” on a 16 GB macbook. Thanks, Arun On 1/23/18, 3:09 PM, "Alexandre Vermeerbergen" wrote: >Hello, > >I'm

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

Hello, I'm afraid I my vote in 1.2.0 RC1 is a -1: Indeed metrics displayed in Storm UI from 1.2.0 RC1 are obviously wrong. See for example attached picture showing "Assigned Mem (MB)" for one of our topologies: - On the left hand side we have Storm 1.1.0 showing 2112 MB on each host, which

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

Let's not block releasing because of minor issues. We've discussed releasing 1.2.0 more than 2 months which is fairly long. Don't want to drag this more. There may be small time frame if RC1 is cancelled for some reason. Let's have short discussion to decide which things to include then. I also

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

Hello, Just to let you know that I ran some basic tests on a small development cluster (ok so far) so I am patching our pre-production environment (with 6 Supervison large VMs, and Kafka Brokers at version 1.0.0) to get results at scale. My hope this that will all recent activity with Storm

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

Note that the link to changes is incorrect. I will provide a corrected link once I sort out issues with the release notes script. Stig — Is the release notes script working for you? I’m getting ssl errors. -Taylor > On Jan 23, 2018, at 10:54 AM, P. Taylor Goetz wrote: > >

[VOTE] Release Apache Storm 1.2.0 (rc1)

This is a call to vote on releasing Apache Storm 1.2.0 (rc1) Full list of changes in this release: https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=0071c67836d1fba0eb31e8f980d80459db14efb8;hb=f04b7a3a74580bde2681504313aa158b5956e7de The tag/commit to be voted upon is v1.2.0: