Hi kuer, I don't see any problem with the log snippet that you give below. The "clgc LOG FRAGMENT PURGE" messages are just leftover debugging statements that I forgot to remove in a recent checkin. Are you experiencing a real problem with the database? If so, what is the symptom?
- Doug On Tue, Jul 7, 2009 at 4:48 PM, kuer <[email protected]> wrote: > > I found lots of message in rangeserver's log : > > 2009-07-08 07:30:23,198 1231112512 Hypertable.RangeServer [WARN] (Lib/ > CommitLog.cc:250) clgc LOG FRAGMENT PURGE breaking because > 1247008867417054087 >= 1247003041037972148 (file='/hypertable/servers/ > 221.194.134.176_31060/log/user/75') > 2009-07-08 07:30:23,198 1231112512 Hypertable.RangeServer [INFO] > (RangeServer/RangeServer.cc:2032) Memory Usage: 322964958 bytes > 2009-07-08 07:30:43,197 1336011072 Hypertable.RangeServer [INFO] > (RangeServer/RangeServer.cc:2032) Memory Usage: 323476974 bytes > 2009-07-08 07:31:03,198 1199642944 Hypertable.RangeServer [WARN] (Lib/ > CommitLog.cc:250) clgc LOG FRAGMENT PURGE breaking because > 1247008867417054087 >= 1247003041037972148 (file='/hypertable/servers/ > 221.194.134.176_31060/log/user/75') > 2009-07-08 07:31:03,198 1199642944 Hypertable.RangeServer [INFO] > (RangeServer/RangeServer.cc:2032) Memory Usage: 323476974 bytes > 2009-07-08 07:31:23,197 1294051648 Hypertable.RangeServer [INFO] > (RangeServer/RangeServer.cc:2032) Memory Usage: 323476974 bytes > 2009-07-08 07:31:43,198 1178663232 Hypertable.RangeServer [WARN] (Lib/ > CommitLog.cc:250) clgc LOG FRAGMENT PURGE breaking because > 1247008867417054087 >= 1247003041037972148 (file='/hypertable/servers/ > 221.194.134.176_31060/log/user/75') > 2009-07-08 07:31:43,198 1178663232 Hypertable.RangeServer [INFO] > (RangeServer/RangeServer.cc:2032) Memory Usage: 324501006 bytes > > It seems that it will be never end. > > I want to know : > 1. How this happened? why to purge a future revision? > 2. How to resolve/correct this problem? > From the purge() function, the thread will stop purging if > meeting with the 'fucture' revision, and purge() will end. The > 'future' revision data is still there; when purging next time, it will > complain it again. > What's the rationale behind this? > Would someone tell me kindly? > > Thanks. > > -- kuer > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
