Hi Doug, Today we find a strange problem in one Range Server's log:
$ grep 'Reporting.*sir_ip_index' RangeServer.log | lcat [...] Tue Dec 2 04:37:42 2008 INFO Hypertable.RangeServer : (/home/pp/src/ hypertable/src/cc/Hypertable/RangeServer/Range.cc:559) Reporting newly split off range sir_ip_index[116.17.176.112..116.217.10.39] to Master Tue Dec 2 04:40:38 2008 INFO Hypertable.RangeServer : (/home/pp/src/ hypertable/src/cc/Hypertable/RangeServer/Range.cc:559) Reporting newly split off range sir_ip_index[116.217.10.39..116.217.49.1] to Master Tue Dec 2 10:24:11 2008 INFO Hypertable.RangeServer : (/home/pp/src/ hypertable/src/cc/Hypertable/RangeServer/Range.cc:559) Reporting newly split off range sir_ip_index[122.224.30.210..122.5.114.102] to Master Wed Dec 3 04:07:42 2008 INFO Hypertable.RangeServer : (/home/pp/src/ hypertable/src/cc/Hypertable/RangeServer/Range.cc:559) Reporting newly split off range sir_ip_index[116.217.49.1..116.217.49.1] to Master The second and fourth lines indicate that two ranges with the same end row are split off, so they share the same row key in METADATA table, and the latter overwrite the former's METADATA record. In this way rows bigger than 116.217.10.39 and smaller than 116.217.49.1 become unreachable. It is strange that the last split contains a range with the same start row and end row. We reviewed all related code but couldn't find any possible reason why this could happen. Do you have any idea? We have multiple access groups in this sir_ip_index table. Thanks Donald --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
