On Sat, Mar 7, 2009 at 6:00 PM, Doug Judd <[email protected]> wrote: > Can you print a log message inside the CellStoreScannerV0 constructor and > destructor to make sure that the scanners are actually getting destructed?
The constructor gets called 2248 times, while the destructor gets called 1915 times. I'm pretty sure every scanner gets destroyed at appropriate time, and I've refactored my code a bit to take advantage of scoping so that scanners get destroyed but there's still a disparity in the number of times both destructor and constructor get called. > In the destructor, you can see the statement: > > if (m_block.base != 0) > Global::block_cache->checkin(m_file_id, m_block.offset); > > If the scanner is not getting destructed then the last scanned block will > not get checked in (above statement), preventing its reference count from > dropping to zero, making it release-able. Ok. The picture starts forming in my head how this thing works. I'll try poking around. Mateusz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
