[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152523#comment-17152523
]
Stanislav Kozlovski commented on KAFKA-7304:
Given that this Jira is for reporting memory
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863719#comment-16863719
]
chengxl commented on KAFKA-7304:
Hi,Yu Yang..Is there any solution to this memory leak problem in
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767458#comment-16767458
]
Matthias J. Sax commented on KAFKA-7304:
Thanks [~rsivaram] and [~yuyang08]!
> memory leakage in
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765924#comment-16765924
]
Rajini Sivaram commented on KAFKA-7304:
---
[~mjsax] We have fixed all the known memory leak issues.
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16765449#comment-16765449
]
Matthias J. Sax commented on KAFKA-7304:
[~rsivaram] This is marked as "Critical" for 2.2 release
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633793#comment-16633793
]
Rajini Sivaram commented on KAFKA-7304:
---
[~yuyang08] We saw the OOM during a load test, so CPU
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633251#comment-16633251
]
Yu Yang commented on KAFKA-7304:
[~rsivaram] Tested with latest kafka 2.0 branch code, using d2.2x
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633137#comment-16633137
]
Yu Yang commented on KAFKA-7304:
Thanks [~rsivaram]! We will try these fixes and let you know the
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631998#comment-16631998
]
Rajini Sivaram commented on KAFKA-7304:
---
[~yuyang08] We came across a similar issue with large
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602839#comment-16602839
]
Rajini Sivaram commented on KAFKA-7304:
---
[~yuyang08] Thank you. Would it be possible to share the
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602415#comment-16602415
]
Yu Yang commented on KAFKA-7304:
[~rsivaram] Thanks for looking into the issue! We are still
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16599827#comment-16599827
]
ASF GitHub Bot commented on KAFKA-7304:
---
tedyu opened a new pull request #5601: KAFKA-7304 memory
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598306#comment-16598306
]
Yu Yang commented on KAFKA-7304:
We experimented with 1.8.0_171, and did not see obvious improvements on
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596663#comment-16596663
]
Yu Yang commented on KAFKA-7304:
[~yuzhih...@gmail.com] I applied
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595315#comment-16595315
]
Ted Yu commented on KAFKA-7304:
---
[~yuyang08]:
Please confirm that the gap between the following two metrics
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595251#comment-16595251
]
Ted Yu commented on KAFKA-7304:
---
One potential cause for the delayed closing of idle connections is that
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594320#comment-16594320
]
Yu Yang commented on KAFKA-7304:
After more experiments, we currently think that the issue is caused by
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592857#comment-16592857
]
Ted Yu commented on KAFKA-7304:
---
I am looking at SaslSslAdminClientIntegrationTest .
It seems some getter
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592765#comment-16592765
]
Ted Yu commented on KAFKA-7304:
---
Thanks for the feedback, Yu.
There are a few {{log.error()}} calls in the
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592762#comment-16592762
]
Yu Yang commented on KAFKA-7304:
Thanks for looking into this, [~yuzhih...@gmail.com]! We also did more
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592752#comment-16592752
]
Ted Yu commented on KAFKA-7304:
---
In patch v7, I added some assertion to SslTransportLayerTest#teardown
The
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16585392#comment-16585392
]
Ted Yu commented on KAFKA-7304:
---
Selector has {{lowMemThreshold}} which used to determine iteration order.
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584928#comment-16584928
]
Ted Yu commented on KAFKA-7304:
---
Without the fix, the test would fail with:
{code}
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584922#comment-16584922
]
Ted Yu commented on KAFKA-7304:
---
Patch v4 adds an assertion for the count of Channels in closingChannels in
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584894#comment-16584894
]
Ted Yu commented on KAFKA-7304:
---
Through a bit more additional logging, here is what happens to
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584847#comment-16584847
]
Ismael Juma commented on KAFKA-7304:
I raised the priority of this issue until we know what's going
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584843#comment-16584843
]
Ismael Juma commented on KAFKA-7304:
Yes, I was thinking of KAFKA-6529.
> memory leakage in
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1658#comment-1658
]
Ted Yu commented on KAFKA-7304:
---
By running test suite with additional logging, I saw the following:
{code}
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584156#comment-16584156
]
Yu Yang commented on KAFKA-7304:
[~ijuma] We have an internal build that cherry-picks 1.1.1 changes. I
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583780#comment-16583780
]
Ismael Juma commented on KAFKA-7304:
You're seeing this with Kafka 1.1.1? There was a memory leak in
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583748#comment-16583748
]
huxihx commented on KAFKA-7304:
---
[~yuzhih...@gmail.com] The channel was closed in `doClose`.
> memory
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583570#comment-16583570
]
Ted Yu commented on KAFKA-7304:
---
Looking at the close() method, I don't see where the channels in
[
https://issues.apache.org/jira/browse/KAFKA-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583565#comment-16583565
]
Yu Yang commented on KAFKA-7304:
[~yuzhih...@gmail.com] There was no exception in server.log before we
33 matches
Mail list logo
