Adding it to storm.yaml and restarting supervisors would be fine, and if you want to just disable backpressure on specific topology, submit jar with -c topology.backpressure.enable=false
2016년 6월 14일 (화) 오후 2:57, anshu shukla <[email protected]>님이 작성: > Thanks for replying . > > Can I put this entry in storm.yaml in place of default.yaml > > topology.backpressure.enable: false > > > On Tue, Jun 14, 2016 at 4:25 AM, Jungtaek Lim <[email protected]> wrote: > >> Hi anshu, >> >> You can set topology.backpressure.enable to false to disable backpressure. >> >> Hope this helps. >> >> Thanks, >> Jungtaek Lim (HeartSaVioR) >> >> 2016년 6월 14일 (화) 오전 5:32, anshu shukla <[email protected]>님이 작성: >> >>> Hey all, >>> >>> With backpressure enabled it is quite difficult to identify/estimate >>> the resource requirement for the given topology .Because every time you >>> add a new VM it may not be using full resources because your spout is >>> slowed down due to bottleneck . >>> >>> So Is there any idea of what watermark values we should use to disable >>> backpressure .So that I can be confident that I my spout is emitting at >>> expected rate . >>> >>> >>> -- >>> Thanks & Regards, >>> Anshu Shukla >>> >> > > > -- > Thanks & Regards, > Anshu Shukla >
