CONTGRATS! Curious why you changed the range_size (because of big rows or big ranges, or both).
Also is it better to let rows grow than to just not accept writes since at least it will not break applications? On Friday, August 16, 2013 7:30:07 AM UTC+2, Doug Judd wrote: > > Hypertable version 0.9.7.9 is now available for download at > http://www.hypertable.com/download/. > > Version 0.9.7.9: > (2013-08-15) > > QFS Broker > Improved disk usage monitoring and handling > Added system state with READONLY variable and HQL SET command > Changed Hypertable.RangeServer.Range.SplitSize default to 512MB > Fixed bug in delete processing in MergeScannerAccessGroup > Fixed CELL_LIMIT processing > Fixed level calculation in MaintenanceQueue > Reduced calls to Range::get_maintenance_data() in get_statistics() > Added version, start_row, and end_row to hints file > Moved transfer log to corresponding /tables/ directory > Fixed race condition in creation of RemoveOkLogs entity > Changed "dropping task" log message from WARN to INFO > Fixed race condition in RangeServer-failover-restart test > Better error state capture for group commit and rs failover basic tests > Replaced RSStats with LoadStatistics class > Added server disk usage statistics to RS_METRICS > Fix tests > Added PosixReaddir to DfsBroker interface > > > -- > Doug Judd > CEO, Hypertable Inc. > -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hypertable-dev. For more options, visit https://groups.google.com/groups/opt_out.
