This reminds me of HBASE-7958 Statistics per-column family per-region Cheers
On Thu, Sep 4, 2014 at 6:23 PM, Mikhail Antonov <[email protected]> wrote: > I think ZK isn't the best possible storage for statistics. A separate stats > table may be better solution. > > -Mikhail > > > 2014-09-04 15:48 GMT-07:00 Michael Segel <[email protected]>: > > > So suppose I want to capture metadata about a table across all of the > > regions for that table. > > > > Has anyone used a coprocessor to capture a region’s statistics and push > > them up to ZK where its stored by (table, region, <metadata object>) and > > then a table wide value is also stored based on a computational update? > > > > So if I wanted to store the row counts for each region of a table, each > > region would update its record in ZK on each insert / delete (can you > > easily remove a tombstone?) and then update the computational value? > > (Assuming you could lock those values for a short enough time to do the > > quick computation. If not, then it can be computed on the fly) > > > > Has this been done? > > > > Thoughts? > > > > > > > -- > Thanks, > Michael Antonov >
