Re: Facing issue in deployment of a topology.

["M.Tarkeshwar Rao" <ta...@gmail.com>]

Yes it is apache 0.9.0.1.Is there any problem in this version?


On Mon, Jun 30, 2014 at 7:26 PM, Naresh Kosgi <na...@gmail.com> wrote:

> are you using the apache version?
>
>
> On Mon, Jun 30, 2014 at 8:56 AM, M.Tarkeshwar Rao <ta...@gmail.com>
> wrote:
>
>> Hi,
>>
>> Thanks Naresh for your quick inputs.
>> I want to share my experience which i got during fixing this issue.
>>
>> we are using version of storm 9.01 for our product. When we used netty
>> with two workers it is getting hanged but runs fine with one worker.
>>
>> I changed the netty to zeroMq it is working fine.
>>
>> What should we change if we want to go with netty?  Is there any option
>> in netty which i need to set.?
>>
>> Regards
>> Tarkeshwar
>>
>>
>> On Sun, Jun 29, 2014 at 3:16 AM, Naresh Kosgi <na...@gmail.com>
>> wrote:
>>
>>> it sounds like storm is working just fine from what you stated.  When
>>> you kill the worker using kill 9, it is possible for some of the work to be
>>> lost (Any work that the worker you killed was doing is lost).  If you have
>>> reply setup with your topology all of that lost work by that worker is
>>> replayed.
>>>
>>>
>>> On Sat, Jun 28, 2014 at 5:39 PM, Sean Allen <sean@monkeysnatchbanana.com
>>> > wrote:
>>>
>>>> we kill 9 storm processes from time to time without issue.
>>>>
>>>>
>>>> On Sat, Jun 28, 2014 at 10:57 AM, M.Tarkeshwar Rao <
>>>> tarkeshwar4u@gmail.com> wrote:
>>>>
>>>>> Yes we are killing it by kill -9.but we are devloping the new
>>>>> product.we have to test that product weather this product working on
>>>>> clusture or not.we are very new on storm.it might be posible that we
>>>>> dont know how to test node failures.can u pls guide me on this. Is there
>>>>> any issue in testing by kill- 9 to test node failure cases?
>>>>>  On 28 Jun 2014 18:37, "Naresh Kosgi" <na...@gmail.com> wrote:
>>>>>
>>>>>> How are killing the worker?  If you trying restart the topology with
>>>>>> less or more workers, you have to stop the topology and restart it with
>>>>>> more or less workers.  It is not a good idea to just kill one worker (i'm
>>>>>> guessing your using kill -9 to kill one of the workers java process)
>>>>>>
>>>>>>
>>>>>> On Sat, Jun 28, 2014 at 8:51 AM, M.Tarkeshwar Rao <
>>>>>> tarkeshwar4u@gmail.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I am facing a issue in a deployment of a topology.we are using
>>>>>>> trident. Actually our topology working fine with one worker. when I set the
>>>>>>> number of worker 2 it is working.but when I kill one of the worker process
>>>>>>> it is giving issue.
>>>>>>> > Sometimes it is working but sometimes the communication between
>>>>>>> two workers getting hanged. I analyzed the issue and found that when the
>>>>>>> killed worker again alive  on new slot (port) it is working fine.
>>>>>>> But when this killed worker alive on same port comunication between
>>>>>>> workers getting hanged.Can u please help me out to resolve it
>>>>>>>
>>>>>>> We are using scheduler where we sheduled  master-batch-controlller,
>>>>>>> co-ordinator and emitor on single machine and in single worker.remaining
>>>>>>> bolts on 2nd worker.
>>>>>>>
>>>>>>> Regards
>>>>>>> Tarkesh
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Ce n'est pas une signature
>>>>
>>>
>>>
>>
>