EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: EPICS archiver appliance redundancy
From: Phillip Sorensen <[email protected]>
To: Eric Berryman <[email protected]>
Cc: TechTalk EPICS <[email protected]>
Date: Fri, 15 Jul 2016 09:17:15 -0400
Eric,

Thanks for the information. Those were the two ideas that I had come up with. Would you be willing to share your python scripts? I was thinking of starting with the two instances model while investigating using a cluster manger long term.

Thanks,
Phil Sorensen


On 7/13/2016 2:22 PM, Eric Berryman wrote:
Hello!

I currently run two instances (not clustered) for redundancy, and have
python scripts to merge protobuffer files.  I realize this is not the
best solution.
What we currently started looking at is running the appliance on a
cluster (Apache Mesos), then use Apache Aurora for managing the
instances.  I think this the most ideal.
I'll have a presentation about it at the next EPICS meeting at SNS.

Thank you!
Eric Berryman

On Tue, Jul 12, 2016 at 3:52 PM, Phillip Sorensen <[email protected]
<mailto:[email protected]>> wrote:

    Hello,

    I am working on deploying the EPICS archiver appliance to replace
    our existing archive solution.  I have tested the multiple
    appliances, and it work well, but that seem to be more for scaling
    up the system and not redundancy or failover.  Is anyone out there
    doing anything to get redundancy or failover with the archive appliance?

    Phil




References:
EPICS archiver appliance redundancy Phillip Sorensen
Re: EPICS archiver appliance redundancy Eric Berryman

Navigate by Date:
Prev: drvAsynIPPort, asynOctetSyncIO and multithreading Brown, Garth
Next: RE: drvAsynIPPort, asynOctetSyncIO and multithreading Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: EPICS archiver appliance redundancy Eric Berryman
Next: Trigger aSub record from bi record reflecting status Luca Cavalli
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Jul 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·