This OS should be similar to my desktop. Did you try
1. kafka-start-zookeeper
2. kafka-start-server
3. kafka-stop-server
And it does not work for you?
Guozhang
On Mon, Dec 23, 2013 at 2:50 PM, Drew Goya wrote:
> We are running on an Amazon Linux AMI, this is our specific version:
>
> Linux v
Thanks for the help with all this stuff guys!
I completed a rolling upgrade to trunk/b23cf19 and was able to issue a
re-election without any brokers dropping out of the ISR list.
On Mon, Dec 23, 2013 at 8:43 PM, Jun Rao wrote:
> This is probably related to KAFKA-1154. Could you upgrade to the
This is probably related to KAFKA-1154. Could you upgrade to the latest
trunk?
Thanks,
Jun
On Mon, Dec 23, 2013 at 3:21 PM, Drew Goya wrote:
> Hey All, another thing to report for my 0.8.1 migration. I am seeing these
> errors occasionally right after a I run a leader election. This looks t
Hey All, another thing to report for my 0.8.1 migration. I am seeing these
errors occasionally right after a I run a leader election. This looks to
be related to KAFKA-860 as it is the same exception. I see this issue was
closed a while go though and I should be running a commit with the fix in.
We are running on an Amazon Linux AMI, this is our specific version:
Linux version 2.6.32-220.23.1.el6.centos.plus.x86_64 (
mockbu...@c6b5.bsys.dev.centos.org) (gcc version 4.4.6 20110731 (Red Hat
4.4.6-3) (GCC) ) #1 SMP Tue Jun 19 04:14:37 BST 2012
On Mon, Dec 23, 2013 at 11:24 AM, Guozhang Wan
Hi Drew,
I tried the kafka-server-stop script and it worked for me. Wondering which
OS are you using?
Guozhang
On Mon, Dec 23, 2013 at 10:57 AM, Drew Goya wrote:
> Occasionally I do have to hard kill brokers, the kafka-server-stop.sh
> script stopped working for me a few months ago. I saw an
Occasionally I do have to hard kill brokers, the kafka-server-stop.sh
script stopped working for me a few months ago. I saw another thread in
the mailing list mentioning the issue too. I'll change the signal back to
SIGTERM and run that way for a while, hopefully the problem goes away.
This is t
Are you hard killing the brokers? And is this issue reproducible?
On Sat, Dec 21, 2013 at 11:39 AM, Drew Goya wrote:
> Hey guys, another small issue to report for 0.8.1. After a couple days 3
> of my brokers had fallen off the ISR list for a 2-3 of their partitions.
>
> I didn't see anything u
Hey guys, another small issue to report for 0.8.1. After a couple days 3
of my brokers had fallen off the ISR list for a 2-3 of their partitions.
I didn't see anything unusual in the log and I just restarted one. It came
up fine but as it loaded its logs I these messages showed up:
[2013-12-21
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 wrote:
> Thanks Neha, I rolled upgrades and completed a rebalance!
>
> I ran into a few small iss
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
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 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
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 cl
13 matches
Mail list logo
