Sorry forgot to include another relevant bit of source: ➜ apache-storm-0.9.2-incubating ag "topology.enable.message.timeouts" conf/defaults.yaml 122:topology.enable.message.timeouts: true
storm-core/src/jvm/backtype/storm/Config.java 512: public static final String TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS = "topology.enable.message.timeouts"; ➜ apache-storm-0.9.2-incubating ag TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS storm-core/src/jvm/backtype/storm/Config.java 512: public static final String TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS = "topology.enable.message.timeouts"; 513: public static final Object TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS_SCHEMA = Boolean.class; On Thu, Nov 6, 2014 at 12:02 PM, Sean Allen <[email protected]> wrote: > Hi all, > > It would appear that "topology.enable.message.timeouts" settings isn't > being used anymore. > I discovered this when I used this following in my topology but has > timeouts after 30 seconds: > > config.put("topology.enable.message.timeouts", Boolean.FALSE) > > A search of the source revels it isn't being used. I assume this was in > error? If yes, I can open a ticket in jira. > > ➜ apache-storm-0.9.2-incubating ag "topology.enable.message.timeouts" > conf/defaults.yaml > 122:topology.enable.message.timeouts: true > > storm-core/src/jvm/backtype/storm/Config.java > 512: public static final String TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS = > "topology.enable.message.timeouts"; > > -Sean- > -- Ce n'est pas une signature
