Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of jim.robinson@gmail.com
 designates 209.85.220.52 as permitted sender)
MIME-Version: 1.0
Sender: jim.robinson@gmail.com
In-Reply-To: 
 <CAPVVMa8P2S3Z7MLiC-25S0Fue8k5Ud92yhnp_Bqv+3uY0uK3zg@mail.gmail.com>
References: <1425650874394-4692615.post@n4.nabble.com>
 <CAPd04b7AWoGWthhJfgSdvkm7P0d8SkW9rt-9uWG13oCSzq1Ocg@mail.gmail.com>
 <54FDC9E8.8000406@gmail.com>
 <CAPVVMa8D+Ub2v3T34Y560mN8-WkvOYXLCCJLJ=UbbGcm3nVkew@mail.gmail.com>
 <CAH+vQmMedZOLiwKp0ByqdpyCL2S1ybZYcJn-Ps5BCMTy=z-PHA@mail.gmail.com>
 <CAPVVMa9K-37b4cZ3yR9X-rncS2N9SNsh9HQgu3jrGdkCvWucqQ@mail.gmail.com>
 <1426132747484-4693034.post@n4.nabble.com>
 <CAPVVMa8wrg3trLA2qkDjh2tXR-bLSHH0cBDD2486fn+=gB-ozQ@mail.gmail.com>
 <CAPd04b51um1L8W+-6rJKPNGxvy4y8OU49QxsjsAySyT6_AArAA@mail.gmail.com>
 <CAPVVMa8P2S3Z7MLiC-25S0Fue8k5Ud92yhnp_Bqv+3uY0uK3zg@mail.gmail.com>
From: "James A. Robinson" <jimr@highwire.org>
Date: Thu, 12 Mar 2015 22:23:59 -0700
Message-ID: 
 <CAPd04b6XHLWB2OZ5GuW5T_MoEMNwFjT1oZ0LcL_kafKDTud7Qw@mail.gmail.com>
Subject: Re: Data Migration from KahaDB to LevelDB?
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=047d7b15a5a191ba40051124b73c

--047d7b15a5a191ba40051124b73c
Content-Type: text/plain; charset=UTF-8

On Thu, Mar 12, 2015 at 9:26 PM, Tim Bain <tbain@alumni.duke.edu> wrote:

> This doesn't really work for topics; you need to get the new messages to
> collect on b2 while the old consumer drains b1, and only then have the old
> consumer disconnect and reconnect on b2; you can't have the consumer
> simultaneously connected to both b1 and b2.
>

I see, my assumption has been that it'd be considered reasonable
for the old consumers to not consume new topic data.  I see where
that might break down depending on your use case for what those
consumers were doing.

--047d7b15a5a191ba40051124b73c--