[
https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021214#comment-14021214
]
Bob Tiernay commented on STORM-213:
-----------------------------------
Trace from {{0.9.2-incubating-SNAPSHOT}} that demonstrates that it takes ~30s
to startup. Its unclear what exactly is going on with all the retries, but it
would be nice to be able to disable this process.
{noformat}
2014-06-08 10:56:45,211 [main] INFO b.storm.zookeeper - Starting inprocess
zookeeper at port 2000 and dir
/var/folders/mf/03qtdmr131j0fstqrhncqmsr0000gp/T//11586a38-472a-4794-8a66-46fed033648e
2014-06-08 10:56:45,291 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:56:50,390 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:56:50,390 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:56:50,391 [main-EventThread] INFO b.storm.zookeeper - Zookeeper
state update: :connected:none
2014-06-08 10:56:50,407 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:56:55,484 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:56:55,484 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:56:55,511 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:00,589 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:00,589 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:00,590 [main-EventThread] INFO b.storm.zookeeper - Zookeeper
state update: :connected:none
2014-06-08 10:57:00,593 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:00,596 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:00,596 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:00,597 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:00,599 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:00,599 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:00,599 [main-EventThread] INFO b.storm.zookeeper - Zookeeper
state update: :connected:none
2014-06-08 10:57:00,602 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:05,679 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:05,679 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:05,697 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:05,699 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:05,700 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:05,700 [main-EventThread] INFO b.storm.zookeeper - Zookeeper
state update: :connected:none
2014-06-08 10:57:05,702 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:10,773 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:10,773 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:10,800 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:10,803 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:10,803 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:10,803 [main-EventThread] INFO b.storm.zookeeper - Zookeeper
state update: :connected:none
2014-06-08 10:57:10,805 [main] INFO o.a.c.f.i.CuratorFrameworkImpl - Starting
2014-06-08 10:57:10,807 [main-EventThread] INFO
o.a.c.f.s.ConnectionStateManager - State change: CONNECTED
2014-06-08 10:57:10,807 [ConnectionStateManager-0] WARN
o.a.c.f.s.ConnectionStateManager - There are no ConnectionStateListeners
registered.
2014-06-08 10:57:11,210 [main] INFO b.s.s.EvenScheduler - Available slots:
(["ad0687ee-df98-4d70-b1e2-7f798703fdc7" 1024]
["ad0687ee-df98-4d70-b1e2-7f798703fdc7" 1025]
["ad0687ee-df98-4d70-b1e2-7f798703fdc7" 1026]
["31cb29bf-d9ae-4ea5-9279-175fcce7c6de" 1027]
["31cb29bf-d9ae-4ea5-9279-175fcce7c6de" 1028]
["31cb29bf-d9ae-4ea5-9279-175fcce7c6de" 1029])
{noformat}
> Decouple In-Process ZooKeeper from LocalCluster
> -----------------------------------------------
>
> Key: STORM-213
> URL: https://issues.apache.org/jira/browse/STORM-213
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Reporter: Sharmarke Aden
> Labels: LocalCluster, ZooKeeper
>
> Currently there is no way to independently start ZooKeeper instance and have
> LocalCluster use this instance. It would be great if there was an option to
> tell LocalCluster to not start its own in-process ZooKeeper and instead rely
> on an already running In-Process instance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
