Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> [DISCUSS] Should we support upgrading 1.4 -> 1.6 w/o going through 1.5?


Copy link to this message
-
Re: [DISCUSS] Should we support upgrading 1.4 -> 1.6 w/o going through 1.5?
We initially tried to set it up as a stand-alone utility but eventually
gave up. In order to properly do the upgrade, you concurrently need to run
whatever upgrade code concurrently with a tablet server hosting !METADATA
and a tablet server that can replay WALs. We ended up duplicating a lot of
logic already present in master before scrapping that plan. An alternative
would have been to try to build on MAC, but that was also non-trivial to
deploy, so we spliced the code into the existing upgrade path. How do you
feel about that, Drew?
On Tue, Jun 17, 2014 at 8:57 PM, Drew Farris <[EMAIL PROTECTED]> wrote:
 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB