Subject: Re: [lmap] Comments on draft-schulzrinne-lmap-requirements-00 - redundancy

From: Henning Schulzrinne <[email-masked]>
Date: Mon, 5 Nov 2012 01:22:31 +0000

5) Finally, it might be nice to consider that for redundancy and/or performance reasons a singular measurement test may simultaneously write results to several measurement data collectors. Alternatively, is the vision that a single measurement data collector will receive results and, in the background?, distribute that to multiple measurement data collectors? Ultimately, this is a discussion about the necessity of caching of measurement data, which becomes important to consider as either: a) the data set inevitably grows larger (into millions of nodes?); and/or, b) entities wish to consume historical data-sets that inevitably will be extremely large.

Good point and I see no reason to limit writing the results to one server. As you note, measurement servers can also back up files in the background. That can presumably use standard file synchronization mechanisms (e.g., rsync), but would increase the size of the failure unit from a single tuple to a whole measurement run. The obvious downside is that this increases the traffic from the client to the collectors.

-shane
_______________________________________________
lmap mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/lmap