Hi Conferno, That does seem like an elegant solution, but I'm a little reluctant to put monitoring data from the system back into it.
Yes the idea is to run a monitoring periodically in a thread on the master. -Sanjit On Fri, Apr 16, 2010 at 3:12 PM, conferno <[email protected]> wrote: > Hi Sanjit > > > Also the master will store per server and per table stats in something > like RRDTool, so that should provide a sliding window of historical data. > > Perhaps, in a Hypertable's table with a special name, like METADATA. ? > Since we will have COMPACT command soon, the table will not grow > indefinitely. > Executing periodically DELETE and COMPACT against the table will > result if RRDTool-like behaviour. > > BTW, i think, the monitoring daemon (which asks RangeServers then > stores the data) can be independent from Master server. > In a particular case it can be run as a thread in Master process. > > -- > You received this message because you are subscribed to the Google Groups > "Hypertable Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<hypertable-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/hypertable-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en.
