[
https://issues.apache.org/jira/browse/KAFKA-16229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justine Olshan resolved KAFKA-16229.
Resolution: Fixed
> Slow expiration of Producer IDs leading to high CPU us
Jorge Esteban Quilcate Otoya created KAFKA-16229:
Summary: Slow expiration of Producer IDs leading to high CPU usage
Key: KAFKA-16229
URL: https://issues.apache.org/jira/browse/KAFKA-16229
xiaotong.wang created KAFKA-15796:
-
Summary: High CPU issue in Kafka Producer when Auth Failed
Key: KAFKA-15796
URL: https://issues.apache.org/jira/browse/KAFKA-15796
Project: Kafka
Issue
Gaurav Narula created KAFKA-15141:
-
Summary: High CPU usage with log4j2
Key: KAFKA-15141
URL: https://issues.apache.org/jira/browse/KAFKA-15141
Project: Kafka
Issue Type: Improvement
gdd sop created KAFKA-14045:
---
Summary: Heartbeat threads cause high CPU usage after broker shut
down
Key: KAFKA-14045
URL: https://issues.apache.org/jira/browse/KAFKA-14045
Project: Kafka
Issue
Gunnar Morling created KAFKA-12801:
--
Summary: High CPU load after restarting brokers subsequent to
quorum loss
Key: KAFKA-12801
URL: https://issues.apache.org/jira/browse/KAFKA-12801
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-10134:
-
> High CPU issue during rebalance in Kafka consumer after upgrading to
[
https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-10134.
---
Resolution: Fixed
> High CPU issue during rebalance in Kafka consumer after upgrading
Sean Guo created KAFKA-10134:
Summary: High CPU issue during rebalance in Kafka consumer after
upgrading to 2.5
Key: KAFKA-10134
URL: https://issues.apache.org/jira/browse/KAFKA-10134
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evan Williams resolved KAFKA-9963.
--
Resolution: Abandoned
> High CPU during replication of replaced (empty) bro
Evan Williams created KAFKA-9963:
Summary: High CPU
Key: KAFKA-9963
URL: https://issues.apache.org/jira/browse/KAFKA-9963
Project: Kafka
Issue Type: Bug
Components: core
li xiangyuan created KAFKA-9646:
---
Summary: kafka consumer cause high cpu usage
Key: KAFKA-9646
URL: https://issues.apache.org/jira/browse/KAFKA-9646
Project: Kafka
Issue Type: Improvement
Yu Yang created KAFKA-7364:
--
Summary: kafka periodically run into high cpu usage with ssl
writing
Key: KAFKA-7364
URL: https://issues.apache.org/jira/browse/KAFKA-7364
Project: Kafka
Issue Type
https://issues.apache.org/jira/browse/KAFKA-3159
Also in version 1.0.0 - and doing sleep between pools is heartly a
reasonable workaround. any fixes upcoming ?
Peter
you think the issue still exists
> High CPU in very active environment
> ---
>
> Key: KAFKA-1636
> URL: https://issues.apache.org/jira/browse/KAFKA-1636
> Project: Kafka
> Issue Type:
Sebastian Bernauer created KAFKA-5766:
-
Summary: Very high CPU-load of consumer when broker is down
Key: KAFKA-5766
URL: https://issues.apache.org/jira/browse/KAFKA-5766
Project: Kafka
r
1:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is
not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
> High CPU util on broker
> ---
>
> Key: KAFKA-3900
> URL: https://iss
r
1:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is
not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
> High CPU util on broker
> ---
>
> Key: KAFKA-3900
> URL: https://issues.apa
r
1:org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is
not the leader for that topic-partition. (kafka.server.ReplicaFetcherThread)
> High CPU util on broker
> ---
>
> Key: KAFKA-3900
> URL: https://issues.apa
tion. (kafka.server.ReplicaFetcherThread)
> High CPU util on broker
> ---
>
> Key: KAFKA-3900
> URL: https://issues.apache.org/jira/browse/KAFKA-3900
> Project: Kafka
> Issue Type: Bug
> Components: network, repli
was a fix in the code appearing in
the stacktrace.
> High CPU util on broker
> ---
>
> Key: KAFKA-3900
> URL: https://issues.apache.org/jira/browse/KAFKA-3900
> Project: Kafka
> Issue Type: Bug
>
[
https://issues.apache.org/jira/browse/KAFKA-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3900:
---
Labels: reliability (was: )
> High CPU util on bro
instance down terminating
it on AWS:
After putting down one Kafka instance, the leadership of partitions it was
a leader for was transferred to other nodes. All nodes increased their cpu
usage and one of them started consuming around 100% cpu. Restarts of that
node does not help because high cpu usage
AM, Kafka wrote:
> >
> >> Hi all,
> >>we found our consumer have high cpu load in our product
> >> enviroment，as we know，fetch.min.bytes and fetch.wait.ma <
> >> http://fetch.wait.ma/>x.ms will affect the frequency of consumer’s
>
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 i
[
https://issues.apache.org/jira/browse/KAFKA-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-4290:
-
Fix Version/s: 0.10.2.0
> High CPU caused by timeout overflow
[
https://issues.apache.org/jira/browse/KAFKA-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-4290.
--
Resolution: Fixed
Reviewer: Ewen Cheslack-Postava
> High CPU caused
uest at:
https://github.com/apache/kafka/pull/2009
> High CPU caused by timeout overflow in WorkerCoordinator
>
>
> Key: KAFKA-4290
> URL: https://issues.apache.org/jir
ason Gustafson
Date: 2016-10-11T04:27:45Z
KAFKA-4290: Fix timeout overflow in WorkerCoordinator.poll
> High CPU caused by timeout overflow in WorkerCoordinator
>
>
> Key: KAFKA-4290
>
Jason Gustafson created KAFKA-4290:
--
Summary: High CPU caused by timeout overflow in WorkerCoordinator
Key: KAFKA-4290
URL: https://issues.apache.org/jira/browse/KAFKA-4290
Project: Kafka
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 know，fetch.min.bytes and fetch.wait.ma <
> http://fetch.wait.ma/>x.
Hi all,
we found our consumer have high cpu load in our product enviroment，as
we know，fetch.min.bytes and fetch.wait.ma <http://fetch.wait.ma/>x.ms will
affect the frequency of consumer’s return，
so we adjust them to very big so that broker is very hard to satisfy it.
t
afka 0.9.0, CPU around around 90%,
replication cannot catch up due to disconnection errors.
> High CPU util on broker
> ---
>
> Key: KAFKA-3900
> URL: https://issues.apache.org/jira/browse/KAFKA-3900
> Project: Kafka
we have a 5 node kafka cluster, 4 of the 5 nodes
have CPU around 65% but one is persistently pegged at 100%. We get the same
exception as above and see frequent shrink / expands on the ISRs. Also on AWS
w/ Amazon Linux.
> High CPU util on broker
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Konyaev updated KAFKA-3900:
--
Component/s: replication
network
> High CPU util on bro
[
https://issues.apache.org/jira/browse/KAFKA-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Konyaev updated KAFKA-3900:
--
Affects Version/s: 0.10.0.0
> High CPU util on bro
[
https://issues.apache.org/jira/browse/KAFKA-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350909#comment-15350909
]
Andrey Konyaev commented on KAFKA-3900:
---
Any comments?
> High CPU util on
Andrey Konyaev created KAFKA-3900:
-
Summary: High CPU util on broker
Key: KAFKA-3900
URL: https://issues.apache.org/jira/browse/KAFKA-3900
Project: Kafka
Issue Type: Bug
Environment
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292319#comment-15292319
]
Manoj Ramakrishnan commented on KAFKA-493:
--
Thanks!
> High CPU u
] We are using the Oracle JVM 1.8 (1.8.0_65
to be specific) in production.
However, after the 0.9.0.1 upgrade this didn't reproduce at all (just checked
the infra monitoring this evening and is fairly flat ever since).
Hope this helps.
> High CPU usage on ina
you running on ?
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
> Components: core
0.8 and also in 0.9.0.1 (latest
release). We have been able to narrow it down a bit which I've have explained
and asked for inputs in this mail on the user list
http://mail-archives.apache.org/mod_mbox/kafka-users/201604.mbox/%3C571F23ED.7050405%40gmail.com%3E
> High CPU usage on ina
d others are not occurred this.
the brokers config is same,but we add:
replica.fetch.wait.max.ms=100
num.replica.fetchers=2
I want to question does is the main reason, or have other reason that leads to
high cpu load?
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210094#comment-15210094
]
Ismael Juma commented on KAFKA-493:
---
Thanks for reporting back Cosmin.
> High CP
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cosmin Marginean updated KAFKA-493:
---
Attachment: 0.9.0.1-upgrade.png
> High CPU usage on inactive ser
ver a week now and none of
the CPU issues are present anymore (See 0.9.0.1-upgrade.png. I will make sure
to update this if it regresses.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues
n running 0.9.0.1 for over a week now and none of
the CPU issues are present anymore (See 0.9.0.1-upgrade.png. I will make sure
to update this if it regresses.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
>
to delete all data
on one node as I thought it's caused by corrupted message data, but it didn't
work.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse
eper cannot see it.
but in another 0.8.2.2 cluster, everything is fine. I tried to delete all data
on one node as I thought it's caused by corrupted message data, but it didn't
work.
> High CPU usage on inactive server
> -
>
>
next few weeks.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
> Components
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-493:
--
Fix Version/s: (was: 0.10.1.0)
> High CPU usage on inactive ser
g to 0.9.0.1 which was just released
last week. It has a couple of bug fixes (KAFKA-3159 and KAFKA-3003) that may be
applicable.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.or
high when there's no activity on any of
the topics.
Is there any other JIRA ticket that has followed up on this separately?
FYI, using 0.9.0.0
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: h
tive for a while but I can confirm that I met
similar conditions (high number of partitions - 256 per topic) and get a high
CPU usage, but only while having producers/consumers wired. As soon as I
shutdown the client apps, CPU usage goes considerably low. Just wanted to know
if this is related o
onsumer of CPU via:
ps -L -p
3) Convert the LWP column to hex and then look for that value in the
thread dump on the "nid=0x.." field of each thread.
Cheers!
Brock
On Thu, Sep 17, 2015 at 3:58 PM, Jaikiran Pai wrote:
That's a good point, I missed that. Is there any other way to
You can enable profiling in tools like jvisualvm and see which methods
other select() show up high.
Thanks,
Jun
On Thu, Sep 17, 2015 at 5:58 PM, Jaikiran Pai
wrote:
> That's a good point, I missed that. Is there any other way to track down
> why it would consume this high CPU whe
at 3:58 PM, Jaikiran Pai wrote:
> That's a good point, I missed that. Is there any other way to track down why
> it would consume this high CPU when it's idle? I can send the thread dumps
> (taken at intervals of a few seconds of each other), but each of them has
> not much inter
That's a good point, I missed that. Is there any other way to track down
why it would consume this high CPU when it's idle? I can send the thread
dumps (taken at intervals of a few seconds of each other), but each of
them has not much interesting (IMO) than these specific repeated
s
eeping aside that part for a while, we have been noticing that
>> even when the system/application is completely idle, the Kafka process
>> seems to take up unreasonably high CPU (10-15% constantly shown in top
>> command). We have taken multiple thread dumps and each of them hav
ping aside that part for a while, we have been noticing
that even when the system/application is completely idle, the Kafka
process seems to take up unreasonably high CPU (10-15% constantly
shown in top command). We have taken multiple thread dumps and each of
them have this:
"kafka-socke
d of figured it out from the kafka git repo.
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues.apache.org/jira/browse/KAFKA-1952
> Project: Kafka
> Issue Type: Bug
>
ways committed to the 0.8.2 branch.
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues.apache.org/jira/browse/KAFKA-1952
> Project: Kafka
> Issue Type: Bug
>
inst kafka 8.2 source? I am not sure since kafka
8.2 source doesn't have any file matching this path i.e
'/core/src/main/scala/kafka/server/DelayedOperation.scala'
Thanks,
Puneet Mehta
> High CPU Usage in 0.8.2 release
> ---
>
>
0.8.2.1 and trunk.
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues.apache.org/jira/browse/KAFKA-1952
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.8.2
d to end latency with the
patch is comparable to those in 0.8.2.
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues.apache.org/jira/browse/KAFKA-1952
> Project: Kafka
>
1150/diff/
against branch origin/trunk
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues.apache.org/jira/browse/KAFKA-1952
> Project: Kafka
> Issue Type: Bug
>
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Attachment: kafka-1952.patch
> High CPU Usage in 0.8.2 rele
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Fix Version/s: (was: 0.8.2.0)
0.8.2.1
> High CPU Usage in 0.8.2 rele
and replica fetcher (both at 500ms), which is expected.
Also measured the localTime and sendTime for the same replica fetch requests on
0.8.1.1. The numbers are comparable with 0.8.2.0 with the patch.
> High CPU Usage in 0.8.2 release
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Attachment: kafka-1952_2015-02-15_15:26:33.patch
> High CPU Usage in 0.8.2 rele
1040/diff/
against branch origin/0.8.2
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues.apache.org/jira/browse/KAFKA-1952
> Project: Kafka
> Issue Type: Bug
>
1040/diff/
against branch origin/0.8.2
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues.apache.org/jira/browse/KAFKA-1952
> Project: Kafka
> Issue Type: Bug
>
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Status: Patch Available (was: Open)
> High CPU Usage in 0.8.2 rele
urning the CPU. This issue seems to only happen
in a cluster when there is no data being produced.
Attach a patch that addresses the issue.
> High CPU Usage in 0.8.2 release
> ---
>
> Key: KAFKA-1952
> URL: https://issues
[
https://issues.apache.org/jira/browse/KAFKA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1952:
---
Attachment: kafka-1952.patch
> High CPU Usage in 0.8.2 rele
Jay Kreps created KAFKA-1952:
Summary: High CPU Usage in 0.8.2 release
Key: KAFKA-1952
URL: https://issues.apache.org/jira/browse/KAFKA-1952
Project: Kafka
Issue Type: Bug
Affects Versions
ptly delete this message and notify the sender of the
delivery error by e-mail or you may call Cerner's corporate offices in Kansas
City, Missouri, U.S.A at (+1) (816)221-1024.
> High CPU usage on inactive server
> -
>
>
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-493.
-
Resolution: Incomplete
> High CPU usage on inactive ser
you include the top few
methods?
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
> C
9 AM:
This is a production high CPU usage snapshot. We used similar amount of traffic
comparing to Kafka 7. Kafka 7 performs at around 10-30%, Kafka 8 (0.8.1.1) hit
at 50%-90%.
Attached file name: Kafka-2014-11-10.snapshot.zip
was (Author: activars):
This is a production high CPU usage snapshot
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Dong updated KAFKA-493:
Attachment: Kafka-2014-11-10.snapshot.zip
This is a production high CPU usage snapshot. We used similar
9 PM:
--
[~smeder] Thanks for the response - do you remember what's the Java class entry
used for hprof?
was (Author: activars):
[~smeder] Thanks for the response - do you remember what's the class entry used
the hprof?
> High CPU usage o
mber what's the class entry used
the hprof?
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: B
been too long
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
> Compone
can provide a similar CPU
profiling result to see if we are having the same issue or it could be
happening in multiple places.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apa
Laurie Turner created KAFKA-1636:
Summary: High CPU in very active environment
Key: KAFKA-1636
URL: https://issues.apache.org/jira/browse/KAFKA-1636
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-493:
Fix Version/s: (was: 0.8.2)
0.9.0
> High CPU usage on inactive ser
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122100#comment-14122100
]
Guozhang Wang commented on KAFKA-493:
-
Moving the fix of 2) to 0.9
> High CP
yet fixed) in KAFKA-1150
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
> C
till exists.
2. The second issue was that when the fetcher disconnects we don't proactively
purge any asynchronous requests it has. So very long timeouts combined with a
consumer with high error rate can accumulate memory.
> High CPU usage on ina
producer performance? With a large number of partitions being replicated, it
seems like a configuration change that might be beneficial.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apac
he fix in KAFKA_1356?
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
> Components:
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Olson updated KAFKA-493:
---
Attachment: backtraces.txt
> High CPU usage on inactive ser
taching stack trace.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
> Componen
e to follower fetch requests. Can
you confirm that in your broker request logs?
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
here is no traffic
to the broker.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.apache.org/jira/browse/KAFKA-493
> Project: Kafka
> Issue Type: Bug
&g
this appears to have already been fixed in trunk/0.8.1.1 by
KAFKA-1356 by changing the metadata cache from a Map
[TopicAndPartition,PartitionStateInfo] to a Map[Topic, Map[Partition,
PartitionStateInfo]].
> High CPU usage on inactive server
> -
>
>
.zip
Also attaching sampling-based profiling data, since the tracing-based profiling
data may be a bit skewed due to the trace overhead.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
> URL: https://issues.
for profiling, trace snapshot files
are attached. Will post a summary of my findings later this morning. The
epollWait does not appear to be a problem.
> High CPU usage on inactive server
> -
>
> Key: KAFKA-493
>
[
https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Olson updated KAFKA-493:
---
Attachment: Kafka-trace1.zip
Kafka-trace2.zip
Kafka-trace3.zip
> H
1 - 100 of 113 matches
Mail list logo
