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
Kafka >> mail # user >> Migrating a cluster from 0.8.0 to 0.8.1


Copy link to this message
-
Re: Migrating a cluster from 0.8.0 to 0.8.1
Hi Drew,

That problem will be fixed by
https://issues.apache.org/jira/browse/KAFKA-1074. I think we are close to
checking that in to trunk.

Thanks,
Neha
On Wed, Dec 18, 2013 at 9:02 AM, Drew Goya <[EMAIL PROTECTED]> wrote:

> Thanks Neha, I rolled upgrades and completed a rebalance!
>
> I ran into a few small issues I figured I would share.
>
> On a few Brokers, there were some log directories left over from some
> failed rebalances which prevented the 0.8.1 brokers from starting once I
> completed the upgrade.  These directories contained an index file and a
> zero size log file, once I cleaned those out the brokers were able to start
> up fine.  If anyone else runs into the same problem, and is running RHEL,
> this is the bash script I used to clean them out:
>
> du --max-depth=1 -h /data/kafka/logs | grep K | sed s/.*K.// | sudo rm -r
>
>
> On Tue, Dec 17, 2013 at 10:42 AM, Neha Narkhede <[EMAIL PROTECTED]
> >wrote:
>
> > There are no compatibility issues. You can roll upgrades through the
> > cluster one node at a time.
> >
> > Thanks
> > Neha
> >
> >
> > On Tue, Dec 17, 2013 at 9:15 AM, Drew Goya <[EMAIL PROTECTED]> wrote:
> >
> > > So I'm going to be going through the process of upgrading a cluster
> from
> > > 0.8.0 to the trunk (0.8.1).
> > >
> > > I'm going to be expanding this cluster several times and the problems
> > with
> > > reassigning partitions in 0.8.0 mean I have to move to trunk(0.8.1)
> asap.
> > >
> > > Will it be safe to roll upgrades through the cluster one by one?
> > >
> > > Also are there any client compatibility issues I need to worry about?
> >  Am I
> > > going to need to pause/upgrade all my consumers/producers at once or
> can
> > I
> > > roll upgrades through the cluster and then upgrade my clients one by
> one?
> > >
> > > Thanks in advance!
> > >
> >
>

 
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