Thanks Vincent. Appreciate your kind suggestion, it worked like a charm! :)
On Wed, Jan 28, 2015 at 7:00 PM, Vincent Russell <[email protected]> wrote: > > You can bundle all of your dependencies into your topology jar using the > maven shade plugin or uberjar with lein. > > On Wed, Jan 28, 2015 at 7:24 AM, Vineet Mishra <[email protected]> > wrote: > >> Well thanks all, I got it working, it seems that the topology jar itself >> was having the topology in the build path, the reason of which it was >> referring the old code. I got it working but only in local mode. >> >> Moreover I was looking out a way as how to invoke job in distributed >> mode, what currently I was doing was copying the dependencies(kafka and >> other few possible) to Storm lib folder and Storm was picking up those >> dependencies while running, but in distributed mode >> >> 1) I am not sure is it a good way to put the external dependencies in the >> Storm lib folder >> 2) If its not a way, then how should we schedule the job in distributed >> mode >> >> Looking out for quick response. >> >> Thanks in advance! >> >> On Wed, Jan 28, 2015 at 11:49 AM, Vineet Mishra <[email protected]> >> wrote: >> >>> Hi Jens, >>> >>> No its not referring to the old jars in the log(bcoz that has been >>> already deleted) rather its picking the changed jar but more over the fun >>> fact is that even storm is picking up new jar but still running the old >>> code(as I can't see the new code running up) in my topology. >>> >>> Thanks! >>> >>> On Tue, Jan 27, 2015 at 11:07 PM, Jens-Uwe Mozdzen <[email protected]> >>> wrote: >>> >>>> Hi Vineet, >>>> >>>> Zitat von Vineet Mishra <[email protected]>: >>>> >>>>> Hi Naresh and Jens, >>>>> >>>>> Well first I tried running a job in local mode that was running good, >>>>> but I >>>>> wanted to run it in distributed environment, >>>>> later I killed the job(Ctrl+c) and rebuild the jar with some addones >>>>> in the >>>>> bolts and made it to run in a production mode >>>>> by StormSubmitter.submitTopology(.,.,.). >>>>> >>>>> I am not sure what was the reason that the job was not able to run as I >>>>> changed the build but soon after cluster restart the same distributed >>>>> job >>>>> started running. >>>>> >>>>> Now if I am killing the existing running job via terminal or via storm >>>>> UI >>>>> it kills pretty fine but Storm is over and over referencing the same >>>>> old >>>>> jar even thought I am making a fresh build. >>>>> >>>> >>>> sorry for repeating myself - *where* is it referencing the same old >>>> jar... in the log files? >>>> >>>> If you're only judging by the functionality/behavior, it might be an >>>> issue of unchanged serialVersionUIDs and cached classes... >>>> >>>> Regards, >>>> Jens >>>> -- >>>> Jens-U. Mozdzen voice : +49-40-559 51 75 >>>> NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 >>>> Postfach 61 03 15 mobile : +49-179-4 98 21 98 >>>> D-22423 Hamburg e-mail : [email protected] >>>> >>>> Vorsitzende des Aufsichtsrates: Angelika Mozdzen >>>> Sitz und Registergericht: Hamburg, HRB 90934 >>>> Vorstand: Jens-U. Mozdzen >>>> USt-IdNr. DE 814 013 983 >>>> >>>> >>> >> >
