One problem with region historian is it has 2 bad patterns: - makes meta a write path for critical things. Can cause slowness and worse - forces messages to visit the master just to queue up and wait for historian availability.
I would suggest future solutions consider the use of logging with aggregation, analysis and dumping posthoc to a seperate table from meta. Logs are great because its an always available facility. Since we run daemons on every host we can do aggregation easily and tie into map reduce to crunch large logs. Win win I hope. On Sep 17, 2009 6:55 PM, "Andrew Purtell" <[email protected]> wrote: J-D, +1, "Region Historian 2.0", disabling the current one. Sorry, I meant to say that in the beginning but then got carried away :-) - Andy ________________________________ From: Jean-Daniel Cryans < [email protected]> To: h... Sent: Thursday, September 17, 2009 6:51:23 PM Subject: Re: on the subject of historians (was Re: Are you using the Region Historian? Read this) Andrew, I think this is all good ideas, in fact I was thinking about a better "Region Historian 2....
