Tail information is not enough. It does not show error, just part of it. And maybe you have worker logs as well ?
On 1 November 2014 23:30, Sa Li <[email protected]> wrote: > I turn on the debug mode, > by > Config conf = new Config(); > conf.setDebug(true); > > This is what I get from log: > root@DO-mq-dev:/etc/storm/logs# ll > total 708 > drwxr-xr-x 2 root root 4096 Aug 11 13:40 ./ > drwxr-xr-x 10 root root 4096 Aug 11 13:33 ../ > -rw-r--r-- 1 root root 0 Aug 11 13:33 access.log > -rw-r--r-- 1 root root 0 Aug 11 13:33 metrics.log > -rw-r--r-- 1 root root 407392 Oct 28 16:08 nimbus.log > -rw-r--r-- 1 root root 270708 Oct 28 15:45 supervisor.log > -rw-r--r-- 1 root root 19965 Oct 28 16:02 ui.log > root@DO-mq-dev:/etc/storm/logs# tail nimbus.log > at > org.apache.thrift7.ProcessFunction.process(ProcessFunction.java:32) > ~[storm-core-0.9.2-incubating.jar:0.9.2-incubating] > at > org.apache.thrift7.TBaseProcessor.process(TBaseProcessor.java:34) > ~[storm-core-0.9.2-incubating.jar:0.9.2-incubating] > at > org.apache.thrift7.server.TNonblockingServer$FrameBuffer.invoke(TNonblockingServer.java:632) > ~[storm-core-0.9.2-incubating.jar:0.9.2-incubating] > at > org.apache.thrift7.server.THsHaServer$Invocation.run(THsHaServer.java:201) > [storm-core-0.9.2-incubating.jar:0.9.2-incubating] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > [na:1.7.0_55] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > [na:1.7.0_55] > at java.lang.Thread.run(Thread.java:744) [na:1.7.0_55] > 2014-10-28 16:08:38 o.a.z.ZooKeeper [INFO] Session: 0x14915a47cdde1f1 > closed > 2014-10-28 16:08:38 o.a.z.ClientCnxn [INFO] EventThread shut down > 2014-10-28 16:08:38 b.s.d.nimbus [INFO] Shut down master > > > This is not correct, since I submit many times topology to cluster on > 2014-10-31, seems didn't get recorded in log files. > > On Nov 1, 2014, at 4:26 PM, Jamil Shehzad <[email protected]> > wrote: > > Can you check log files kindly? > > > On Sun, Nov 2, 2014 at 4:05 AM, Sa Li <[email protected]> wrote: > >> any hints about why my topology does nothing in cluster mode. >> >> thanks >> >> >> On Oct 30, 2014, at 11:17 AM, Sa Li <[email protected]> wrote: >> >> Also I am testing the KafkaSpout throughput, running KafkaSpout on local >> mode, it consumes the data, (i retrieve the data and write into DB), but >> when I am checking the kafkaMoniter UI, it is the kafkaOffsetMonitering, I >> click the topic "topictest" which I generate the stream in kafkaproducer, >> but it unable to find active consumers, I feel like the kafka and storm >> have problem to integrate (maybe I am wrong). Or the conflict on zk server, >> since I believe the UIs get stats from ZK server. >> >> Thanks >> >> Alec >> >> >> >> >> On Thu, Oct 30, 2014 at 10:14 AM, Sa Li <[email protected]> wrote: >> >>> Hi, All >>> >>> I have been working Storm for a while, mostly I work on localmode, but >>> recently I want to test the thoughtput of KafkaSpout, when I submit the >>> topology to cluster, it didn't work while working fine in local mode. >>> >>> Test the cluster, I run the example typologies come with Storm package >>> in cluster, it is running but I can't see any throughput in storm UI (see >>> the attached screenshot), is that correct? if not, is it the problem of my >>> storm setup? >>> >>> I am setup the storm in a single server, using supervisord to run storm, >>> here is the storm.yaml >>> >>> ########### These MUST be filled in for a storm configuration >>> storm.zookeeper.servers: >>> - "10.100.70.128" >>> # - "server2" >>> # >>> >>> storm.zookeeper.port: 2181 >>> >>> nimbus.host: "10.100.70.128" >>> >>> storm.local.dir: "/app/storm" >>> >>> java.library.path: "/usr/lib/jvm/java-7-openjdk-amd64" >>> >>> supervisor.slots.ports: >>> >>> - 6700 >>> - 6701 >>> - 6702 >>> - 6703 >>> >>> drpc.servers: >>> - "10.100.70.128" >>> # - "server2" >>> >>> nimbus.childopts: "-Xms2048m" >>> ui.childopts: "-Xms1024m" >>> logviewer.childopts: "-Xmx512m" >>> supervisor.childopts: "-Xms1024m" >>> topology.trident.batch.emit.interval.millis: 100 >>> topology.message.timeout.secs: 300 >>> >>> >>> thanks >>> >>> Alec >>> >>> >> >> > >
