storm StormSubmitter.submitTopology问题

我在用本地模式调试的时候在bolt中能读取到数据
而使用StormSubmitter.submitTopology的时候
storm jar运行我的打包程序执行之后
我通过日志发现根本没进入bolt中去不知道为什么能帮我解答一下吗

zou79189747 · 发表于 2015-8-4 14:02:32

511  [main] INFO  backtype.storm.StormSubmitter - Generated ZooKeeper secret payload for MD5-digest: -6892927833486188545:-6197665121217628607
514  [main] INFO  backtype.storm.security.auth.AuthUtils - Got AutoCreds []
525  [main] WARN  org.apache.storm.curator.retry.ExponentialBackoffRetry - maxRetries too large (60000). Pinning to 29
525  [main] INFO  backtype.storm.utils.StormBoundedExponentialBackoffRetry - The baseSleepTimeMs [2000] the maxSleepTimeMs [5] the maxRetries [60000]
525  [main] WARN  backtype.storm.utils.StormBoundedExponentialBackoffRetry - Misconfiguration: the baseSleepTimeMs [2000] can't be greater than the maxSleepTimeMs [5].
583  [main] WARN  org.apache.storm.curator.retry.ExponentialBackoffRetry - maxRetries too large (60000). Pinning to 29
583  [main] INFO  backtype.storm.utils.StormBoundedExponentialBackoffRetry - The baseSleepTimeMs [2000] the maxSleepTimeMs [5] the maxRetries [60000]
583  [main] WARN  backtype.storm.utils.StormBoundedExponentialBackoffRetry - Misconfiguration: the baseSleepTimeMs [2000] can't be greater than the maxSleepTimeMs [5].
591  [main] WARN  org.apache.storm.curator.retry.ExponentialBackoffRetry - maxRetries too large (60000). Pinning to 29
591  [main] INFO  backtype.storm.utils.StormBoundedExponentialBackoffRetry - The baseSleepTimeMs [2000] the maxSleepTimeMs [5] the maxRetries [60000]
591  [main] WARN  backtype.storm.utils.StormBoundedExponentialBackoffRetry - Misconfiguration: the baseSleepTimeMs [2000] can't be greater than the maxSleepTimeMs [5].
608  [main] INFO  backtype.storm.StormSubmitter - Uploading topology jar f:\bolts.jar to assigned location: /hadoop/storm/nimbus/inbox/stormjar-08a17054-c94e-43f5-8917-a3da91359cdc.jar
706  [main] INFO  backtype.storm.StormSubmitter - Successfully uploaded topology jar to assigned location: /hadoop/storm/nimbus/inbox/stormjar-08a17054-c94e-43f5-8917-a3da91359cdc.jar
706  [main] INFO  backtype.storm.StormSubmitter - Submitting topology ZWL-topology22 in distributed mode with conf {"storm.zookeeper.topology.auth.scheme":"digest","nimbus.host":"100.0.26.132","storm.zookeeper.topology.auth.payload":"-6892927833486188545:-6197665121217628607","topology.workers":3,"storm.zookeeper.port":2181,"topology.debug":true,"nimbus.thrift.port":6627,"storm.zookeeper.servers":["100.0.26.131,100.0.26.132,100.0.26.133"]}
739  [main] INFO  backtype.storm.StormSubmitter - Finished submitting topology: ZWL-topology22

zou79189747 · 发表于 2015-8-4 14:03:10

上面是我的控制台信息

bioger_hit · 发表于 2015-8-4 14:32:02

zou79189747 发表于 2015-8-4 14:03
上面是我的控制台信息

从楼主提供信息看不出有没有金bolt，楼主从那看出来的。
上面只是给出了警告信息，然后告诉最大重试次数过多，睡眠时间等

zou79189747 · 发表于 2015-8-4 15:02:44

bioger_hit 发表于 2015-8-4 14:32
从楼主提供信息看不出有没有金bolt，楼主从那看出来的。
上面只是给出了警告信息，然后告诉最大重试次数 ...

哪些warn是可以忽略的吗应该不是上面异常吧
我在Storm UI中也能看到topology
我在bolt中记录了日志 private static int counter = 0;
@Override
public void execute(Tuple tuple, BasicOutputCollector collector) {
// TODO Auto-generated method stub
log.info("msg = "+tuple.getString(0)+" ----------- counter= "+(counter++));
System.out.println("msg = "+tuple.getString(0)+" ----------- counter= "+(counter++));
}
在日志文件中找不到日志信息

同样的代码用本地模式是正常的

bioger_hit · 发表于 2015-8-4 15:18:53

zou79189747 发表于 2015-8-4 15:02
哪些warn是可以忽略的吗应该不是上面异常吧
我在Storm UI中也能看到topology
我在bolt中记录了日志 ...

楼主本地模式和集群模式，相关的代码都修改了吗

zou79189747 · 发表于 2015-8-4 15:30:42

bioger_hit 发表于 2015-8-4 15:18
楼主本地模式和集群模式，相关的代码都修改了吗

这是我的topology代码我是初学者都是在网上找的
模式区分是根据有没有传递args来判断
if (args != null && args.length > 0) {
            conf.setNumWorkers(3);
            log.info("step in StormSubmitter");
            StormSubmitter.submitTopology(args[0], conf, builder.createTopology());
         } else {
            log.info("step in LocalCluster");
            LocalCluster cluster = new LocalCluster();
            cluster.submitTopology("Topo", conf, builder.createTopology());
            Utils.sleep(100000);
            cluster.killTopology("Topo");
            cluster.shutdown();
         }