Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BEEFA17FE5 for ; Mon, 20 Oct 2014 13:08:24 +0000 (UTC) Received: (qmail 24512 invoked by uid 500); 20 Oct 2014 13:08:19 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 24465 invoked by uid 500); 20 Oct 2014 13:08:19 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 24453 invoked by uid 99); 20 Oct 2014 13:08:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2014 13:08:18 +0000 X-ASF-Spam-Status: No, hits=4.0 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX,URI_TRY_3LD X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of james.mk.green@gmail.com designates 209.85.215.47 as permitted sender) Received: from [209.85.215.47] (HELO mail-la0-f47.google.com) (209.85.215.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2014 13:08:14 +0000 Received: by mail-la0-f47.google.com with SMTP id pv20so3830132lab.20 for ; Mon, 20 Oct 2014 06:07:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8eqz1PJ6S9OLx5jBc5CsNlMFQRzG+LrWNxXC11xXtFE=; b=aB2sMCYWvl3hKC7VpuGsWO+0A9vOVE0dnq+fUG/7cGSudUChjFNbD5gmLWJSmIvdih yCjU/tlUthKpPMSx0nT0t0OgQim0P5+Y6Yj1a2IkN38xi9JoQR0esA98EKUIm8x9C+Ne kE1j3H9DWkcqotxJr4ooGfSPXcSZ2oc0Q/LzD9iH9i2z/oYJZjgPtAqtkjS/dhmXxY7X bTBEi9d9Z2ZQtONx4iDar/nctYiQS+lUmmCtkepRKiU5yVBAko8Xl0peZVvUh/ciiP1j 0ncp9o7scOlWMK8xDILGbZ9KTx26mUaAhweswkB6qaO7U+l8sURzCeP6rC8jysi7Nt0e qKvA== MIME-Version: 1.0 X-Received: by 10.112.54.162 with SMTP id k2mr27130887lbp.63.1413810473242; Mon, 20 Oct 2014 06:07:53 -0700 (PDT) Received: by 10.25.166.144 with HTTP; Mon, 20 Oct 2014 06:07:53 -0700 (PDT) In-Reply-To: <1413405556270-4686426.post@n4.nabble.com> References: <1413405556270-4686426.post@n4.nabble.com> Date: Mon, 20 Oct 2014 14:07:53 +0100 Message-ID: Subject: Re: 5.9 to 5.10 Upgrade From: James Green To: users Content-Type: multipart/alternative; boundary=001a11c3eeee0995f90505da67ba X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3eeee0995f90505da67ba Content-Type: text/plain; charset=UTF-8 We have a hub/spoke architecture. We did a rolling upgrade from 5.7.0 to 5.10.0 starting with the hub instance. So long as the client/server & peer protocols don't become incompatible it's fine. On 15 October 2014 21:39, djdick wrote: > We're looking to upgrade from 5.9 to 5.10 and are using a network of > brokers > topology. In order to keep downtime to a minimum we're looking at upgrading > one server at a time while keeping the other servers active. For example > server A stays active while we shutdown server B and upgrade from 5.9 to > 5.10. Then bring server B up while we take down server A and upgrade it to > 5.10. > > Has anyone else tried this? > Will this allow us to upgrade our environment without any downtime? > Has anyone experienced problems with 2 different versions of ActiveMQ > communicating with each other (5.9 to 5.10)? > > Any guidance or experience you could share with this process is greatly > appreciated. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/5-9-to-5-10-Upgrade-tp4686426.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a11c3eeee0995f90505da67ba--