I am sure that such info should be reflected in wiki.

On Fri, Sep 10, 2010 at 10:51 PM, Sanjit Jhala <[email protected]> wrote:

> Hi Stanislav,
>
> If you look at the directory run/monitoring under the install path on the
> master server, you will see these files:
>
> rs_map.txt
> rs_stats.txt
> table_stats.txt
> rs1_stats_v0.rrd
> rs2_stats_v0.rrd
> ....
> rsN_stats_v0.rrd
>
> The file rs_map.txt contains a mapping from range server id (ie rs1, rs2
> etc) to ip address.
> The file rs_stats.txt contains stats for the last 1,5, 10 min time
> intervals for all rangeservers.
> The file table_stats.txt contains stats for the last 1,5, 10 min time
> intervals for all tables.
> The file rsi_stats_v0.rrd is an RRD file containing archived stats for the
> ith rangeserver (upto last 18 months) I believe. To see how to extract data
> from the RRD database you can look at the Monitoring UI code
> (src/rb/Monitoring) or take a look at the RRDTool 
> documentaion<http://oss.oetiker.ch/rrdtool/doc/index.en.html>.
> By default the system updates statistics every 30s which can be controlled
> via the config "Hypertable.Master.StatsGather.Interval". You can use rrdtool
> info to examine the contents of the rrd file, for example to list all the
> stats stored in it:
> *rrdtool info rs1_stats_v0.rrd |grep "ds.*type"*
>
> -Sanjit
>
>
> On Fri, Sep 10, 2010 at 12:40 AM, Stanislav Yudin <[email protected]>wrote:
>
>> Congratulations on this milestone!
>> This release includes monitoring UI, but what about Monitoring APIs? I
>> believe that stats format should have been changed too.
>>
>> On Fri, Sep 10, 2010 at 9:12 AM, Doug Judd <[email protected]> wrote:
>>
>>> Hypertable micro release 0.9.4.0 has been released and is now available
>>> for download at http://www.hypertable.org/download.html.
>>>
>>> NOTE:  This release is *incompatible* with previous releases.  There have
>>> been numerous API 
>>> changes<http://code.google.com/p/hypertable/wiki/ApiChanges>,
>>> as well as changes to the on-disk format.  To upgrade from a previous
>>> release, you will need to do the following:
>>>
>>> 1. backup your tables
>>> 2. clean the database
>>> 3. upgrade the Hypertable software to 0.9.4.0
>>> 4. restore from backup
>>>
>>> Version 0.9.4.0:
>>> (2010-09-09)
>>>
>>>     Added Namespaces
>>>     Added AG garbage collection logic for MAX_VERSIONS, deletes, and TTL
>>>     Hypertable Monitoring web interface using sinatra
>>>     Made changes to garbage collect unused Hyperspace BerkeleyDB logs.
>>>     Upgraded to Thrift 0.4.0
>>>     issue 501: Made Capistrano "upgrade" task first verify that upgrade
>>> is OK
>>>     issue 440: Renamed CellFlag to KeyFlag; Renamed put_ methods to
>>> offer_
>>>     issue 504: Store relative filenames in METADATA
>>>     Added RENAME TABLE feature.
>>>     issue 479: Added support for configurable toplevel directory name
>>>     issue 174: Changed all state file/dir names to include table id
>>> instead of name
>>>     Modified capfile to start and stop monitoring server on master.
>>>     Updated location of monitoring UI code.
>>>     Modified start and stop scripts for Monitoring UI
>>>     Made changes to print out ProxyMap to text file to be used for the
>>> Monitoring UI.
>>>     Fixed string encoding/decoding problem in Java code
>>>     Fixed stats gathering logic to handle variable length string table ID
>>>     issue 316: Moved CREATE TABLE options to the end after column defs
>>>     issue 487: Fixed Comm layer core dump with many client connections
>>>     issue 496: Fixed bad logic in EINTR handling
>>>     Changed namespace "SYS" to "sys"
>>>     issue 497: fixed problem of column qualifier not getting cleared in
>>> Thrift API
>>>     issue 11: Use shorter cellstore filenames. Fixed
>>>     Added hypertable shell regression test for namespaces. Updated some
>>> documentation.
>>>     Namespace Client API changes.
>>>     issue 174: Changed all state file/dir names to include table id
>>> instead of name
>>>     issue 234: Propagate better error messages from DfsBroker to
>>> RangeServer log
>>>     issue 106: Use JAVA_HOME to find java binary, if set
>>>     Got rid of verbose logging from recent AG garbage collection change -
>>> Also changed Hypertable.RangeServer.AccessGrou
>>>     issue 479: Added dual-instance regression test
>>>     Changed semantics of readdirattr and readpathattr Hyperspace commands
>>>     Added NameIdMapper class.
>>>     Made changes to store next table id in Hyperspace..
>>>     Added Hyperspace readpathattr API to list the value of an attribute
>>> for all components in a path
>>>     Added Hyperspace attr_incr API to atomically increment an attribute.
>>>     [Issue 148] hql parser doesn't like quotes inside a string even when
>>> escaped. Fixed.
>>>     [Issue 481] ThriftClient-reconnect-hyperspace failure. Fixed.
>>>     [Issue 491] core dump at get_ts64() of Time.cc. Fixed
>>>     [Issue 488]  Hyperspace crash. Fixed
>>>     [Issue 492] RangeServer crash. Fixed
>>>     Fixed bug in Master stats collection.
>>>     Made changes to checkpoint BDB every time there is 1M worth on
>>> uncheckpointed log data.
>>>     Minor fix in FindRRDtool.cmake
>>>     Don't link Hyperspace.Master to tcmalloc for 32-bit
>>>
>>>  --
>>> 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]<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]<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.

Reply via email to