* History logs and RRD files - i.e. the Hobbit modules that need to
store data on disk - can be distributed among multiple servers.
Hobbit will automatically send updates to the correct server, and
fetch data from the server holding it when generating webpages.
This also applies to the client-data logs that are stored when
a critical event occurs. (4.3.0)
Is this leading the way to a hot-cold or hot-hot HA setup? I understand how
one server could distribute jobs to a farm. But what if the central server
goes down? If data is sync'ed throughout the environement how could the
'freshest' be guaranteed through failures?
I am looking to implement a HA Hobbit solution where 10 minutes of recovery
is acceptable while preserving historical data.
Are you just writing 'load sharing logic' or do you plan on developing
failover/recovery logic as well?
Scott Walters
-PacketPusher