Re: Resource Aware Scheduler Kills Nimbus

pleasing values. > > Cheers, > > Alessio > > On 10 Feb 2018, at 21:42, Wuyang Zhang wrote: > > Hi Jerry, > > I am not familiar with the pull operation on the Storm website... Can you > do it when you get a chance? > > Also, I wonder how can I accurately specify

Re: Resource Aware Scheduler Kills Nimbus

: > Yup, an error in the documentation > > Feel free to submit a pull request to fix the documentation. > > Best, > > Jerry > > On Sat, Feb 10, 2018 at 1:42 PM, Wuyang Zhang > wrote: > >> Ok, I find it works by adding >> storm.scheduler: org.apache.storm.

Re: Resource Aware Scheduler Kills Nimbus

Ok, I find it works by adding storm.scheduler: org.apache.storm.scheduler.resource.ResourceAwareScheduler instead of adding storm.scheduler: “org.apache.storm.scheduler.resource.ResourceAwareScheduler” suggested by the website.. ᐧ On Sat, Feb 10, 2018 at 2:22 PM, Wuyang Zhang wrote: > W

Re: Resource Aware Scheduler Kills Nimbus

ry version of Storm 1.1.1 from http://www.apache.org/dyn/closer.lua/storm/apache-storm-1.1.1/apache-storm-1.1.1.tar.gz . ᐧ On Sat, Feb 10, 2018 at 2:02 PM, Wuyang Zhang wrote: > Hi Jerry, > > I just retry to use the resource aware scheduler in a single node with 4 > slots without any

Re: Resource Aware Scheduler Kills Nimbus

pts: "-Xmx%HEAP-MEM%m -Xms6000m -XX:+PrintGCDetails > -Xloggc:artifacts/gc.log -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps > -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=1M > -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=artifacts/heapdump" > > On Sa

Resource Aware Scheduler Kills Nimbus

Hi, I have the difficulty with the resource aware scheduler from the version 1.1.1. As suggested by the website, I add the following lines to storm.yaml: *storm.scheduler: “org.apache.storm.scheduler.resource.ResourceAwareScheduler”* * supervisor.memory.capacity.mb: 2048.0* * supervisor.cpu.cap

Re: Apache Storm High Messaging Delay When Passing 5MB Images

en 2 Storm workers. -roshan *From: *Wuyang Zhang *Reply-To: *"user@storm.apache.org" *Date: *Wednesday, January 31, 2018 at 7:55 PM *To: *"user@storm.apache.org" *Subject: *Re: Apache Storm High Messaging Delay When Passing 5MB Images Also, I would like to ask that when

Re: Apache Storm High Messaging Delay When Passing 5MB Images

nd rebuild to include timestamp in transport layer? Or measured via after emit() in Spout to starting of execute() in Bolt? If it's latter, it is including serialization/deserialization cost which we consider as expensive part. 2018년 2월 1일 (목) 오후 12:55, Wuyang Zhang 님이 작성: > Also, I would lik

Re: Apache Storm High Messaging Delay When Passing 5MB Images

after an interval. So to reduce the queue delay, I try to set the batch size to 1 and the flush interval to 1ms. Meanwhile, I modify the waiting strategy to yield. Any other suggestions to reduce messaging delay introduced inside Storm? ᐧ On Wed, Jan 31, 2018 at 10:20 PM, Wuyang Zhang wrote

Re: Apache Storm High Messaging Delay When Passing 5MB Images

ot easily seen, so the latency may > not be from messaging overhead. > > > > If it took 200 ms for each transfer that can be a thing to talk about. > Please let me know which is your case. > > > > Thanks, > > Jungtaek Lim (HeartSaVioR) > > > > 2018년 2월 1일 (

Apache Storm High Messaging Delay When Passing 5MB Images

I am playing with Apache Storm for a real-time image processing application which requires ultra low latency. In the topology definition, a single spout will emit raw images(5MB) in every 1s and a few bolts will process them. The processing latency of each bolt is acceptable and the overall computi