ot, you are going to have to remove it through the shell or executor
>or
>however you reliably and safely do that.
>
>Re-run the command again.
>
>I created a JIRA for this https://issues.apache.org/jira/browse/KAFKA-1665
>issue once we can reproduce it we should fix it.
>
>
broker host with a new one,
>>instead
>> of
>> > using the reassign partition tool, simply start a new broker with the
>> same
>> > broker id as the old one, the new broker will replicate all the data
>> > automatically.
>> >
>> >
Hi All,
I had a 0.8.1.1 Kafka Broker go down, and I was trying to use the reassign
partition script to move topics off that broker. When I describe the topics, I
see the following:
Topic: mini__022active_120__33__mini Partition: 0 Leader: 2131118 Replicas:
2131118,2166601,2163421 Isr: 2131
;
>Jun
>
>
>On Wed, Jul 9, 2014 at 9:59 AM, Lung, Paul wrote:
>
>> Yup. In fact, I just ran the test program again while the Kafak broker
>>is
>> still running, using the same user of course. I was able to get up to
>>10K
>> connections with the test
Kafka broker machine can handle before it gives me the
³Too Many Open Files² error and eventually crashes.
Paul Lung
On 7/8/14, 9:29 PM, "Jun Rao" wrote:
>Does your test program run as the same user as Kafka broker?
>
>Thanks,
>
>Jun
>
>
>On Tue, Jul 8,
Hit the send button too fast. I verified the number of open file
descriptors from the broker by using ³sudo lsof -p², and by using ³sudo ls
-l /proc//fd | wc -l².
Paul
On 7/8/14, 1:42 PM, "Lung, Paul" wrote:
>Hi Guys,
>
>I¹m seeing the following errors from the 0.8.1.1 broke
Hi Guys,
I’m seeing the following errors from the 0.8.1.1 broker. This occurs most often
on the Controller machine. Then the controller process crashes, and the
controller bounces to other machines, which causes those machines to crash.
Looking at the file descriptors being held by the process,
t;
>
>On Tue, Jul 8, 2014 at 10:29 AM, Lung, Paul wrote:
>
>> Hi All,
>>
>>
>> I¹m seeing the following issues after running a Kafka broker cluster
>>for 2
>> months:
>>
>>
>> [2014-07-07 17:54:19,798] ERROR Conditional update of path
Hi All,
I’m seeing the following issues after running a Kafka broker cluster for 2
months:
[2014-07-07 17:54:19,798] ERROR Conditional update of path
/brokers/topics/mini__065active_80__32__miniactiveitembrn_chd_qn/partitions/0/state
with data
{"controller_epoch":9,"leader":2129087,
not get elected as the leader. Have
>you seen a case where such a broker became the leader? Could you elaborate
>more on the type of failure that you describe?
>
>
>
>
>On Tue, Jun 24, 2014 at 6:20 PM, Lung, Paul wrote:
>
>> Hi All,
>>
>> Is there anyway to
Hi Prakash,
How many open files do you expect a broker to be able to handle? It seems
like this broker is crashing at around 4100 or so open files.
Thanks,
Paul Lung
On 6/24/14, 11:08 PM, "Lung, Paul" wrote:
>Ok. What I just saw was that when the controller machine reaches around
Ok. What I just saw was that when the controller machine reaches around
4100+ files, it crashes. Then I think the controller bounced between 2
other machines, taking them down too, and the circled back to the original
machine.
Paul Lung
On 6/24/14, 10:51 PM, "Lung, Paul" wrote:
>T
The controller machine has 3500 or so, while the other machines have
around 1600.
Paul Lung
On 6/24/14, 10:31 PM, "Prakash Gowri Shankor"
wrote:
>How many files does each broker itself have open ? You can find this from
>'ls -l /proc//fd'
>
>
>
>
>On
Hi All,
I just upgraded my cluster from 0.8.1 to 0.8.1.1. I’m seeing the following
error messages on the same 3 brokers once in a while:
[2014-06-24 21:43:44,711] ERROR Error in acceptor (kafka.network.Acceptor)
java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChann
Hi All,
Is there anyway to blacklist brokers? Sometimes we run into situations where
there are certain hardware failures on a broker machine, and the machines goes
into a “half dead” state. The broker process is up and participating in the
cluster, but it can’t actually transmit messages proper
artition
>reassignment?
>
>Thanks,
>Neha
>On Jun 23, 2014 5:16 PM, "Lung, Paul" wrote:
>
>> Hi All,
>>
>> First, I¹m using 0.8.1. Is there anyway to cancel an ongoing
>> kafka-reassign-partitions job? I started a reassignment, and for so
Hi All,
Is there anyway to move a topic by force, even if it means loss of
messages? The problem I¹m looking at is the loss of multiple Kafka brokers
simultaneously in a Kafka cluster, which means that all replicas and
leader is lost. Under these circumstances, is there any way to forcibly
move th
Hi All,
First, I¹m using 0.8.1. Is there anyway to cancel an ongoing
kafka-reassign-partitions job? I started a reassignment, and for some
reason it just takes forever. However, it won¹t let me start another
reassignment job while this one is running. So is there a way to just
cancel it?
Thank yo
Hi Guys,
I’m using Kafka 0.8.1, and I’m having difficulty trying to move a replica from
one broker to another.
Doing a "kafka-topics.sh —describe | grep mini__078active_80__32__mini"
shows:
Topic:mini__078active_80__32__mini PartitionCount:1 ReplicationFactor:3
Configs:retention.byte
19 matches
Mail list logo