falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pragya mittal <mittal.pragy...@gmail.com>
Subject Re: Running 2 versions of Falcon on the same cluster/upgrade procedure
Date Fri, 19 Feb 2016 12:16:11 GMT
Hi Mark,

To maintain entities there you can configure the config-store property in
# Location to store user entity configurations

(I usually maintain a standard location to store entity configs and point
all my falcon to the same store)

After this it is pretty straight-forward. This is how you can migrate from
one falcon version to another :

1. Stop the old falcon instance. Install Falcon 0.9 on the same cluster as
the old one. Maintain the config-store property as defined above (in prism
as well as server)
2. Start falcon-0.9 and you should be able to list your entities. Consider
re-runing any failed/killed instances if required.

Note :
Two servers of falcon cannot co-exist in the same cluster as of now.

There is no documentation as of now. We will consider adding the same.

Pragya Mittal

On Fri, Feb 19, 2016 at 10:14 AM, Marek Wiewiorka <marek.wiewiorka@gmail.com
> wrote:

> Hi All - I've basically a question related to migration of entities between
> Falcon versions.
> I would like to upgrade Falcon from an old version to 0.9 by following such
> an procedure:
> 1)Install Falcon 0.9 on the same cluster as the old one (and have them both
> running at the same time)- 2 questions arise:
> a)is it possible at all and if so what should be configured: ports,
> anything else?
> b)how to backup the existing entities definition?
> 2) test a few of the processes using the new Falcon
> 3)migrate all of the processes to the new Falcon
> 4)Decommission the old Falcon installation
> Is there any document describing a migration procedure?
> The most import question for me now is the first one - how to run temporary
> 2 falcon instances
> on the same cluster for testing purposes? Is it safe?
> Many thanks in advance for any hints.
> Marek

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message