+1 I rebuilt from the tag, all of the unit tests passed.  I ran a small cluster 
and all of my simple tests passed there too.
Alexandre,
When the storm script is run it needs to read some config options.  Sadly we 
have not reproduced the same process in python so to do this is run a special 
command to read a config option.  This one is trying to read java.library.path 
so it can set up the command line properly.  I have no idea why it would be 
taking so long.  Usually it finishes very quickly.  If it is reproducible for 
you, you could take a jstack of it, there should only be one thread, and see 
where it is stuck.  My guess is that it is trying to read in a file, simply 
because that is all that this code really does.


- Bobby

On Monday, February 27, 2017, 7:13:28 AM CST, Alexandre Vermeerbergen 
<avermeerber...@gmail.com> wrote: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/
local/Storm/storm-stable/lib/log4j-slf4j-impl-2.8.jar:/usr/
local/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 <ptgo...@apache.org>:

> 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_
> plain;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_
> plain;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