When you killed the old topology with the old jar did you wait for the timeout period? If you want to kill it right away use the -w 0 flag and check the storm UI to make sure the job is gone, like Jens-U mentioned I don't think ur looking at the right cause. I have done this in the past, and deployed my topology before it was killed so just guessing this is what you might be doing...
On Tue, Jan 27, 2015 at 8:24 AM, Vineet Mishra <[email protected]> wrote: > Hi All, > > I am stucked at a vague issue. I am having a 3 node Storm > Cluster(apache-storm-0.9.3) with configuration given below, > > node1 - Nimbus, UI > node2 - Supervisor, Worker > node3 - Supervisor, Worker > > I have written a topology and I was running it through storm, but soon > after I made some changes in Bolts, created a fresh jar, redeployed it and > ran again with the Storm jar command, but it still seems to be referring > the old jar somewhere cached(although I have already deleted that old jar). > > I am seriously stucked at this issue, tried looking at some post relating > the same issue but couldn't find any sufficing answer. > > Looking for expert comments. > > Thanks in advance! > > >
