[evla-sw-discuss] moving monitor point archive loader(s)

[Bill Sahr]

I agree with Rich, Stephan, and James.  Moving the dbase loaders,
both for alerts & monitor data, from mcmonitor and mctest to
the machines that host the databases, r2d2 and lando, makes a
lot of sense to me, basically, for the reasons already cited
by Stephan.

One would _not_ want to do something similar for the query interface.
The mid-term plan for the query interface is to give it the ability
to change databases on-the-fly so it will not be tied to a specific
database, and should most definitely not be down when a particular
database or machine hosting a database is down.

bill

Stephan Witz wrote:
> I'd like to move the monitor point and alert archive loaders off of
> mcmonitor and mctest and onto the machines that host those databases
> (r2d2 and lando, I think). I think doing so will make things a bit
> cleaner out there: it will reduce the network traffic a bit and it
> will get what is essentially a production service (monstdby loader)
> off of mctest.
> 
> I'd like to live in a world where mctest can be shut down, rebooted,
> or replaced with a bucket of turnips with absolutely no impact on
> production.
> 
> Discuss.
>