someone can help to analysis it？
> 在 2017年11月10日，上午11:08，Json Tu 写道：
>
> I‘m so sorry for my poor english.
>
> what I really means is my broker machine is configured as 8 core 16G. but my
> jvm configure is as below.
> java -Xmx1G -Xms1G -server -XX:+UseG1GC -X
写道：
>
> Seems broker `4759750` was always removed for partition [Yelp, 5] every round
> of ISR shrinking. Did you check if everything works alright for this broker?
>
>
> 发件人: Json Tu
> 发送时间: 2017年11月10日 11:08
> 收件人: us...@kafka.apache.org
> 抄送: dev@kafka.apache.org;
suggestions.
> 在 2017年11月9日，下午9:59，John Yost 写道：
>
> I've seen this before and it was due to long GC pauses due in large part to
> a memory heap > 8 GB.
>
> --John
>
> On Thu, Nov 9, 2017 at 8:17 AM, Json Tu wrote:
>
>> Hi,
>>we have a kafka clus
Hi,
we have a kafka cluster which is made of 6 brokers, with 8 cpu and 16G
memory on each broker’s machine, and we have about 1600 topics in the
cluster，about 1700 partitions’ leader and 1600 partitions' replica on each
broker.
when we restart a normal broke, we find that there are 500
Hi all，
we have a cluster with 10 brokers, and our kafka version is 0.9.0.1，we
repeatedly get our metric data such as offlinePartition metric from each broker
with 2 minutes gap to achieve the goal of cluster’s monitor.
but accidental timeout occurs when we get data from some of brokers.
Hi all，
We are now using kafka 0.9.0 in our product enviroment, and we add one
broker to the cluster，and execute reassign partitions between all brokers，we
find our network card and disk io is very high.
and I know KIP-73 has resolved this problem, but I wonder can I merge it to my
kafk
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu resolved KAFKA-4447.
Resolution: Fixed
> Controller resigned but it also acts as a controller for a long t
Would be grateful to hear opinions from experts out there. Thanks in advance
> 在 2016年12月16日，下午6:17，Json Tu 写道：
>
> Hi all,
> we have a cluster of 0.9.0.0 with 3 nodes, we have a topic with 3
> replicas, and send it with ack -1, our sending latency is avg 7ms. I prepare
Hi all,
we have a cluster of 0.9.0.0 with 3 nodes, we have a topic with 3
replicas, and send it with ack -1, our sending latency is avg 7ms. I prepare to
optimize performance of cluster through adjusting some params.
we find our brokers has set config item as below,
log.flush.inte
Hi,
Can someone else help to review the pr in jira:
https://issues.apache.org/jira/browse/KAFKA-4447
<https://issues.apache.org/jira/browse/KAFKA-4447>.
> 在 2016年11月23日，下午11:28，Json Tu 写道：
>
> Hi,
> We have a cluster of kafka 0.9.0.1 with 3 nodes, and
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702384#comment-15702384
]
Json Tu edited comment on KAFKA-4447 at 12/1/16 6:2
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711052#comment-15711052
]
Json Tu commented on KAFKA-4447:
[~hachikuji] could you help review it，th
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4447:
---
Comment: was deleted
(was: [~wangg...@gmail.com] thank you for such a detailed analysis .
as you
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703688#comment-15703688
]
Json Tu commented on KAFKA-4447:
[~wangg...@gmail.com] thank you for such a deta
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703687#comment-15703687
]
Json Tu commented on KAFKA-4447:
[~wangg...@gmail.com] thank you for such a deta
thanks to Jason Gustafson, hope more contributor can take part in this
discussion.
https://issues.apache.org/jira/browse/KAFKA-4447
<https://issues.apache.org/jira/browse/KAFKA-4447>
> 在 2016年11月27日，下午9:20，Json Tu 写道：
>
> AnyBody？This is very disconcerting! If convenient, Can s
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702465#comment-15702465
]
Json Tu commented on KAFKA-4447:
may be the phenomenon of these listener is the sam
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702384#comment-15702384
]
Json Tu edited comment on KAFKA-4447 at 11/28/16 4:4
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702384#comment-15702384
]
Json Tu edited comment on KAFKA-4447 at 11/28/16 4:4
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4447:
---
Comment: was deleted
(was: [~skarface] thanks for your reply.
the latest release version 0.10.1.0
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702384#comment-15702384
]
Json Tu edited comment on KAFKA-4447 at 11/28/16 4:2
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702383#comment-15702383
]
Json Tu commented on KAFKA-4447:
[~skarface] thanks for your reply.
the latest rel
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702384#comment-15702384
]
Json Tu commented on KAFKA-4447:
[~skarface] thanks for your reply.
the latest rel
AnyBody？This is very disconcerting! If convenient, Can somebody help to confirm
this strange question.
> 在 2016年11月26日，上午1:35，Json Tu 写道：
>
> thanks guozhang,
> if it's convenient，can we disscuss it in the jira
> https://issues.apache.org/jira/browse/
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696353#comment-15696353
]
Json Tu edited comment on KAFKA-4447 at 11/26/16 1:17 AM:
--
a
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696340#comment-15696340
]
Json Tu edited comment on KAFKA-4447 at 11/26/16 1:16 AM:
--
a
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696353#comment-15696353
]
Json Tu edited comment on KAFKA-4447 at 11/25/16 5:40 PM:
--
a
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696353#comment-15696353
]
Json Tu edited comment on KAFKA-4447 at 11/25/16 5:39 PM:
--
a
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696340#comment-15696340
]
Json Tu edited comment on KAFKA-4447 at 11/25/16 5:38 PM:
--
a
ontinuously see broker
> 100's listener fires and it acts like a controller then there may be an
> issue with 0.9.0.1 version.
>
> Guozhang
>
> On Wed, Nov 23, 2016 at 7:28 AM, Json Tu wrote:
>
>> Hi,
>>We have a cluster of kafka 0.9.0.1 with 3 nodes
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4447:
---
Reviewer: Guozhang Wang
> Controller resigned but it also acts as a controller for a long t
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696340#comment-15696340
]
Json Tu edited comment on KAFKA-4447 at 11/25/16 5:27 PM:
--
a
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696353#comment-15696353
]
Json Tu commented on KAFKA-4447:
after review the code of kafka 0.9.0.0 and some
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696340#comment-15696340
]
Json Tu commented on KAFKA-4447:
after check the email's response in the dev&#x
[
https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4447:
---
Attachment: log.tar.gz
I upload the log's tar, we can unzip it using tar tools
> Controller resigne
Json Tu created KAFKA-4447:
--
Summary: Controller resigned but it also acts as a controller for
a long time
Key: KAFKA-4447
URL: https://issues.apache.org/jira/browse/KAFKA-4447
Project: Kafka
Hi,
We have a cluster of kafka 0.9.0.1 with 3 nodes, and we found a strange
controller log as below.
[2016-11-07 03:14:48,575] INFO [SessionExpirationListener on 100], ZK expired;
shut down all controller components and try to re-elect
(kafka.controller.KafkaController$SessionExpiration
Hi, when I move __consumer_offsets from old broker to new broker, we encounter
error as follow and it always shuabing.
server.log.2016-11-07-19:[2016-11-07 19:17:15,392] ERROR Found invalid messages
during fetch for partition [__consumer_offsets,10] offset 13973569 error
Message found with corru
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631474#comment-15631474
]
Json Tu commented on KAFKA-4360:
I'm sorry, I rollback one comment commit, a
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4360:
---
Reviewer: Jiangjie Qin (was: Json Tu)
> Controller may deadLock when autoLeaderRebalance encounter
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15625317#comment-15625317
]
Json Tu edited comment on KAFKA-4360 at 11/1/16 12:38 PM:
--
I
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15625317#comment-15625317
]
Json Tu commented on KAFKA-4360:
I put a pull request：https://github.com/apache/k
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624461#comment-15624461
]
Json Tu edited comment on KAFKA-4360 at 11/1/16 6:22 AM:
-
i
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4360:
---
Reviewer: Json Tu
> Controller may deadLock when autoLeaderRebalance encounter zk expi
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624461#comment-15624461
]
Json Tu edited comment on KAFKA-4360 at 11/1/16 5:57 AM:
-
i
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624461#comment-15624461
]
Json Tu edited comment on KAFKA-4360 at 11/1/16 5:50 AM:
-
i
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624461#comment-15624461
]
Json Tu edited comment on KAFKA-4360 at 11/1/16 5:49 AM:
-
i
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624461#comment-15624461
]
Json Tu commented on KAFKA-4360:
it is wonderful，I search onControllerResignation(
//issues.apache.org/jira/browse/KAFKA-4360
>> Project: Kafka
>> Issue Type: Bug
>> Components: controller
>> Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1
>> Reporter: Json Tu
>> Labels
Key: KAFKA-4360
>> URL: https://issues.apache.org/jira/browse/KAFKA-4360
>> Project: Kafka
>>Issue Type: Bug
>>Components: controller
>> Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0, 0.10.0.1
>>
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4360:
---
Comment: was deleted
(was: add a deadlock_patch to kafka.)
> Controller may deadLock w
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4360:
---
Attachment: deadlock_patch
add a deadlock_patch to kafka.
> Controller may deadLock when autoLeaderRebala
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624174#comment-15624174
]
Json Tu edited comment on KAFKA-4360 at 11/1/16 3:04 AM:
-
ye
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624174#comment-15624174
]
Json Tu edited comment on KAFKA-4360 at 11/1/16 3:04 AM:
-
y
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624174#comment-15624174
]
Json Tu commented on KAFKA-4360:
yes，I think we should add a AtomicBoolean variable
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4360:
---
Description:
when controller has checkAndTriggerPartitionRebalance task in
autoRebalanceScheduler，and then
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4360:
---
Attachment: yf-mafka2-common02_jstack.txt
the jstack file created when kill kafka
> Controller may deadL
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622377#comment-15622377
]
Json Tu commented on KAFKA-4360:
[~guozhang] [~junrao] do you think this is may be a
[
https://issues.apache.org/jira/browse/KAFKA-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Json Tu updated KAFKA-4360:
---
Description:
when controller has checkAndTriggerPartitionRebalance task in
autoRebalanceScheduler，and then
Json Tu created KAFKA-4360:
--
Summary: Controller may deadLock when autoLeaderRebalance
encounter zk expired
Key: KAFKA-4360
URL: https://issues.apache.org/jira/browse/KAFKA-4360
Project: Kafka
Hi all,
We have a kafka cluster with 11 nodes, and we found there are some
partition’s replica num is not equal to isr’s num，because our data traffic is
small，we think it should isr’s num should equal to replica’s num at last，
but it can not recovery to normal，so we try to shutdown a brok
epeated error log entries since it should at most print one entry (and
> should be DEBUG not ERROR) for each delayed request whose partition leaders
> have migrated out.
>
>
>
> Guozhang
>
>
>
> On Wed, Oct 26, 2016 at 7:46 AM, Json Tu wrote:
>
>> it make t
[
https://issues.apache.org/jira/browse/KAFKA-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608708#comment-15608708
]
Json Tu commented on KAFKA-3536:
Thank you，But I think I can’t ignore it，because it
in this request may not be
completely be satisfied and return to the fetch broker，
which leads some producer and consumer fail for a longtime，I don’t know is it
correct
> 在 2016年10月25日，下午8:32，Json Tu 写道：
>
> Hi all,
> I use Kafka 0.9.0.0, and we have a cluster with 6 nodes, when
Hi all,
I use Kafka 0.9.0.0, and we have a cluster with 6 nodes, when I restart
a broker，we find there are many logs as below，
[2016-10-24 15:29:00,914] ERROR [KafkaApi-2141642] error when handling request
Name: FetchRequest; Version: 1; CorrelationId: 4928; ClientId:
ReplicaFetcherThre
Thanks. I patch it, and everything goes ok.
> 在 2016年10月9日，下午12:39，Becket Qin 写道：
>
> Can you check if you have KAFKA-3003 when you run the code?
>
> On Sat, Oct 8, 2016 at 12:52 AM, Kafka wrote:
>
>> Hi all,
>>we found our consumer have high cpu load in our product
>> enviroment，as we
Hi all,
I have a kafka 0.9.0.0 cluster with 11 nodes.
First,I found server logs as below，
server.log.2016-10-17-22:[2016-10-17 22:22:13,885] WARN
[ReplicaFetcherThread-0-4], Error in fetch
kafka.server.ReplicaFetcherThread$FetchRequest@367c9f98. Possible cause:
org.apache.kafka.common.pr
67 matches
Mail list logo
