Hi Milko, For the most part, you no longer need to supply these options. However, you may need to supply Hypertable.CommitLog.SkipErrors if you discover that one of the commit logs is corrupt and you would like to proceed with possible data loss.
- Doug On Wed, May 27, 2009 at 3:57 AM, <[email protected]> wrote: > > Hi Doug, > > In the Hypertable config 0.9.2.3 ver I have added the following keys: > > Hypertable.Lib.Mutator.FlushDelay=100 > Hypertable.CommitLog.SkipErrors=true > > Hypertable.RangeServer.AccessGroup.CellCache.PageSize=512K > > Please let me know if I have to add the same keys into the config of > 0.9.2.4 version or some of them are fixed into the release. > > Please let me know if there are any new keys which should be added to the > config. > > Regards, > > Milko > > ************************************************** > Assoc. Prof. Milko Todorov Marinov, PhD > Department of Computer Systems & Technologies > University of Rousse > 8 Studentska Str, 7017 Rousse, BULGARIA > Tel. (+359 82) 888 356, Fax. (+359 82) 845 708 > Cell phone: (+359 88) 999 6793 > E-mail: [email protected] > ************************************************* > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
