You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by researcher cs <pr...@gmail.com> on 2016/01/17 16:22:43 UTC
Acked still zero after update some properties
i submitted topology with storm and it's not my topology it's from project
submitted before so it should has no error !
i submitted topology with topology.stats.sample.rate: 1
topology.acker.executors: 1
topology has one worker = one supervisor but in the code ,
conf.setMaxSpoutPending(50000000) so
1- is there any othr properties i should change it as i'm using defualt
values ?
2- what are the condidtions or the calculatation you are using to make
properites more convient with the topology ?
like
#topology.executor.receive.buffer.size: 16384
# topology.executor.send.buffer.size: 16384
# topology.transfer.buffer.size: 32
# topology.receiver.buffer.size: 8
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
i found in the log file of worker this statements also
2016-01-19 17:03:00 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 17:03:04 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __metrics_tick, id: {}, [60]
2016-01-19 17:03:04 b.s.d.task [INFO] Emitting: __acker __metrics
[#<TaskInfo backtype.storm.metric.api.IMetricsConsumer$TaskInfo@e7ed40a>
[#<DataPoint [__ack-count = {}]> #<DataPoint [__sendqueue = {write_pos=-1,
read_pos=-1, capacity=1024, population=0}]> #<DataPoint [__receive =
{write_pos=8, read_pos=7, capacity=1024, population=1}]> #<DataPoint
[__process-latency = {}]> #<DataPoint [__transfer-count = {__metrics=0,
__system=0}]> #<DataPoint [__execute-latency = {}]> #<DataPoint
[__fail-count = {}]> #<DataPoint [__emit-count = {__metrics=1,
__system=0}]> #<DataPoint [__execute-count = {}]>]]
2016-01-19 17:03:04 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __metrics_tick, id: {}, [60]
2016-01-19 17:03:04 b.s.d.task [INFO] Emitting: __acker __metrics
[#<TaskInfo backtype.storm.metric.api.IMetricsConsumer$TaskInfo@2892e3f5>
[#<DataPoint [__ack-count = {}]> #<DataPoint [__sendqueue = {write_pos=-1,
read_pos=-1, capacity=1024, population=0}]> #<DataPoint [__receive =
{write_pos=8, read_pos=7, capacity=1024, population=1}]> #<DataPoint
[__process-latency = {}]> #<DataPoint [__transfer-count = {__metrics=0,
__system=0}]> #<DataPoint [__execute-latency = {}]> #<DataPoint
[__fail-count = {}]> #<DataPoint [__emit-count = {__metrics=1,
__system=0}]> #<DataPoint [__execute-count = {}]>]]
i searched for fixing it and found this post
https://groups.google.com/forum/#!topic/storm-user/paZ0Xnln4kE has same
problem as i thought, i increased maxClientCnxs to 1000 but didn't work
can someone help me to fix it ?
On Tue, Jan 19, 2016 at 6:42 PM, researcher cs <pr...@gmail.com>
wrote:
> i checked solts and it's OK but i enabled debug for my topology i used
> logviewer in port of spout in storm ui and got in
> , [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:29 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
> 2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
> source: __system:-1, stream: __tick, id: {}, [5]
>
> On Tue, Jan 19, 2016 at 6:09 PM, Kashyap Mhaisekar <ka...@gmail.com>
> wrote:
>
>> Show System Stats - has nothing to do with topology running or not
>> running. For your other question, please check if all "slots" are already
>> used by the first topology. If the first topology uses up all slots, then
>> other topologies may not work.
>>
>> On Tue, Jan 19, 2016 at 1:38 AM, researcher cs <prog.researcher@gmail.com
>> > wrote:
>>
>>> i searched for someone submitted wordcounttopology and this screenshot
>>> for it
>>>
>>> i'm confused i think it's like to my screenshot so he has a problem too
>>> ?
>>>
>>>
>>> On Tue, Jan 19, 2016 at 9:10 AM, researcher cs <
>>> prog.researcher@gmail.com> wrote:
>>>
>>>> something i want to ask about : when i submitted topology of wordcount
>>>> i got numbers without click on show system stats button
>>>>
>>>> But when i submitted another topology i got zeros in all columns
>>>> without click on show system stats button but when i clicked on it i got
>>>> numbers in Emitted cloumns only , so the basic problem with what ?
>>>>
>>>>
>>>>
>>>> On Tue, Jan 19, 2016 at 8:47 AM, researcher cs <
>>>> prog.researcher@gmail.com> wrote:
>>>>
>>>>> thanks for the link , i read this statements i guess problem here
>>>>> rigth ot i'm wrong
>>>>>
>>>>> When an acker task sees that an "ack val" has become 0, then it knows
>>>>> that the tuple tree is completed. Since tuple ids are random 64 bit
>>>>> numbers, the chances of an "ack val" accidentally becoming 0 is extremely
>>>>> small. If you work the math, at 10K acks per second, it will take
>>>>> 50,000,000 years until a mistake is made. And even then, it will only cause
>>>>> data loss if that tuple happens to fail in the topology.
>>>>>
>>>>> Now that you understand the reliability algorithm, let's go over all
>>>>> the failure cases and see how in each case Storm avoids data loss:
>>>>>
>>>>> - *A tuple isn't acked because the task died*: In this case the
>>>>> spout tuple ids at the root of the trees for the failed tuple will time out
>>>>> and be replayed.
>>>>> - *Acker task dies*: In this case all the spout tuples the acker
>>>>> was tracking will time out and be replayed.
>>>>> - *Spout task dies*: In this case the source that the spout talks
>>>>> to is responsible for replaying the messages. For example, queues like
>>>>> Kestrel and RabbitMQ will place all pending messages back on the queue when
>>>>> a client disconnects.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jan 19, 2016 at 4:23 AM, Annabel Melongo <
>>>>> melongo_annabel@yahoo.com> wrote:
>>>>>
>>>>>> Hopefully this link will provide some insights to your question:
>>>>>> Guaranteeing Message Processing
>>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>>>
>>>>>>
>>>>>> [image: image]
>>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Guaranteeing Message Processing
>>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>>> Storm guarantees that each message coming off a spout will be fully
>>>>>> processed.
>>>>>> View on storm.apache.org
>>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>>> Preview by Yahoo
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Monday, January 18, 2016 7:13 PM, researcher cs <
>>>>>> prog.researcher@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> i saw example in a site illustarted how can we submit a topology
>>>>>> like wordcount and results like what i got ..
>>>>>>
>>>>>> please what is the difference between transferred , Acked and emitted
>>>>>> ?
>>>>>>
>>>>>> On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <
>>>>>> prog.researcher@gmail.com> wrote:
>>>>>>
>>>>>> @john thanks for replying . so problem with configuration ! Is
>>>>>> zookeeper can be a problem ? Or I missed something in storm.yaml ? Because
>>>>>> word-count also has problem with me
>>>>>>
>>>>>>
>>>>>> On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
>>>>>>
>>>>>> Ah, okay, acking is happening, which is good, but no acking of the
>>>>>> spout tuples, which is puzzling. The spout tuples should either be acked or
>>>>>> they should fail. Unfortunately, not sure what's going on here.
>>>>>>
>>>>>> --John
>>>>>>
>>>>>> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <
>>>>>> prog.researcher@gmail.com> wrote:
>>>>>>
>>>>>> this is what i got with wordcount topology , but storm.yaml has
>>>>>> topology.stats.sample.rate: 1
>>>>>> topology.acker.executors: 1
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <
>>>>>> kashyap.m@gmail.com> wrote:
>>>>>>
>>>>>> Also, for checking if your topology is working or not, the default
>>>>>> values are more than sufficient. You dont need to change the buffer
>>>>>> settings for sure.
>>>>>>
>>>>>> Did you check with the default test topology on the word count on
>>>>>> your cluster? Does this work?
>>>>>>
>>>>>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Okay, this actually looks like the only tuples going through your
>>>>>> topology are tick tuples. To confirm, I recommend adding some logging
>>>>>> statements in the b-0 bolt to confirm if you are getting any non-tick
>>>>>> tuples in the execute method.
>>>>>>
>>>>>> --John
>>>>>>
>>>>>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>>>>>> prog.researcher@gmail.com> wrote:
>>>>>>
>>>>>> i submitted topology with storm and it's not my topology it's from
>>>>>> project submitted before so it should has no error !
>>>>>>
>>>>>> i submitted topology with topology.stats.sample.rate: 1
>>>>>> topology.acker.executors: 1
>>>>>> topology has one worker = one supervisor but in the code ,
>>>>>> conf.setMaxSpoutPending(50000000) so
>>>>>>
>>>>>> 1- is there any othr properties i should change it as i'm using
>>>>>> defualt values ?
>>>>>>
>>>>>> 2- what are the condidtions or the calculatation you are using to
>>>>>> make properites more convient with the topology ?
>>>>>>
>>>>>> like
>>>>>> #topology.executor.receive.buffer.size: 16384
>>>>>> # topology.executor.send.buffer.size: 16384
>>>>>> # topology.transfer.buffer.size: 32
>>>>>> # topology.receiver.buffer.size: 8
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
i checked solts and it's OK but i enabled debug for my topology i used
logviewer in port of spout in storm ui and got in
, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:25 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:29 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
2016-01-19 16:55:30 b.s.d.executor [INFO] Processing received message
source: __system:-1, stream: __tick, id: {}, [5]
On Tue, Jan 19, 2016 at 6:09 PM, Kashyap Mhaisekar <ka...@gmail.com>
wrote:
> Show System Stats - has nothing to do with topology running or not
> running. For your other question, please check if all "slots" are already
> used by the first topology. If the first topology uses up all slots, then
> other topologies may not work.
>
> On Tue, Jan 19, 2016 at 1:38 AM, researcher cs <pr...@gmail.com>
> wrote:
>
>> i searched for someone submitted wordcounttopology and this screenshot
>> for it
>>
>> i'm confused i think it's like to my screenshot so he has a problem too
>> ?
>>
>>
>> On Tue, Jan 19, 2016 at 9:10 AM, researcher cs <prog.researcher@gmail.com
>> > wrote:
>>
>>> something i want to ask about : when i submitted topology of wordcount i
>>> got numbers without click on show system stats button
>>>
>>> But when i submitted another topology i got zeros in all columns without
>>> click on show system stats button but when i clicked on it i got numbers in
>>> Emitted cloumns only , so the basic problem with what ?
>>>
>>>
>>>
>>> On Tue, Jan 19, 2016 at 8:47 AM, researcher cs <
>>> prog.researcher@gmail.com> wrote:
>>>
>>>> thanks for the link , i read this statements i guess problem here rigth
>>>> ot i'm wrong
>>>>
>>>> When an acker task sees that an "ack val" has become 0, then it knows
>>>> that the tuple tree is completed. Since tuple ids are random 64 bit
>>>> numbers, the chances of an "ack val" accidentally becoming 0 is extremely
>>>> small. If you work the math, at 10K acks per second, it will take
>>>> 50,000,000 years until a mistake is made. And even then, it will only cause
>>>> data loss if that tuple happens to fail in the topology.
>>>>
>>>> Now that you understand the reliability algorithm, let's go over all
>>>> the failure cases and see how in each case Storm avoids data loss:
>>>>
>>>> - *A tuple isn't acked because the task died*: In this case the
>>>> spout tuple ids at the root of the trees for the failed tuple will time out
>>>> and be replayed.
>>>> - *Acker task dies*: In this case all the spout tuples the acker
>>>> was tracking will time out and be replayed.
>>>> - *Spout task dies*: In this case the source that the spout talks
>>>> to is responsible for replaying the messages. For example, queues like
>>>> Kestrel and RabbitMQ will place all pending messages back on the queue when
>>>> a client disconnects.
>>>>
>>>>
>>>>
>>>> On Tue, Jan 19, 2016 at 4:23 AM, Annabel Melongo <
>>>> melongo_annabel@yahoo.com> wrote:
>>>>
>>>>> Hopefully this link will provide some insights to your question:
>>>>> Guaranteeing Message Processing
>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>>
>>>>>
>>>>> [image: image]
>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Guaranteeing Message Processing
>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>> Storm guarantees that each message coming off a spout will be fully
>>>>> processed.
>>>>> View on storm.apache.org
>>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>> Preview by Yahoo
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Monday, January 18, 2016 7:13 PM, researcher cs <
>>>>> prog.researcher@gmail.com> wrote:
>>>>>
>>>>>
>>>>> i saw example in a site illustarted how can we submit a topology like
>>>>> wordcount and results like what i got ..
>>>>>
>>>>> please what is the difference between transferred , Acked and emitted
>>>>> ?
>>>>>
>>>>> On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <
>>>>> prog.researcher@gmail.com> wrote:
>>>>>
>>>>> @john thanks for replying . so problem with configuration ! Is
>>>>> zookeeper can be a problem ? Or I missed something in storm.yaml ? Because
>>>>> word-count also has problem with me
>>>>>
>>>>>
>>>>> On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
>>>>>
>>>>> Ah, okay, acking is happening, which is good, but no acking of the
>>>>> spout tuples, which is puzzling. The spout tuples should either be acked or
>>>>> they should fail. Unfortunately, not sure what's going on here.
>>>>>
>>>>> --John
>>>>>
>>>>> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <
>>>>> prog.researcher@gmail.com> wrote:
>>>>>
>>>>> this is what i got with wordcount topology , but storm.yaml has
>>>>> topology.stats.sample.rate: 1
>>>>> topology.acker.executors: 1
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <
>>>>> kashyap.m@gmail.com> wrote:
>>>>>
>>>>> Also, for checking if your topology is working or not, the default
>>>>> values are more than sufficient. You dont need to change the buffer
>>>>> settings for sure.
>>>>>
>>>>> Did you check with the default test topology on the word count on your
>>>>> cluster? Does this work?
>>>>>
>>>>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Okay, this actually looks like the only tuples going through your
>>>>> topology are tick tuples. To confirm, I recommend adding some logging
>>>>> statements in the b-0 bolt to confirm if you are getting any non-tick
>>>>> tuples in the execute method.
>>>>>
>>>>> --John
>>>>>
>>>>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>>>>> prog.researcher@gmail.com> wrote:
>>>>>
>>>>> i submitted topology with storm and it's not my topology it's from
>>>>> project submitted before so it should has no error !
>>>>>
>>>>> i submitted topology with topology.stats.sample.rate: 1
>>>>> topology.acker.executors: 1
>>>>> topology has one worker = one supervisor but in the code ,
>>>>> conf.setMaxSpoutPending(50000000) so
>>>>>
>>>>> 1- is there any othr properties i should change it as i'm using
>>>>> defualt values ?
>>>>>
>>>>> 2- what are the condidtions or the calculatation you are using to
>>>>> make properites more convient with the topology ?
>>>>>
>>>>> like
>>>>> #topology.executor.receive.buffer.size: 16384
>>>>> # topology.executor.send.buffer.size: 16384
>>>>> # topology.transfer.buffer.size: 32
>>>>> # topology.receiver.buffer.size: 8
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Acked still zero after update some properties
Posted by Kashyap Mhaisekar <ka...@gmail.com>.
Show System Stats - has nothing to do with topology running or not running.
For your other question, please check if all "slots" are already used by
the first topology. If the first topology uses up all slots, then other
topologies may not work.
On Tue, Jan 19, 2016 at 1:38 AM, researcher cs <pr...@gmail.com>
wrote:
> i searched for someone submitted wordcounttopology and this screenshot for
> it
>
> i'm confused i think it's like to my screenshot so he has a problem too ?
>
>
> On Tue, Jan 19, 2016 at 9:10 AM, researcher cs <pr...@gmail.com>
> wrote:
>
>> something i want to ask about : when i submitted topology of wordcount i
>> got numbers without click on show system stats button
>>
>> But when i submitted another topology i got zeros in all columns without
>> click on show system stats button but when i clicked on it i got numbers in
>> Emitted cloumns only , so the basic problem with what ?
>>
>>
>>
>> On Tue, Jan 19, 2016 at 8:47 AM, researcher cs <prog.researcher@gmail.com
>> > wrote:
>>
>>> thanks for the link , i read this statements i guess problem here rigth
>>> ot i'm wrong
>>>
>>> When an acker task sees that an "ack val" has become 0, then it knows
>>> that the tuple tree is completed. Since tuple ids are random 64 bit
>>> numbers, the chances of an "ack val" accidentally becoming 0 is extremely
>>> small. If you work the math, at 10K acks per second, it will take
>>> 50,000,000 years until a mistake is made. And even then, it will only cause
>>> data loss if that tuple happens to fail in the topology.
>>>
>>> Now that you understand the reliability algorithm, let's go over all the
>>> failure cases and see how in each case Storm avoids data loss:
>>>
>>> - *A tuple isn't acked because the task died*: In this case the
>>> spout tuple ids at the root of the trees for the failed tuple will time out
>>> and be replayed.
>>> - *Acker task dies*: In this case all the spout tuples the acker was
>>> tracking will time out and be replayed.
>>> - *Spout task dies*: In this case the source that the spout talks to
>>> is responsible for replaying the messages. For example, queues like Kestrel
>>> and RabbitMQ will place all pending messages back on the queue when a
>>> client disconnects.
>>>
>>>
>>>
>>> On Tue, Jan 19, 2016 at 4:23 AM, Annabel Melongo <
>>> melongo_annabel@yahoo.com> wrote:
>>>
>>>> Hopefully this link will provide some insights to your question:
>>>> Guaranteeing Message Processing
>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>
>>>>
>>>> [image: image]
>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Guaranteeing Message Processing
>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>> Storm guarantees that each message coming off a spout will be fully
>>>> processed.
>>>> View on storm.apache.org
>>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>> Preview by Yahoo
>>>>
>>>>
>>>>
>>>>
>>>> On Monday, January 18, 2016 7:13 PM, researcher cs <
>>>> prog.researcher@gmail.com> wrote:
>>>>
>>>>
>>>> i saw example in a site illustarted how can we submit a topology like
>>>> wordcount and results like what i got ..
>>>>
>>>> please what is the difference between transferred , Acked and emitted ?
>>>>
>>>> On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <
>>>> prog.researcher@gmail.com> wrote:
>>>>
>>>> @john thanks for replying . so problem with configuration ! Is
>>>> zookeeper can be a problem ? Or I missed something in storm.yaml ? Because
>>>> word-count also has problem with me
>>>>
>>>>
>>>> On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
>>>>
>>>> Ah, okay, acking is happening, which is good, but no acking of the
>>>> spout tuples, which is puzzling. The spout tuples should either be acked or
>>>> they should fail. Unfortunately, not sure what's going on here.
>>>>
>>>> --John
>>>>
>>>> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <
>>>> prog.researcher@gmail.com> wrote:
>>>>
>>>> this is what i got with wordcount topology , but storm.yaml has
>>>> topology.stats.sample.rate: 1
>>>> topology.acker.executors: 1
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <kashyap.m@gmail.com
>>>> > wrote:
>>>>
>>>> Also, for checking if your topology is working or not, the default
>>>> values are more than sufficient. You dont need to change the buffer
>>>> settings for sure.
>>>>
>>>> Did you check with the default test topology on the word count on your
>>>> cluster? Does this work?
>>>>
>>>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com>
>>>> wrote:
>>>>
>>>> Okay, this actually looks like the only tuples going through your
>>>> topology are tick tuples. To confirm, I recommend adding some logging
>>>> statements in the b-0 bolt to confirm if you are getting any non-tick
>>>> tuples in the execute method.
>>>>
>>>> --John
>>>>
>>>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>>>> prog.researcher@gmail.com> wrote:
>>>>
>>>> i submitted topology with storm and it's not my topology it's from
>>>> project submitted before so it should has no error !
>>>>
>>>> i submitted topology with topology.stats.sample.rate: 1
>>>> topology.acker.executors: 1
>>>> topology has one worker = one supervisor but in the code ,
>>>> conf.setMaxSpoutPending(50000000) so
>>>>
>>>> 1- is there any othr properties i should change it as i'm using defualt
>>>> values ?
>>>>
>>>> 2- what are the condidtions or the calculatation you are using to make
>>>> properites more convient with the topology ?
>>>>
>>>> like
>>>> #topology.executor.receive.buffer.size: 16384
>>>> # topology.executor.send.buffer.size: 16384
>>>> # topology.transfer.buffer.size: 32
>>>> # topology.receiver.buffer.size: 8
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
i searched for someone submitted wordcounttopology and this screenshot for
it
i'm confused i think it's like to my screenshot so he has a problem too ?
On Tue, Jan 19, 2016 at 9:10 AM, researcher cs <pr...@gmail.com>
wrote:
> something i want to ask about : when i submitted topology of wordcount i
> got numbers without click on show system stats button
>
> But when i submitted another topology i got zeros in all columns without
> click on show system stats button but when i clicked on it i got numbers in
> Emitted cloumns only , so the basic problem with what ?
>
>
>
> On Tue, Jan 19, 2016 at 8:47 AM, researcher cs <pr...@gmail.com>
> wrote:
>
>> thanks for the link , i read this statements i guess problem here rigth
>> ot i'm wrong
>>
>> When an acker task sees that an "ack val" has become 0, then it knows
>> that the tuple tree is completed. Since tuple ids are random 64 bit
>> numbers, the chances of an "ack val" accidentally becoming 0 is extremely
>> small. If you work the math, at 10K acks per second, it will take
>> 50,000,000 years until a mistake is made. And even then, it will only cause
>> data loss if that tuple happens to fail in the topology.
>>
>> Now that you understand the reliability algorithm, let's go over all the
>> failure cases and see how in each case Storm avoids data loss:
>>
>> - *A tuple isn't acked because the task died*: In this case the spout
>> tuple ids at the root of the trees for the failed tuple will time out and
>> be replayed.
>> - *Acker task dies*: In this case all the spout tuples the acker was
>> tracking will time out and be replayed.
>> - *Spout task dies*: In this case the source that the spout talks to
>> is responsible for replaying the messages. For example, queues like Kestrel
>> and RabbitMQ will place all pending messages back on the queue when a
>> client disconnects.
>>
>>
>>
>> On Tue, Jan 19, 2016 at 4:23 AM, Annabel Melongo <
>> melongo_annabel@yahoo.com> wrote:
>>
>>> Hopefully this link will provide some insights to your question:
>>> Guaranteeing Message Processing
>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>
>>>
>>> [image: image]
>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>>
>>>
>>>
>>>
>>>
>>> Guaranteeing Message Processing
>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>> Storm guarantees that each message coming off a spout will be fully
>>> processed.
>>> View on storm.apache.org
>>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>> Preview by Yahoo
>>>
>>>
>>>
>>>
>>> On Monday, January 18, 2016 7:13 PM, researcher cs <
>>> prog.researcher@gmail.com> wrote:
>>>
>>>
>>> i saw example in a site illustarted how can we submit a topology like
>>> wordcount and results like what i got ..
>>>
>>> please what is the difference between transferred , Acked and emitted ?
>>>
>>> On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <
>>> prog.researcher@gmail.com> wrote:
>>>
>>> @john thanks for replying . so problem with configuration ! Is zookeeper
>>> can be a problem ? Or I missed something in storm.yaml ? Because
>>> word-count also has problem with me
>>>
>>>
>>> On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
>>>
>>> Ah, okay, acking is happening, which is good, but no acking of the spout
>>> tuples, which is puzzling. The spout tuples should either be acked or they
>>> should fail. Unfortunately, not sure what's going on here.
>>>
>>> --John
>>>
>>> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <
>>> prog.researcher@gmail.com> wrote:
>>>
>>> this is what i got with wordcount topology , but storm.yaml has
>>> topology.stats.sample.rate: 1
>>> topology.acker.executors: 1
>>>
>>>
>>>
>>>
>>> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <ka...@gmail.com>
>>> wrote:
>>>
>>> Also, for checking if your topology is working or not, the default
>>> values are more than sufficient. You dont need to change the buffer
>>> settings for sure.
>>>
>>> Did you check with the default test topology on the word count on your
>>> cluster? Does this work?
>>>
>>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com>
>>> wrote:
>>>
>>> Okay, this actually looks like the only tuples going through your
>>> topology are tick tuples. To confirm, I recommend adding some logging
>>> statements in the b-0 bolt to confirm if you are getting any non-tick
>>> tuples in the execute method.
>>>
>>> --John
>>>
>>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>>> prog.researcher@gmail.com> wrote:
>>>
>>> i submitted topology with storm and it's not my topology it's from
>>> project submitted before so it should has no error !
>>>
>>> i submitted topology with topology.stats.sample.rate: 1
>>> topology.acker.executors: 1
>>> topology has one worker = one supervisor but in the code ,
>>> conf.setMaxSpoutPending(50000000) so
>>>
>>> 1- is there any othr properties i should change it as i'm using defualt
>>> values ?
>>>
>>> 2- what are the condidtions or the calculatation you are using to make
>>> properites more convient with the topology ?
>>>
>>> like
>>> #topology.executor.receive.buffer.size: 16384
>>> # topology.executor.send.buffer.size: 16384
>>> # topology.transfer.buffer.size: 32
>>> # topology.receiver.buffer.size: 8
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
something i want to ask about : when i submitted topology of wordcount i
got numbers without click on show system stats button
But when i submitted another topology i got zeros in all columns without
click on show system stats button but when i clicked on it i got numbers in
Emitted cloumns only , so the basic problem with what ?
On Tue, Jan 19, 2016 at 8:47 AM, researcher cs <pr...@gmail.com>
wrote:
> thanks for the link , i read this statements i guess problem here rigth ot
> i'm wrong
>
> When an acker task sees that an "ack val" has become 0, then it knows that
> the tuple tree is completed. Since tuple ids are random 64 bit numbers, the
> chances of an "ack val" accidentally becoming 0 is extremely small. If you
> work the math, at 10K acks per second, it will take 50,000,000 years until
> a mistake is made. And even then, it will only cause data loss if that
> tuple happens to fail in the topology.
>
> Now that you understand the reliability algorithm, let's go over all the
> failure cases and see how in each case Storm avoids data loss:
>
> - *A tuple isn't acked because the task died*: In this case the spout
> tuple ids at the root of the trees for the failed tuple will time out and
> be replayed.
> - *Acker task dies*: In this case all the spout tuples the acker was
> tracking will time out and be replayed.
> - *Spout task dies*: In this case the source that the spout talks to
> is responsible for replaying the messages. For example, queues like Kestrel
> and RabbitMQ will place all pending messages back on the queue when a
> client disconnects.
>
>
>
> On Tue, Jan 19, 2016 at 4:23 AM, Annabel Melongo <
> melongo_annabel@yahoo.com> wrote:
>
>> Hopefully this link will provide some insights to your question:
>> Guaranteeing Message Processing
>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>
>>
>> [image: image]
>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>>
>>
>>
>>
>>
>> Guaranteeing Message Processing
>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>> Storm guarantees that each message coming off a spout will be fully
>> processed.
>> View on storm.apache.org
>> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>> Preview by Yahoo
>>
>>
>>
>>
>> On Monday, January 18, 2016 7:13 PM, researcher cs <
>> prog.researcher@gmail.com> wrote:
>>
>>
>> i saw example in a site illustarted how can we submit a topology like
>> wordcount and results like what i got ..
>>
>> please what is the difference between transferred , Acked and emitted ?
>>
>> On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <prog.researcher@gmail.com
>> > wrote:
>>
>> @john thanks for replying . so problem with configuration ! Is zookeeper
>> can be a problem ? Or I missed something in storm.yaml ? Because
>> word-count also has problem with me
>>
>>
>> On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
>>
>> Ah, okay, acking is happening, which is good, but no acking of the spout
>> tuples, which is puzzling. The spout tuples should either be acked or they
>> should fail. Unfortunately, not sure what's going on here.
>>
>> --John
>>
>> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <
>> prog.researcher@gmail.com> wrote:
>>
>> this is what i got with wordcount topology , but storm.yaml has
>> topology.stats.sample.rate: 1
>> topology.acker.executors: 1
>>
>>
>>
>>
>> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <ka...@gmail.com>
>> wrote:
>>
>> Also, for checking if your topology is working or not, the default values
>> are more than sufficient. You dont need to change the buffer settings for
>> sure.
>>
>> Did you check with the default test topology on the word count on your
>> cluster? Does this work?
>>
>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com> wrote:
>>
>> Okay, this actually looks like the only tuples going through your
>> topology are tick tuples. To confirm, I recommend adding some logging
>> statements in the b-0 bolt to confirm if you are getting any non-tick
>> tuples in the execute method.
>>
>> --John
>>
>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>> prog.researcher@gmail.com> wrote:
>>
>> i submitted topology with storm and it's not my topology it's from
>> project submitted before so it should has no error !
>>
>> i submitted topology with topology.stats.sample.rate: 1
>> topology.acker.executors: 1
>> topology has one worker = one supervisor but in the code ,
>> conf.setMaxSpoutPending(50000000) so
>>
>> 1- is there any othr properties i should change it as i'm using defualt
>> values ?
>>
>> 2- what are the condidtions or the calculatation you are using to make
>> properites more convient with the topology ?
>>
>> like
>> #topology.executor.receive.buffer.size: 16384
>> # topology.executor.send.buffer.size: 16384
>> # topology.transfer.buffer.size: 32
>> # topology.receiver.buffer.size: 8
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
thanks for the link , i read this statements i guess problem here rigth ot
i'm wrong
When an acker task sees that an "ack val" has become 0, then it knows that
the tuple tree is completed. Since tuple ids are random 64 bit numbers, the
chances of an "ack val" accidentally becoming 0 is extremely small. If you
work the math, at 10K acks per second, it will take 50,000,000 years until
a mistake is made. And even then, it will only cause data loss if that
tuple happens to fail in the topology.
Now that you understand the reliability algorithm, let's go over all the
failure cases and see how in each case Storm avoids data loss:
- *A tuple isn't acked because the task died*: In this case the spout
tuple ids at the root of the trees for the failed tuple will time out and
be replayed.
- *Acker task dies*: In this case all the spout tuples the acker was
tracking will time out and be replayed.
- *Spout task dies*: In this case the source that the spout talks to is
responsible for replaying the messages. For example, queues like Kestrel
and RabbitMQ will place all pending messages back on the queue when a
client disconnects.
On Tue, Jan 19, 2016 at 4:23 AM, Annabel Melongo <me...@yahoo.com>
wrote:
> Hopefully this link will provide some insights to your question:
> Guaranteeing Message Processing
> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>
>
> [image: image]
> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
>
>
>
>
>
> Guaranteeing Message Processing
> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
> Storm guarantees that each message coming off a spout will be fully
> processed.
> View on storm.apache.org
> <http://storm.apache.org/documentation/Guaranteeing-message-processing.html>
> Preview by Yahoo
>
>
>
>
> On Monday, January 18, 2016 7:13 PM, researcher cs <
> prog.researcher@gmail.com> wrote:
>
>
> i saw example in a site illustarted how can we submit a topology like
> wordcount and results like what i got ..
>
> please what is the difference between transferred , Acked and emitted ?
>
> On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <pr...@gmail.com>
> wrote:
>
> @john thanks for replying . so problem with configuration ! Is zookeeper
> can be a problem ? Or I missed something in storm.yaml ? Because
> word-count also has problem with me
>
>
> On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
>
> Ah, okay, acking is happening, which is good, but no acking of the spout
> tuples, which is puzzling. The spout tuples should either be acked or they
> should fail. Unfortunately, not sure what's going on here.
>
> --John
>
> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <prog.researcher@gmail.com
> > wrote:
>
> this is what i got with wordcount topology , but storm.yaml has
> topology.stats.sample.rate: 1
> topology.acker.executors: 1
>
>
>
>
> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <ka...@gmail.com>
> wrote:
>
> Also, for checking if your topology is working or not, the default values
> are more than sufficient. You dont need to change the buffer settings for
> sure.
>
> Did you check with the default test topology on the word count on your
> cluster? Does this work?
>
> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com> wrote:
>
> Okay, this actually looks like the only tuples going through your topology
> are tick tuples. To confirm, I recommend adding some logging statements in
> the b-0 bolt to confirm if you are getting any non-tick tuples in the
> execute method.
>
> --John
>
> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <prog.researcher@gmail.com
> > wrote:
>
> i submitted topology with storm and it's not my topology it's from project
> submitted before so it should has no error !
>
> i submitted topology with topology.stats.sample.rate: 1
> topology.acker.executors: 1
> topology has one worker = one supervisor but in the code ,
> conf.setMaxSpoutPending(50000000) so
>
> 1- is there any othr properties i should change it as i'm using defualt
> values ?
>
> 2- what are the condidtions or the calculatation you are using to make
> properites more convient with the topology ?
>
> like
> #topology.executor.receive.buffer.size: 16384
> # topology.executor.send.buffer.size: 16384
> # topology.transfer.buffer.size: 32
> # topology.receiver.buffer.size: 8
>
>
>
>
>
>
>
>
>
>
>
>
Re: Acked still zero after update some properties
Posted by Annabel Melongo <me...@yahoo.com>.
Hopefully this link will provide some insights to your question: Guaranteeing Message Processing
| |
| | | | | | | |
| Guaranteeing Message ProcessingStorm guarantees that each message coming off a spout will be fully processed. |
| |
| View on storm.apache.org | Preview by Yahoo |
| |
| |
On Monday, January 18, 2016 7:13 PM, researcher cs <pr...@gmail.com> wrote:
i saw example in a site illustarted how can we submit a topology like wordcount and results like what i got ..
please what is the difference between transferred , Acked and emitted ?
On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <pr...@gmail.com> wrote:
@john thanks for replying . so problem with configuration ! Is zookeeper can be a problem ? Or I missed something in storm.yaml ? Because word-count also has problem with me
On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
Ah, okay, acking is happening, which is good, but no acking of the spout tuples, which is puzzling. The spout tuples should either be acked or they should fail. Unfortunately, not sure what's going on here.
--John
On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <pr...@gmail.com> wrote:
this is what i got with wordcount topology , but storm.yaml has topology.stats.sample.rate: 1
topology.acker.executors: 1
On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <ka...@gmail.com> wrote:
Also, for checking if your topology is working or not, the default values are more than sufficient. You dont need to change the buffer settings for sure.
Did you check with the default test topology on the word count on your cluster? Does this work?
On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com> wrote:
Okay, this actually looks like the only tuples going through your topology are tick tuples. To confirm, I recommend adding some logging statements in the b-0 bolt to confirm if you are getting any non-tick tuples in the execute method.
--John
On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <pr...@gmail.com> wrote:
i submitted topology with storm and it's not my topology it's from project submitted before so it should has no error !
i submitted topology with topology.stats.sample.rate: 1
topology.acker.executors: 1
topology has one worker = one supervisor but in the code ,
conf.setMaxSpoutPending(50000000) so
1- is there any othr properties i should change it as i'm using defualt values ?
2- what are the condidtions or the calculatation you are using to make properites more convient with the topology ?
like
#topology.executor.receive.buffer.size: 16384
# topology.executor.send.buffer.size: 16384
# topology.transfer.buffer.size: 32
# topology.receiver.buffer.size: 8
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
i saw example in a site illustarted how can we submit a topology like
wordcount and results like what i got ..
please what is the difference between transferred , Acked and emitted ?
On Tue, Jan 19, 2016 at 1:12 AM, researcher cs <pr...@gmail.com>
wrote:
> @john thanks for replying . so problem with configuration ! Is zookeeper
> can be a problem ? Or I missed something in storm.yaml ? Because
> word-count also has problem with me
>
>
> On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
>
>> Ah, okay, acking is happening, which is good, but no acking of the spout
>> tuples, which is puzzling. The spout tuples should either be acked or they
>> should fail. Unfortunately, not sure what's going on here.
>>
>> --John
>>
>> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <
>> prog.researcher@gmail.com> wrote:
>>
>>> this is what i got with wordcount topology , but storm.yaml has
>>> topology.stats.sample.rate: 1
>>> topology.acker.executors: 1
>>>
>>>
>>>
>>>
>>> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <ka...@gmail.com>
>>> wrote:
>>>
>>>> Also, for checking if your topology is working or not, the default
>>>> values are more than sufficient. You dont need to change the buffer
>>>> settings for sure.
>>>>
>>>> Did you check with the default test topology on the word count on your
>>>> cluster? Does this work?
>>>>
>>>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com>
>>>> wrote:
>>>>
>>>>> Okay, this actually looks like the only tuples going through your
>>>>> topology are tick tuples. To confirm, I recommend adding some logging
>>>>> statements in the b-0 bolt to confirm if you are getting any non-tick
>>>>> tuples in the execute method.
>>>>>
>>>>> --John
>>>>>
>>>>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>>>>> prog.researcher@gmail.com> wrote:
>>>>>
>>>>>> i submitted topology with storm and it's not my topology it's from
>>>>>> project submitted before so it should has no error !
>>>>>>
>>>>>> i submitted topology with topology.stats.sample.rate: 1
>>>>>> topology.acker.executors: 1
>>>>>> topology has one worker = one supervisor but in the code ,
>>>>>> conf.setMaxSpoutPending(50000000) so
>>>>>>
>>>>>> 1- is there any othr properties i should change it as i'm using
>>>>>> defualt values ?
>>>>>>
>>>>>> 2- what are the condidtions or the calculatation you are using to
>>>>>> make properites more convient with the topology ?
>>>>>>
>>>>>> like
>>>>>> #topology.executor.receive.buffer.size: 16384
>>>>>> # topology.executor.send.buffer.size: 16384
>>>>>> # topology.transfer.buffer.size: 32
>>>>>> # topology.receiver.buffer.size: 8
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
@john thanks for replying . so problem with configuration ! Is zookeeper
can be a problem ? Or I missed something in storm.yaml ? Because
word-count also has problem with me
On Monday, January 18, 2016, John Yost <ho...@gmail.com> wrote:
> Ah, okay, acking is happening, which is good, but no acking of the spout
> tuples, which is puzzling. The spout tuples should either be acked or they
> should fail. Unfortunately, not sure what's going on here.
>
> --John
>
> On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <prog.researcher@gmail.com
> <javascript:_e(%7B%7D,'cvml','prog.researcher@gmail.com');>> wrote:
>
>> this is what i got with wordcount topology , but storm.yaml has
>> topology.stats.sample.rate: 1
>> topology.acker.executors: 1
>>
>>
>>
>>
>> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <kashyap.m@gmail.com
>> <javascript:_e(%7B%7D,'cvml','kashyap.m@gmail.com');>> wrote:
>>
>>> Also, for checking if your topology is working or not, the default
>>> values are more than sufficient. You dont need to change the buffer
>>> settings for sure.
>>>
>>> Did you check with the default test topology on the word count on your
>>> cluster? Does this work?
>>>
>>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <hokiegeek2@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','hokiegeek2@gmail.com');>> wrote:
>>>
>>>> Okay, this actually looks like the only tuples going through your
>>>> topology are tick tuples. To confirm, I recommend adding some logging
>>>> statements in the b-0 bolt to confirm if you are getting any non-tick
>>>> tuples in the execute method.
>>>>
>>>> --John
>>>>
>>>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>>>> prog.researcher@gmail.com
>>>> <javascript:_e(%7B%7D,'cvml','prog.researcher@gmail.com');>> wrote:
>>>>
>>>>> i submitted topology with storm and it's not my topology it's from
>>>>> project submitted before so it should has no error !
>>>>>
>>>>> i submitted topology with topology.stats.sample.rate: 1
>>>>> topology.acker.executors: 1
>>>>> topology has one worker = one supervisor but in the code ,
>>>>> conf.setMaxSpoutPending(50000000) so
>>>>>
>>>>> 1- is there any othr properties i should change it as i'm using
>>>>> defualt values ?
>>>>>
>>>>> 2- what are the condidtions or the calculatation you are using to
>>>>> make properites more convient with the topology ?
>>>>>
>>>>> like
>>>>> #topology.executor.receive.buffer.size: 16384
>>>>> # topology.executor.send.buffer.size: 16384
>>>>> # topology.transfer.buffer.size: 32
>>>>> # topology.receiver.buffer.size: 8
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Acked still zero after update some properties
Posted by John Yost <ho...@gmail.com>.
Ah, okay, acking is happening, which is good, but no acking of the spout
tuples, which is puzzling. The spout tuples should either be acked or they
should fail. Unfortunately, not sure what's going on here.
--John
On Sun, Jan 17, 2016 at 12:44 PM, researcher cs <pr...@gmail.com>
wrote:
> this is what i got with wordcount topology , but storm.yaml has
> topology.stats.sample.rate: 1
> topology.acker.executors: 1
>
>
>
>
> On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <ka...@gmail.com>
> wrote:
>
>> Also, for checking if your topology is working or not, the default values
>> are more than sufficient. You dont need to change the buffer settings for
>> sure.
>>
>> Did you check with the default test topology on the word count on your
>> cluster? Does this work?
>>
>> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com> wrote:
>>
>>> Okay, this actually looks like the only tuples going through your
>>> topology are tick tuples. To confirm, I recommend adding some logging
>>> statements in the b-0 bolt to confirm if you are getting any non-tick
>>> tuples in the execute method.
>>>
>>> --John
>>>
>>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>>> prog.researcher@gmail.com> wrote:
>>>
>>>> i submitted topology with storm and it's not my topology it's from
>>>> project submitted before so it should has no error !
>>>>
>>>> i submitted topology with topology.stats.sample.rate: 1
>>>> topology.acker.executors: 1
>>>> topology has one worker = one supervisor but in the code ,
>>>> conf.setMaxSpoutPending(50000000) so
>>>>
>>>> 1- is there any othr properties i should change it as i'm using defualt
>>>> values ?
>>>>
>>>> 2- what are the condidtions or the calculatation you are using to make
>>>> properites more convient with the topology ?
>>>>
>>>> like
>>>> #topology.executor.receive.buffer.size: 16384
>>>> # topology.executor.send.buffer.size: 16384
>>>> # topology.transfer.buffer.size: 32
>>>> # topology.receiver.buffer.size: 8
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
Re: Acked still zero after update some properties
Posted by researcher cs <pr...@gmail.com>.
this is what i got with wordcount topology , but storm.yaml has
topology.stats.sample.rate: 1
topology.acker.executors: 1
On Sun, Jan 17, 2016 at 6:29 PM, Kashyap Mhaisekar <ka...@gmail.com>
wrote:
> Also, for checking if your topology is working or not, the default values
> are more than sufficient. You dont need to change the buffer settings for
> sure.
>
> Did you check with the default test topology on the word count on your
> cluster? Does this work?
>
> On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com> wrote:
>
>> Okay, this actually looks like the only tuples going through your
>> topology are tick tuples. To confirm, I recommend adding some logging
>> statements in the b-0 bolt to confirm if you are getting any non-tick
>> tuples in the execute method.
>>
>> --John
>>
>> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <
>> prog.researcher@gmail.com> wrote:
>>
>>> i submitted topology with storm and it's not my topology it's from
>>> project submitted before so it should has no error !
>>>
>>> i submitted topology with topology.stats.sample.rate: 1
>>> topology.acker.executors: 1
>>> topology has one worker = one supervisor but in the code ,
>>> conf.setMaxSpoutPending(50000000) so
>>>
>>> 1- is there any othr properties i should change it as i'm using defualt
>>> values ?
>>>
>>> 2- what are the condidtions or the calculatation you are using to make
>>> properites more convient with the topology ?
>>>
>>> like
>>> #topology.executor.receive.buffer.size: 16384
>>> # topology.executor.send.buffer.size: 16384
>>> # topology.transfer.buffer.size: 32
>>> # topology.receiver.buffer.size: 8
>>>
>>>
>>>
>>>
>>
>>
>
Re: Acked still zero after update some properties
Posted by Kashyap Mhaisekar <ka...@gmail.com>.
Also, for checking if your topology is working or not, the default values
are more than sufficient. You dont need to change the buffer settings for
sure.
Did you check with the default test topology on the word count on your
cluster? Does this work?
On Sun, Jan 17, 2016 at 10:23 AM, John Yost <ho...@gmail.com> wrote:
> Okay, this actually looks like the only tuples going through your topology
> are tick tuples. To confirm, I recommend adding some logging statements in
> the b-0 bolt to confirm if you are getting any non-tick tuples in the
> execute method.
>
> --John
>
> On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <prog.researcher@gmail.com
> > wrote:
>
>> i submitted topology with storm and it's not my topology it's from
>> project submitted before so it should has no error !
>>
>> i submitted topology with topology.stats.sample.rate: 1
>> topology.acker.executors: 1
>> topology has one worker = one supervisor but in the code ,
>> conf.setMaxSpoutPending(50000000) so
>>
>> 1- is there any othr properties i should change it as i'm using defualt
>> values ?
>>
>> 2- what are the condidtions or the calculatation you are using to make
>> properites more convient with the topology ?
>>
>> like
>> #topology.executor.receive.buffer.size: 16384
>> # topology.executor.send.buffer.size: 16384
>> # topology.transfer.buffer.size: 32
>> # topology.receiver.buffer.size: 8
>>
>>
>>
>>
>
>
Re: Acked still zero after update some properties
Posted by John Yost <ho...@gmail.com>.
Okay, this actually looks like the only tuples going through your topology
are tick tuples. To confirm, I recommend adding some logging statements in
the b-0 bolt to confirm if you are getting any non-tick tuples in the
execute method.
--John
On Sun, Jan 17, 2016 at 10:22 AM, researcher cs <pr...@gmail.com>
wrote:
> i submitted topology with storm and it's not my topology it's from project
> submitted before so it should has no error !
>
> i submitted topology with topology.stats.sample.rate: 1
> topology.acker.executors: 1
> topology has one worker = one supervisor but in the code ,
> conf.setMaxSpoutPending(50000000) so
>
> 1- is there any othr properties i should change it as i'm using defualt
> values ?
>
> 2- what are the condidtions or the calculatation you are using to make
> properites more convient with the topology ?
>
> like
> #topology.executor.receive.buffer.size: 16384
> # topology.executor.send.buffer.size: 16384
> # topology.transfer.buffer.size: 32
> # topology.receiver.buffer.size: 8
>
>
>
>