Can you tell us the output of <install_dir>/bin/ht -v, uname -a and which DFS you're using (HDFS or KFS?), did the range server/dfs broker/hdfs datanode crash?
You might be able to set Hypertable.MetaLog.SkipErrors=1 and restart the range server. But I'd like to find out why metalog is corrupted. On Wed, Nov 11, 2009 at 6:41 AM, Ramesh <[email protected]> wrote: > > 1257948078 INFO Hypertable.RangeServer : (/home/luke/Source/hypertable/ > src/cc/Hypertable/RangeServer/ConnectionHandler.cc:200) Event: > type=CONNECTION_ESTABLISHED from=202.137.239.106:38050 > 1257948078 ERROR Hypertable.RangeServer : local_recover (/home/luke/ > Source/hypertable/src/cc/Hypertable/RangeServer/RangeServer.cc:472): > Hypertable::Exception: Error reading metalog: /hypertable/servers/ > 202.137.239.106_38060/log/range_txn: read 14873/15476 - METALOG > checksum mismatch > at virtual Hypertable::MetaLogReader::ScanEntry* > Hypertable::MetaLogReaderDfsBase::next > (Hypertable::MetaLogReader::ScanEntry&) (/home/luke/Source/hypertable/ > src/cc/Hypertable/Lib/MetaLogReaderDfsBase.cc:128) > at virtual Hypertable::MetaLogReader::ScanEntry* > Hypertable::MetaLogReaderDfsBase::next > (Hypertable::MetaLogReader::ScanEntry&) (/home/luke/Source/hypertable/ > src/cc/Hypertable/Lib/MetaLogReaderDfsBase.cc:122): type=0 expected 0, > got f744682 > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
