Thanks Ewen, I am just trying to ensure a smooth role over. So what I was able to test so far, was 0.10.1 mirror maker with source (0.10.0.1) and target (0.10.1) brokers. That doesn't work, even if I specify zookeepers in the consumer config. Not work as in "comes up, does nothing, eventually throws a socket time out". The old version of mirror maker does work with this setup and config. I guess I have to setup 2 new broker clusters and test new mirror maker to start working, but it's a lot of trouble for a minor update.
tl;dr: the fine print of mirror maker update is underspecified and thus I have a trust deficiency that the new mirror maker will work. Cheers, Hagen On Sun, Dec 11, 2016 at 3:52 AM, Ewen Cheslack-Postava <e...@confluent.io> wrote: > Hagen, > > What does "new consumer doesn't like the old brokers" mean exactly? > > When upgrading MM, remember that it uses the clients internally so the same > compatibility rules apply: you need to upgrade both sets of brokers before > you can start using the new version of MM. > > -Ewen > > On Thu, Dec 8, 2016 at 6:32 AM, Hagen Rother <hagen.rot...@liquidm.com> > wrote: > > > Hi, > > > > I am testing an upgrade and I am stuck on the mirror maker. > > > > - New consumer doesn't like the old brokers > > - Old consumer comes up, but does nothing and throws > > a java.net.SocketTimeoutException after while. > > > > What's the correct upgrade strategy when mirroring is used? > > > > Thanks! > > Hagen > > > > > > -- > Thanks, > Ewen > -- *Hagen Rother* Lead Architect | LiquidM ------------------------------ LiquidM Technology GmbH Rosenthaler Str. 36 | 10178 Berlin | Germany Phone: +49 176 15 00 38 77 Internet: www.liquidm.com | LinkedIn <http://www.linkedin.com/company/3488199?trk=tyah&trkInfo=tas%3AliquidM%2Cidx%3A1-2-2> ------------------------------ Managing Directors | André Bräuer, Philipp Simon, Thomas Hille Jurisdiction | Local Court Berlin-Charlottenburg HRB 152426 B
