Re: Data upgrade from 0.89x to 0.90.0.

2011-02-11 Thread James Kennedy
Right, but the 2.78hours [threadWakeFrequency (1ms) x multiplier (1000ms)] check comes before a full compaction and from the code it looks like the NPE would have blocked any Store that had no timeRangeTracker from every getting a major compaction... unless it had been triggered in some

Data upgrade from 0.89x to 0.90.0.

2011-02-10 Thread James Kennedy
I've tested HBase 0.90 + HBase-trx 0.90.0 and i've run it over old data from 0.89x using a variety of seeded unit test/QA data and cluster configurations. But when it came time to upgrade some production data I got snagged on HBASE-3524. The gist of it is in Ryan's last points: * compaction is

Re: Data upgrade from 0.89x to 0.90.0.

2011-02-10 Thread Ryan Rawson
we only major compact a region ever 24 hours, therefore if it was JUST compacted within the last 24 hours we skip it. this is how it used to work, and how it should still work, not really looking at code right now, busy elsewhere :-) -ryan On Thu, Feb 10, 2011 at 11:17 PM, James Kennedy