Do you have a list of test cases you've tried? (like with/without walogs, custom iterators on tables, delete markers for the metadata table, etc.)?
If we could consolidate some of those into a comprehensive list, that'd be pretty useful, I'd think, to give confidence that we didn't miss anything in the review. It might also help focus testing for 1.6.1 release after you've pushed. Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, Jul 30, 2014 at 4:39 PM, Sean Busbey <[EMAIL PROTECTED]> wrote:
* Start up 1.4 (or 1.5) * Create tables with a variety of configurations (LZO/Snappy/GZ, Bloom Filter On/Off, Block Cache On/Off) * Load some data into these tables, enough such that flushes and compactions start to occur. * Abruptly kill all of the servers. This ensures that there are WALs around. Unfortunately, we can't have any compactions in progress at this point, since that causes a Fate Operation, and that would prevent the upgrade from completing. * Upgrade the bits, start 1.6, and wait for the upgrade steps to finish. * Check for data loss * Trigger some compactions and wait for those to finish. In a previous iteration, we discovered an issue where the relative path'd files and WALs were not being properly deleted from !0. * Check for data loss. * Restart the tablet servers to force tablets to reload (test for orphaned files). * Check for data loss.
We did not try using custom iterators.
Mike On Wed, Jul 30, 2014 at 4:58 PM, Christopher <[EMAIL PROTECTED]> wrote:
Thats fair. We could modify the upgrade code directly.
<div>-------- Original message --------</div><div>From: Sean Busbey <[EMAIL PROTECTED]> </div><div>Date:07/30/2014 9:35 PM (GMT-05:00) </div><div>To: "dev@accumulo apache. org" <[EMAIL PROTECTED]> </div><div>Subject: Re: [DISCUSS] Should we support upgrading 1.4 -> 1.6 w/o going through 1.5? </div><div> </div>On Wed, Jul 30, 2014 at 5:55 PM, <[EMAIL PROTECTED]> wrote: Dave, how is that change related to the changes in ACCUMULO-2988?
I'm all for adding that check. However, it's something we should be doing for all 1.6 upgrades; it isn't a part of adding teh 1.4 -> 1.6 path.
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext