You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "P. Taylor Goetz" <pt...@gmail.com> on 2018/02/06 21:01:10 UTC
[VOTE] Release Apache Storm 1.2.0 (rc3)
This is a call to vote on releasing Apache Storm 1.2.0 (rc3)
Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/RELEASE_NOTES.html
The tag/commit to be voted upon is v1.2.0:
https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7be1308bfea0d71efac141888cdcfc9e708cfff5;hb=b20228de004dda52e414a9ade6e60ff0756df9d1
The source archive being voted upon can be found here:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.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-1.2.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-1057
Please vote on releasing this package as Apache Storm 1.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 1.2.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 1.2.0 (rc3)
Posted by Jungtaek Lim <ka...@gmail.com>.
CORRECTION: didn't check md5/sha from source targz/zip since the files are
not presented. Will check again once they are available.
2018년 2월 7일 (수) 오후 10:49, Jungtaek Lim <ka...@gmail.com>님이 작성:
> +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
> -- 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
>
> Both STORM-2853 [1] and STORM-2912 [2] are confirmed to be resolved in
> verification phase.
>
> Thanks,
> Jungtaek Lim (HeartSaVioR)
>
> 1. https://issues.apache.org/jira/browse/STORM-2853
> 2. https://issues.apache.org/jira/browse/STORM-2912
>
>
> 2018년 2월 7일 (수) 오후 9:39, Jungtaek Lim <ka...@gmail.com>님이 작성:
>
>> Looks like missing md5/sha for apache-storm-1.2.0-src.tar.gz as well as
>> apache-storm-1.2.0-src.zip.
>>
>> I'll continue verifying without that.
>>
>> 2018년 2월 7일 (수) 오전 6:01, P. Taylor Goetz <pt...@gmail.com>님이 작성:
>>
>>> This is a call to vote on releasing Apache Storm 1.2.0 (rc3)
>>>
>>> Full list of changes in this release:
>>>
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/RELEASE_NOTES.html
>>>
>>> The tag/commit to be voted upon is v1.2.0:
>>>
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7be1308bfea0d71efac141888cdcfc9e708cfff5;hb=b20228de004dda52e414a9ade6e60ff0756df9d1
>>>
>>> The source archive being voted upon can be found here:
>>>
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.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-1.2.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-1057
>>>
>>> Please vote on releasing this package as Apache Storm 1.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 1.2.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 1.2.0 (rc3)
Posted by Jungtaek Lim <ka...@gmail.com>.
+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
-- 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
Both STORM-2853 [1] and STORM-2912 [2] are confirmed to be resolved in
verification phase.
Thanks,
Jungtaek Lim (HeartSaVioR)
1. https://issues.apache.org/jira/browse/STORM-2853
2. https://issues.apache.org/jira/browse/STORM-2912
2018년 2월 7일 (수) 오후 9:39, Jungtaek Lim <ka...@gmail.com>님이 작성:
> Looks like missing md5/sha for apache-storm-1.2.0-src.tar.gz as well as
> apache-storm-1.2.0-src.zip.
>
> I'll continue verifying without that.
>
> 2018년 2월 7일 (수) 오전 6:01, P. Taylor Goetz <pt...@gmail.com>님이 작성:
>
>> This is a call to vote on releasing Apache Storm 1.2.0 (rc3)
>>
>> Full list of changes in this release:
>>
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/RELEASE_NOTES.html
>>
>> The tag/commit to be voted upon is v1.2.0:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7be1308bfea0d71efac141888cdcfc9e708cfff5;hb=b20228de004dda52e414a9ade6e60ff0756df9d1
>>
>> The source archive being voted upon can be found here:
>>
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.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-1.2.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-1057
>>
>> Please vote on releasing this package as Apache Storm 1.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 1.2.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 1.2.0 (rc3)
Posted by Jungtaek Lim <ka...@gmail.com>.
Filed https://issues.apache.org/jira/browse/STORM-2943 for
storm-kafka-monitor src/javadoc inclusion issue and assigned to Taylor.
2018년 2월 8일 (목) 오전 5:32, Jungtaek Lim <ka...@gmail.com>님이 작성:
> Thanks for addressing md5/sha issue, Taylor. Verified src.tar.gz and
> src.zip.
>
> Alexandre, thanks again for thoughtful verification of release. It much
> helped for us and I really appreciate it. Please keep up the good work.
>
> I feel what Alexandre reported is a blocker since it leads strange error
> in point of user side, worth to cancel current RC. Changing my vote to -1
> (binding).
>
> -Jungtaek Lim (HeartSaVioR)
>
> 2018년 2월 8일 (목) 오전 5:20, P. Taylor Goetz <pt...@gmail.com>님이 작성:
>
>> Yes. It will be fixed. Thanks again for pointing it out.
>>
>> -Taylor
>>
>> > On Feb 7, 2018, at 2:57 PM, Alexandre Vermeerbergen <
>> avermeerbergen@gmail.com> wrote:
>> >
>> > Hello Taylor,
>> >
>> > Yes same issue in Storm 1.1.0 : we have a production storm cluster
>> > based on this release, but then we were using our own Kafka spout, no
>> > we weren't impacted by this packaging issue.
>> >
>> > Could the extraneous files be cleaned up from 1.2.0-final?
>> >
>> > Best regards,
>> > Alexandre Vermeerbergen
>> >
>> > 2018-02-07 19:18 GMT+01:00 P. Taylor Goetz <pt...@gmail.com>:
>> >> Hi Alexandre,
>> >>
>> >> Thanks for the review. You’re right, the javadoc/source jars should
>> not be there, though it looks like this has been the case for a long time
>> and would have affected previous releases.
>> >>
>> >> It looks like the problem was introduced in 1.1.0. Have you seen the
>> same issue in other 1.1.x releases, or just seeing this now?
>> >>
>> >> -Taylor
>> >>
>> >>> On Feb 7, 2018, at 12:40 PM, Alexandre Vermeerbergen <
>> avermeerbergen@gmail.com> wrote:
>> >>>
>> >>> Hello All,
>> >>>
>> >>> I hate to be the one who always give bad news, but as a matter of
>> >>> facts, Storm 1.2.0 RC3 installation from binary artifacts (both
>> >>> apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
>> >>> default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
>> >>> ui.log)
>> >>>
>> >>> Here's for example what I get from apache-storm-1.2.0-src.tar.gz
>> >>> downloaded from
>> >>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz
>> :
>> >>>
>> >>> $ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
>> >>> -rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
>> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
>> >>> -rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
>> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
>> >>> -rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
>> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
>> >>>
>> >>> And here's what I see in ui.log:
>> >>>
>> >>> org.apache.storm.kafka.spout.KafkaSpout
>> >>> 2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
>> >>> [WARN] Exception message:Error: Could not find or load main class
>> >>>
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>> >>>
>> >>> org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
>> >>> find or load main class
>> >>>
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>> >>>
>> >>> at
>> org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at clojure.core$some.invoke(core.clj:2570)
>> ~[clojure-1.7.0.jar:?]
>> >>> at
>> org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at clojure.lang.RestFn.applyTo(RestFn.java:139)
>> ~[clojure-1.7.0.jar:?]
>> >>> at clojure.core$apply.invoke(core.clj:632)
>> ~[clojure-1.7.0.jar:?]
>> >>> at
>> org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>>
>> >>> Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
>> >>> storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
>> >>> solves the issue.
>> >>>
>> >>> However, binaries artifacts should be as clean as possible, isn't it ?
>> >>>
>> >>> Best regards,
>> >>> Alexandre Vermeerbergen
>> >>
>>
>>
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by Alexandre Vermeerbergen <av...@gmail.com>.
Hello Jungtaek,
Reporting bugs is the least I can do to thank you guys for developing Storm :)
I understand that there will be a RC4, but just FYI I have tested RC3
on a small Storm cluster with our 10+ topologies (small setup: 1
Nimbus VM, 1 Supervisor VM, 1 Zookeeper VM, Kafka Broker 1.0.0 and
Kafka Client Jars also at 1.0.0 with Storm Kafka Client 1.2.0).
I have by-passed the Storm-Monitoring issue on this cluster.
So far so good : it's up and running all day, without ERROR nor WARN
messages, which confirms that the endless WARN messages for Kafka
Spouts in autocommit mode have been indeed fixed => thanks
I'm waiting for RC4 to test it on our big scale pre-production cluster.
Best regards,
Alexandre Vermeerbergen
2018-02-07 21:32 GMT+01:00 Jungtaek Lim <ka...@gmail.com>:
> Thanks for addressing md5/sha issue, Taylor. Verified src.tar.gz and
> src.zip.
>
> Alexandre, thanks again for thoughtful verification of release. It much
> helped for us and I really appreciate it. Please keep up the good work.
>
> I feel what Alexandre reported is a blocker since it leads strange error in
> point of user side, worth to cancel current RC. Changing my vote to -1
> (binding).
>
> -Jungtaek Lim (HeartSaVioR)
>
> 2018년 2월 8일 (목) 오전 5:20, P. Taylor Goetz <pt...@gmail.com>님이 작성:
>
>> Yes. It will be fixed. Thanks again for pointing it out.
>>
>> -Taylor
>>
>> > On Feb 7, 2018, at 2:57 PM, Alexandre Vermeerbergen <
>> avermeerbergen@gmail.com> wrote:
>> >
>> > Hello Taylor,
>> >
>> > Yes same issue in Storm 1.1.0 : we have a production storm cluster
>> > based on this release, but then we were using our own Kafka spout, no
>> > we weren't impacted by this packaging issue.
>> >
>> > Could the extraneous files be cleaned up from 1.2.0-final?
>> >
>> > Best regards,
>> > Alexandre Vermeerbergen
>> >
>> > 2018-02-07 19:18 GMT+01:00 P. Taylor Goetz <pt...@gmail.com>:
>> >> Hi Alexandre,
>> >>
>> >> Thanks for the review. You’re right, the javadoc/source jars should not
>> be there, though it looks like this has been the case for a long time and
>> would have affected previous releases.
>> >>
>> >> It looks like the problem was introduced in 1.1.0. Have you seen the
>> same issue in other 1.1.x releases, or just seeing this now?
>> >>
>> >> -Taylor
>> >>
>> >>> On Feb 7, 2018, at 12:40 PM, Alexandre Vermeerbergen <
>> avermeerbergen@gmail.com> wrote:
>> >>>
>> >>> Hello All,
>> >>>
>> >>> I hate to be the one who always give bad news, but as a matter of
>> >>> facts, Storm 1.2.0 RC3 installation from binary artifacts (both
>> >>> apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
>> >>> default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
>> >>> ui.log)
>> >>>
>> >>> Here's for example what I get from apache-storm-1.2.0-src.tar.gz
>> >>> downloaded from
>> >>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz
>> :
>> >>>
>> >>> $ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
>> >>> -rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
>> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
>> >>> -rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
>> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
>> >>> -rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
>> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
>> >>>
>> >>> And here's what I see in ui.log:
>> >>>
>> >>> org.apache.storm.kafka.spout.KafkaSpout
>> >>> 2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
>> >>> [WARN] Exception message:Error: Could not find or load main class
>> >>>
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>> >>>
>> >>> org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
>> >>> find or load main class
>> >>>
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>> >>>
>> >>> at
>> org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
>> >>> at
>> org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at clojure.lang.RestFn.applyTo(RestFn.java:139)
>> ~[clojure-1.7.0.jar:?]
>> >>> at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
>> >>> at
>> org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>> at
>> org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
>> >>> ~[storm-core-1.2.0.jar:1.2.0]
>> >>>
>> >>> Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
>> >>> storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
>> >>> solves the issue.
>> >>>
>> >>> However, binaries artifacts should be as clean as possible, isn't it ?
>> >>>
>> >>> Best regards,
>> >>> Alexandre Vermeerbergen
>> >>
>>
>>
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
I agree. As a heads up, I’m going to commit the the following change for 1.x and 1.1.x:
--- a/storm-dist/binary/src/main/assembly/binary.xml
+++ b/storm-dist/binary/src/main/assembly/binary.xml
@@ -313,7 +313,7 @@
<directory>${project.basedir}/../../external/storm-kafka-monitor/target</directory>
<outputDirectory>toollib</outputDirectory>
<includes>
- <include>storm*jar</include>
+ <include>storm-kafka-monitor-${project.version}.jar</include>
</includes>
</fileSet>
<!-- Autocred plugins -->
That will be the only difference between rc3 and rc4.
-Taylor
> On Feb 7, 2018, at 3:32 PM, Jungtaek Lim <ka...@gmail.com> wrote:
>
> Thanks for addressing md5/sha issue, Taylor. Verified src.tar.gz and
> src.zip.
>
> Alexandre, thanks again for thoughtful verification of release. It much
> helped for us and I really appreciate it. Please keep up the good work.
>
> I feel what Alexandre reported is a blocker since it leads strange error in
> point of user side, worth to cancel current RC. Changing my vote to -1
> (binding).
>
> -Jungtaek Lim (HeartSaVioR)
>
> 2018년 2월 8일 (목) 오전 5:20, P. Taylor Goetz <pt...@gmail.com>님이 작성:
>
>> Yes. It will be fixed. Thanks again for pointing it out.
>>
>> -Taylor
>>
>>> On Feb 7, 2018, at 2:57 PM, Alexandre Vermeerbergen <
>> avermeerbergen@gmail.com> wrote:
>>>
>>> Hello Taylor,
>>>
>>> Yes same issue in Storm 1.1.0 : we have a production storm cluster
>>> based on this release, but then we were using our own Kafka spout, no
>>> we weren't impacted by this packaging issue.
>>>
>>> Could the extraneous files be cleaned up from 1.2.0-final?
>>>
>>> Best regards,
>>> Alexandre Vermeerbergen
>>>
>>> 2018-02-07 19:18 GMT+01:00 P. Taylor Goetz <pt...@gmail.com>:
>>>> Hi Alexandre,
>>>>
>>>> Thanks for the review. You’re right, the javadoc/source jars should not
>> be there, though it looks like this has been the case for a long time and
>> would have affected previous releases.
>>>>
>>>> It looks like the problem was introduced in 1.1.0. Have you seen the
>> same issue in other 1.1.x releases, or just seeing this now?
>>>>
>>>> -Taylor
>>>>
>>>>> On Feb 7, 2018, at 12:40 PM, Alexandre Vermeerbergen <
>> avermeerbergen@gmail.com> wrote:
>>>>>
>>>>> Hello All,
>>>>>
>>>>> I hate to be the one who always give bad news, but as a matter of
>>>>> facts, Storm 1.2.0 RC3 installation from binary artifacts (both
>>>>> apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
>>>>> default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
>>>>> ui.log)
>>>>>
>>>>> Here's for example what I get from apache-storm-1.2.0-src.tar.gz
>>>>> downloaded from
>>>>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz
>> :
>>>>>
>>>>> $ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
>>>>> -rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
>>>>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
>>>>> -rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
>>>>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
>>>>> -rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
>>>>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
>>>>>
>>>>> And here's what I see in ui.log:
>>>>>
>>>>> org.apache.storm.kafka.spout.KafkaSpout
>>>>> 2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
>>>>> [WARN] Exception message:Error: Could not find or load main class
>>>>>
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>>>>>
>>>>> org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
>>>>> find or load main class
>>>>>
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>>>>>
>>>>> at
>> org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
>>>>> at
>> org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at clojure.lang.RestFn.applyTo(RestFn.java:139)
>> ~[clojure-1.7.0.jar:?]
>>>>> at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
>>>>> at
>> org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>> at
>> org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
>>>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>>>
>>>>> Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
>>>>> storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
>>>>> solves the issue.
>>>>>
>>>>> However, binaries artifacts should be as clean as possible, isn't it ?
>>>>>
>>>>> Best regards,
>>>>> Alexandre Vermeerbergen
>>>>
>>
>>
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by Jungtaek Lim <ka...@gmail.com>.
Thanks for addressing md5/sha issue, Taylor. Verified src.tar.gz and
src.zip.
Alexandre, thanks again for thoughtful verification of release. It much
helped for us and I really appreciate it. Please keep up the good work.
I feel what Alexandre reported is a blocker since it leads strange error in
point of user side, worth to cancel current RC. Changing my vote to -1
(binding).
-Jungtaek Lim (HeartSaVioR)
2018년 2월 8일 (목) 오전 5:20, P. Taylor Goetz <pt...@gmail.com>님이 작성:
> Yes. It will be fixed. Thanks again for pointing it out.
>
> -Taylor
>
> > On Feb 7, 2018, at 2:57 PM, Alexandre Vermeerbergen <
> avermeerbergen@gmail.com> wrote:
> >
> > Hello Taylor,
> >
> > Yes same issue in Storm 1.1.0 : we have a production storm cluster
> > based on this release, but then we were using our own Kafka spout, no
> > we weren't impacted by this packaging issue.
> >
> > Could the extraneous files be cleaned up from 1.2.0-final?
> >
> > Best regards,
> > Alexandre Vermeerbergen
> >
> > 2018-02-07 19:18 GMT+01:00 P. Taylor Goetz <pt...@gmail.com>:
> >> Hi Alexandre,
> >>
> >> Thanks for the review. You’re right, the javadoc/source jars should not
> be there, though it looks like this has been the case for a long time and
> would have affected previous releases.
> >>
> >> It looks like the problem was introduced in 1.1.0. Have you seen the
> same issue in other 1.1.x releases, or just seeing this now?
> >>
> >> -Taylor
> >>
> >>> On Feb 7, 2018, at 12:40 PM, Alexandre Vermeerbergen <
> avermeerbergen@gmail.com> wrote:
> >>>
> >>> Hello All,
> >>>
> >>> I hate to be the one who always give bad news, but as a matter of
> >>> facts, Storm 1.2.0 RC3 installation from binary artifacts (both
> >>> apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
> >>> default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
> >>> ui.log)
> >>>
> >>> Here's for example what I get from apache-storm-1.2.0-src.tar.gz
> >>> downloaded from
> >>>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz
> :
> >>>
> >>> $ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
> >>> -rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
> >>> -rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
> >>> -rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
> >>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
> >>>
> >>> And here's what I see in ui.log:
> >>>
> >>> org.apache.storm.kafka.spout.KafkaSpout
> >>> 2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
> >>> [WARN] Exception message:Error: Could not find or load main class
> >>>
> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
> >>>
> >>> org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
> >>> find or load main class
> >>>
> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
> >>>
> >>> at
> org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
> >>> at
> org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at clojure.lang.RestFn.applyTo(RestFn.java:139)
> ~[clojure-1.7.0.jar:?]
> >>> at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
> >>> at
> org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>> at
> org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
> >>> ~[storm-core-1.2.0.jar:1.2.0]
> >>>
> >>> Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
> >>> storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
> >>> solves the issue.
> >>>
> >>> However, binaries artifacts should be as clean as possible, isn't it ?
> >>>
> >>> Best regards,
> >>> Alexandre Vermeerbergen
> >>
>
>
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Yes. It will be fixed. Thanks again for pointing it out.
-Taylor
> On Feb 7, 2018, at 2:57 PM, Alexandre Vermeerbergen <av...@gmail.com> wrote:
>
> Hello Taylor,
>
> Yes same issue in Storm 1.1.0 : we have a production storm cluster
> based on this release, but then we were using our own Kafka spout, no
> we weren't impacted by this packaging issue.
>
> Could the extraneous files be cleaned up from 1.2.0-final?
>
> Best regards,
> Alexandre Vermeerbergen
>
> 2018-02-07 19:18 GMT+01:00 P. Taylor Goetz <pt...@gmail.com>:
>> Hi Alexandre,
>>
>> Thanks for the review. You’re right, the javadoc/source jars should not be there, though it looks like this has been the case for a long time and would have affected previous releases.
>>
>> It looks like the problem was introduced in 1.1.0. Have you seen the same issue in other 1.1.x releases, or just seeing this now?
>>
>> -Taylor
>>
>>> On Feb 7, 2018, at 12:40 PM, Alexandre Vermeerbergen <av...@gmail.com> wrote:
>>>
>>> Hello All,
>>>
>>> I hate to be the one who always give bad news, but as a matter of
>>> facts, Storm 1.2.0 RC3 installation from binary artifacts (both
>>> apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
>>> default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
>>> ui.log)
>>>
>>> Here's for example what I get from apache-storm-1.2.0-src.tar.gz
>>> downloaded from
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz:
>>>
>>> $ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
>>> -rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
>>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
>>> -rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
>>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
>>> -rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
>>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
>>>
>>> And here's what I see in ui.log:
>>>
>>> org.apache.storm.kafka.spout.KafkaSpout
>>> 2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
>>> [WARN] Exception message:Error: Could not find or load main class
>>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>>>
>>> org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
>>> find or load main class
>>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>>>
>>> at org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
>>> at org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at clojure.lang.RestFn.applyTo(RestFn.java:139) ~[clojure-1.7.0.jar:?]
>>> at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
>>> at org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>> at org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
>>> ~[storm-core-1.2.0.jar:1.2.0]
>>>
>>> Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
>>> storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
>>> solves the issue.
>>>
>>> However, binaries artifacts should be as clean as possible, isn't it ?
>>>
>>> Best regards,
>>> Alexandre Vermeerbergen
>>
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by Alexandre Vermeerbergen <av...@gmail.com>.
Hello Taylor,
Yes same issue in Storm 1.1.0 : we have a production storm cluster
based on this release, but then we were using our own Kafka spout, no
we weren't impacted by this packaging issue.
Could the extraneous files be cleaned up from 1.2.0-final?
Best regards,
Alexandre Vermeerbergen
2018-02-07 19:18 GMT+01:00 P. Taylor Goetz <pt...@gmail.com>:
> Hi Alexandre,
>
> Thanks for the review. You’re right, the javadoc/source jars should not be there, though it looks like this has been the case for a long time and would have affected previous releases.
>
> It looks like the problem was introduced in 1.1.0. Have you seen the same issue in other 1.1.x releases, or just seeing this now?
>
> -Taylor
>
>> On Feb 7, 2018, at 12:40 PM, Alexandre Vermeerbergen <av...@gmail.com> wrote:
>>
>> Hello All,
>>
>> I hate to be the one who always give bad news, but as a matter of
>> facts, Storm 1.2.0 RC3 installation from binary artifacts (both
>> apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
>> default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
>> ui.log)
>>
>> Here's for example what I get from apache-storm-1.2.0-src.tar.gz
>> downloaded from
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz:
>>
>> $ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
>> -rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
>> -rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
>> -rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
>> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
>>
>> And here's what I see in ui.log:
>>
>> org.apache.storm.kafka.spout.KafkaSpout
>> 2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
>> [WARN] Exception message:Error: Could not find or load main class
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>>
>> org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
>> find or load main class
>> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>>
>> at org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
>> at org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at clojure.lang.RestFn.applyTo(RestFn.java:139) ~[clojure-1.7.0.jar:?]
>> at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
>> at org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
>> ~[storm-core-1.2.0.jar:1.2.0]
>> at org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
>> ~[storm-core-1.2.0.jar:1.2.0]
>>
>> Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
>> storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
>> solves the issue.
>>
>> However, binaries artifacts should be as clean as possible, isn't it ?
>>
>> Best regards,
>> Alexandre Vermeerbergen
>
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Hi Alexandre,
Thanks for the review. You’re right, the javadoc/source jars should not be there, though it looks like this has been the case for a long time and would have affected previous releases.
It looks like the problem was introduced in 1.1.0. Have you seen the same issue in other 1.1.x releases, or just seeing this now?
-Taylor
> On Feb 7, 2018, at 12:40 PM, Alexandre Vermeerbergen <av...@gmail.com> wrote:
>
> Hello All,
>
> I hate to be the one who always give bad news, but as a matter of
> facts, Storm 1.2.0 RC3 installation from binary artifacts (both
> apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
> default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
> ui.log)
>
> Here's for example what I get from apache-storm-1.2.0-src.tar.gz
> downloaded from
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz:
>
> $ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
> -rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
> -rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
> -rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
> apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
>
> And here's what I see in ui.log:
>
> org.apache.storm.kafka.spout.KafkaSpout
> 2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
> [WARN] Exception message:Error: Could not find or load main class
> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>
> org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
> find or load main class
> .usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
>
> at org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
> ~[storm-core-1.2.0.jar:1.2.0]
> at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
> at org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
> ~[storm-core-1.2.0.jar:1.2.0]
> at clojure.lang.RestFn.applyTo(RestFn.java:139) ~[clojure-1.7.0.jar:?]
> at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
> at org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
> ~[storm-core-1.2.0.jar:1.2.0]
> at org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
> ~[storm-core-1.2.0.jar:1.2.0]
>
> Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
> storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
> solves the issue.
>
> However, binaries artifacts should be as clean as possible, isn't it ?
>
> Best regards,
> Alexandre Vermeerbergen
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by Alexandre Vermeerbergen <av...@gmail.com>.
Hello All,
I hate to be the one who always give bad news, but as a matter of
facts, Storm 1.2.0 RC3 installation from binary artifacts (both
apache-storm-1.2.0-src.tar.gz and apache-storm-1.2.0.zip) leads to "by
default KO Kafka monitor" in Nimbus UI (which dirty exceptions in
ui.log)
Here's for example what I get from apache-storm-1.2.0-src.tar.gz
downloaded from
https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.2.0-src.tar.gz:
$ tar ztvf apache-storm-1.2.0.tar.gz apache-storm-1.2.0/toollib
-rwxrwxrwx ptgoetz/staff 16999 2018-02-06 21:22
apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-sources.jar
-rwxrwxrwx ptgoetz/staff 93461 2018-02-06 21:22
apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0-javadoc.jar
-rwxrwxrwx ptgoetz/staff 21591320 2018-02-06 21:22
apache-storm-1.2.0/toollib/storm-kafka-monitor-1.2.0.jar
And here's what I see in ui.log:
org.apache.storm.kafka.spout.KafkaSpout
2018-02-07 16:49:57.153 o.a.s.u.TopologySpoutLag qtp1997623038-18
[WARN] Exception message:Error: Could not find or load main class
.usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
org.apache.storm.utils.ShellUtils$ExitCodeException: Error: Could not
find or load main class
.usr.local.Storm.storm-stable.toollib.storm-kafka-monitor-1.2.0-javadoc.jar
at org.apache.storm.utils.ShellUtils.runCommand(ShellUtils.java:231)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.utils.ShellUtils.run(ShellUtils.java:161)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.utils.ShellUtils$ShellCommandExecutor.execute(ShellUtils.java:371)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:461)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.utils.ShellUtils.execCommand(ShellUtils.java:444)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.utils.TopologySpoutLag.getLagResultForKafka(TopologySpoutLag.java:163)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.utils.TopologySpoutLag.getLagResultForNewKafkaSpout(TopologySpoutLag.java:189)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.utils.TopologySpoutLag.lag(TopologySpoutLag.java:57)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.ui.core$topology_lag.invoke(core.clj:805)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.ui.core$fn__9586.invoke(core.clj:1165)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.compojure.core$make_route$fn__5979.invoke(core.clj:100)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.compojure.core$if_route$fn__5967.invoke(core.clj:46)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.compojure.core$if_method$fn__5960.invoke(core.clj:31)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.compojure.core$routing$fn__5985.invoke(core.clj:113)
~[storm-core-1.2.0.jar:1.2.0]
at clojure.core$some.invoke(core.clj:2570) ~[clojure-1.7.0.jar:?]
at org.apache.storm.shade.compojure.core$routing.doInvoke(core.clj:113)
~[storm-core-1.2.0.jar:1.2.0]
at clojure.lang.RestFn.applyTo(RestFn.java:139) ~[clojure-1.7.0.jar:?]
at clojure.core$apply.invoke(core.clj:632) ~[clojure-1.7.0.jar:?]
at org.apache.storm.shade.compojure.core$routes$fn__5989.invoke(core.clj:118)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.ring.middleware.cors$wrap_cors$fn__8894.invoke(cors.clj:149)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.ring.middleware.json$wrap_json_params$fn__8841.invoke(json.clj:56)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.ring.middleware.multipart_params$wrap_multipart_params$fn__6621.invoke(multipart_params.clj:118)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.shade.ring.middleware.reload$wrap_reload$fn__7904.invoke(reload.clj:22)
~[storm-core-1.2.0.jar:1.2.0]
at org.apache.storm.ui.helpers$requests_middleware$fn__6874.invoke(helpers.clj:52)
~[storm-core-1.2.0.jar:1.2.0]
Deleting the extraneous storm-kafka-monitor-1.2.0-sources.jar and
storm-kafka-monitor-1.2.0-javadoc.jar file, then restarting Nimbus
solves the issue.
However, binaries artifacts should be as clean as possible, isn't it ?
Best regards,
Alexandre Vermeerbergen
Re: [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Corrected. Thanks for pointing that out.
-Taylor
> On Feb 7, 2018, at 7:39 AM, Jungtaek Lim <ka...@gmail.com> wrote:
>
> Looks like missing md5/sha for apache-storm-1.2.0-src.tar.gz as well as
> apache-storm-1.2.0-src.zip.
>
> I'll continue verifying without that.
>
> 2018년 2월 7일 (수) 오전 6:01, P. Taylor Goetz <pt...@gmail.com>님이 작성:
>
>> This is a call to vote on releasing Apache Storm 1.2.0 (rc3)
>>
>> Full list of changes in this release:
>>
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/RELEASE_NOTES.html
>>
>> The tag/commit to be voted upon is v1.2.0:
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7be1308bfea0d71efac141888cdcfc9e708cfff5;hb=b20228de004dda52e414a9ade6e60ff0756df9d1
>>
>> The source archive being voted upon can be found here:
>>
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.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-1.2.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-1057
>>
>> Please vote on releasing this package as Apache Storm 1.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 1.2.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 1.2.0 (rc3)
Posted by Jungtaek Lim <ka...@gmail.com>.
Looks like missing md5/sha for apache-storm-1.2.0-src.tar.gz as well as
apache-storm-1.2.0-src.zip.
I'll continue verifying without that.
2018년 2월 7일 (수) 오전 6:01, P. Taylor Goetz <pt...@gmail.com>님이 작성:
> This is a call to vote on releasing Apache Storm 1.2.0 (rc3)
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v1.2.0:
>
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7be1308bfea0d71efac141888cdcfc9e708cfff5;hb=b20228de004dda52e414a9ade6e60ff0756df9d1
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.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-1.2.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-1057
>
> Please vote on releasing this package as Apache Storm 1.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 1.2.0
> [ ] 0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> -Taylor
>
[CANCELED] [VOTE] Release Apache Storm 1.2.0 (rc3)
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Canceling to include fix for STORM-2942.
-Taylor
> On Feb 6, 2018, at 4:01 PM, P. Taylor Goetz <pt...@gmail.com> wrote:
>
> This is a call to vote on releasing Apache Storm 1.2.0 (rc3)
>
> Full list of changes in this release:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v1.2.0:
>
> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=7be1308bfea0d71efac141888cdcfc9e708cfff5;hb=b20228de004dda52e414a9ade6e60ff0756df9d1
>
> The source archive being voted upon can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc3/apache-storm-1.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-1.2.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-1057
>
> Please vote on releasing this package as Apache Storm 1.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 1.2.0
> [ ] 0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> -Taylor