Hey Joaquin, You can perhaps create a blog-post or add something on http://stackoverflow.com/documentation This will help others doing the upgrade and maybe we can address some of them in the Storm codebase as well.
-SG On Thu, Sep 8, 2016 at 6:26 PM, Joaquin Menchaca <[email protected]> wrote: > Summary, a lot of the issue I was having were due to Storm 0.10.0 > zookeeper key/values existing, when trying to bring up Storm 1.0.2 using > the same zookeeper and same server hostnames (essentially and in place > upgrade). > > Solution was to stop zookeeper, blast out all the data, then start > zookeeper up again. > > This problem generated all sorts of errors: > > - TFramedTransport invalid frame size, > - TTransportException, and > - Unexpected throwable while invoking! > > Anyhow, a painful process, glad that is over, but now need to have my > supervisors and nimbus not report themselves as localhost.... > > Trying to rely on hostname so that I can reverse-proxy to all the systems > and not use split-DNS, but that's another adventure. > > > -- > > 是故勝兵先勝而後求戰，敗兵先戰而後求勝。 >
