I just found that source doesn't compile against JDK 7.
(Unfortunately I missed building source with JDK7. It was built with JDK8.)

I filed STORM-2388 <https://issues.apache.org/jira/browse/STORM-2388> and
submitted a PR <https://github.com/apache/storm/pull/1977> for this.

Since Storm 1.x should be guaranteed to be compatible with JDK 7, I think
it's blocker.
I'm changing my vote to -1 (binding).

We might need to have code-freeze period for 1.1.0 release.

- Jungtaek Lim (HeartSaVioR)

2017년 2월 28일 (화) 오전 8:33, Priyank Shah <[email protected]>님이 작성:

> +1(non-binding)
>
> - Verified signatures, md5s and shas for all files
> - Mvn clean install on source successsully
> - Started daemons and killed them successfully for both source and binary
> - Submitted WodCountTopology and FastWordCountTopology for both as well
> - Tried out different commands from UI like Deactivate, Activate,
> Rebalance and Kill
> - All of test runs were done on single node cluster on my local machine
> with each daemon running in its own jvm
>
>
> On 2/27/17, 12:26 PM, "Alexandre Vermeerbergen" <[email protected]>
> wrote:
>
>     Hello,
>
>     +1 (non-binding)
>
>     My first attempt to deploy our Supervision app (made of 10 topologies
> with
>     a Redis server for sharing memory) intto a small Storm 1.1.0rc2
> cluster (1
>     nimbus node, 2 supervisors, 3 zookeeper VMs) failed because operations
> on
>     Nimbus VM were taking too long.
>
>     I realized that this was because my Nimbus VM was a "m1.small"
> (provided by
>     OUTSCALE Europe 2 datacenter) and it was too slow. I have the
> impression
>     that this setup was OK with Storm 1.0.2, but I have no proofs. I
> re-did my
>     1.1.0rc2 with a m1.medium VM for Nimbus and everything works like a
> charm.
>
>     One detail: on our Kafka spouts, I got the following message instead
> of a
>     lag information:
>
>
>     Offset lags for kafka not supported for older versions. Please update
> kafka
>     spout to latest version.
>     Is there some documentation which provides the clear requirements to
> get
>     Kafka monitoring from Nimbus UI?
>     PS: I'm using Kafka Spout (not yet migrated to Kafka Client Spout with
>     Kafka 0.9.01 libraries.
>
>     Best regards,
>     Alexandre
>
>
>
>     2017-02-27 14:13 GMT+01:00 Alexandre Vermeerbergen <
> [email protected]
>     >:
>
>     > Hello,
>     >
>     > Tried with our supervision topologies on a small cluster (1 Nimbus
> VM, 3
>     > Zookeeper VMs, 2 Supervisor VMs).
>     >
>     > For the moment I have trouble with Nimbus & Nimbus UI startup time,
> the
>     > "bin/storm nimbus" starts the following process with runs for quite
> a long
>     > time (5 to 10 minutes) before the actual Nimbus process (which has a
> "java
>     > -server" pattern instead of "java -client" in ps aux list) is
> actually
>     > started:
>     >
>     > root     29178 81.0  0.9 1965584 18404 pts/0   Sl   13:04   0:00
>     > /usr/local/jdk/bin/java -client -Dstorm.options= -Dstorm.conf.file=
> -cp
>     > /usr/local/Storm/storm-stable/lib/servlet-api-2.5.jar:/usr/l
>     > ocal/Storm/storm-stable/lib/log4j-slf4j-impl-2.8.jar:/usr/lo
>     > cal/Storm/storm-stable/lib/minlog-1.3.0.jar:/usr/local/Storm
>     > /storm-stable/lib/storm-rename-hack-1.1.0.jar:/usr/local/
>     > Storm/storm-stable/lib/slf4j-api-1.7.21.jar:/usr/local/
>     > Storm/storm-stable/lib/disruptor-3.3.2.jar:/usr/local/Storm/
>     > storm-stable/lib/log4j-core-2.8.jar:/usr/local/Storm/storm-
>     > stable/lib/log4j-over-slf4j-1.6.6.jar:/usr/local/Storm/
>     > storm-stable/lib/reflectasm-1.10.1.jar:/usr/local/Storm/
>     > storm-stable/lib/ring-cors-0.1.5.jar:/usr/local/Storm/
>     > storm-stable/lib/clojure-1.7.0.jar:/usr/local/Storm/storm-
>     > stable/lib/kryo-3.0.3.jar:/usr/local/Storm/storm-stable/
>     > lib/asm-5.0.3.jar:/usr/local/Storm/storm-stable/lib/
>     > objenesis-2.1.jar:/usr/local/Storm/storm-stable/lib/log4j-
>     > api-2.8.jar:/usr/local/Storm/storm-stable/lib/storm-core-1.
>     > 1.0.jar:/usr/local/Storm/storm-stable/extlib/flux-
>     > wrappers-1.1.0.jar:/usr/local/Storm/storm-stable/extlib/
>     > flux-core-1.1.0.jar:/usr/local/Storm/storm-stable/conf
>     > org.apache.storm.command.config_value java.library.path
>     >
>     > I have no logs generated by this first process.
>     > Is there a way to turn on some logs to understand what takes so long?
>     >
>     > Best regards,
>     > Alexandre
>     >
>     >
>     > 2017-02-24 21:40 GMT+01:00 P. Taylor Goetz <[email protected]>:
>     >
>     >> This is a call to vote on releasing Apache Storm 1.1.0 (rc2)
>     >>
>     >> Full list of changes in this release:
>     >>
>     >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_p
>     >> lain;f=CHANGELOG.md;hb=17a2017fb644e353fb2a0f5bf50d400ee28036ba
>     >>
>     >> The tag/commit to be voted upon is v1.1.0:
>     >>
>     >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob;f
>     >> =CHANGELOG.md;h=0352f6d27dad1c88c24bb99fd894a211ea6c1e71;hb=
>     >> 7c8ea09e09160d36bba7e363ed53781816b46597
>     >>
>     >> The source archive being voted upon can be found here:
>     >>
>     >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.
>     >> 1.0-rc2/apache-storm-1.1.0-src.tar.gz
>     >>
>     >> Other release files, signatures and digests can be found here:
>     >>
>     >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.1.0-rc2/
>     >>
>     >> The release artifacts are signed with the following key:
>     >>
>     >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_p
>     >> lain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>     >>
>     >> The Nexus staging repository for this release is:
>     >>
>     >>
> https://repository.apache.org/content/repositories/orgapachestorm-1046
>     >>
>     >> Please vote on releasing this package as Apache Storm 1.1.0.
>     >>
>     >> When voting, please list the actions taken to verify the release.
>     >>
>     >> This vote will be open for at least 72 hours.
>     >>
>     >> [ ] +1 Release this package as Apache Storm 1.1.0
>     >> [ ]  0 No opinion
>     >> [ ] -1 Do not release this package because...
>     >>
>     >> Thanks to everyone who contributed to this release.
>     >>
>     >> -Taylor
>     >
>     >
>     >
>
>
>

Reply via email to