[
https://issues.apache.org/jira/browse/KAFKA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-17188:
---
Summary: LoginManager ctor might throw an exception causing login and
loginCallbackHandler not
Philip Nee created KAFKA-17188:
--
Summary: LoginManager ctro might throw an exception causing login
and loginCallbackHandler not being closed properly
Key: KAFKA-17188
URL:
[
https://issues.apache.org/jira/browse/KAFKA-14648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-14648:
--
Assignee: Brenden DeLuna (was: Philip Nee)
> Do not fail clients if bootstrap servers is
[
https://issues.apache.org/jira/browse/KAFKA-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-13421:
---
Priority: Major (was: Blocker)
> Fix
>
[
https://issues.apache.org/jira/browse/KAFKA-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854404#comment-17854404
]
Philip Nee commented on KAFKA-13421:
the test is disabled, can we make this non-blocker?
> Fix
>
[
https://issues.apache.org/jira/browse/KAFKA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16160.
Resolution: Cannot Reproduce
> AsyncKafkaConsumer is trying to connect to a disconnected node in
[
https://issues.apache.org/jira/browse/KAFKA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848748#comment-17848748
]
Philip Nee commented on KAFKA-16160:
Hey [~phuctran] - I'm going to close this issue because I
[
https://issues.apache.org/jira/browse/KAFKA-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848703#comment-17848703
]
Philip Nee commented on KAFKA-15250:
After the inflight check fix. I think most request managers are
[
https://issues.apache.org/jira/browse/KAFKA-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-15250.
Resolution: Fixed
> ConsumerNetworkThread is running tight loop
>
Philip Nee created KAFKA-16819:
--
Summary: CoordinatorRequestManager seems to return 0ms during the
coordinator discovery
Key: KAFKA-16819
URL: https://issues.apache.org/jira/browse/KAFKA-16819
Project:
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848688#comment-17848688
]
Philip Nee commented on KAFKA-16687:
Hey [~fortherightous] - I was wondering if what I saw is in
[
https://issues.apache.org/jira/browse/KAFKA-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16001:
---
Description:
We should:
# Remove spy calls to the dependencies
# Remove ConsumerNetworkThreadTest
Philip Nee created KAFKA-16799:
--
Summary: NetworkClientDelegate is not backing off if the node is
not found
Key: KAFKA-16799
URL: https://issues.apache.org/jira/browse/KAFKA-16799
Project: Kafka
Philip Nee created KAFKA-16778:
--
Summary: AsyncKafkaConsumer fetcher might occasionally try to
fetch to a revoked partition
Key: KAFKA-16778
URL: https://issues.apache.org/jira/browse/KAFKA-16778
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846107#comment-17846107
]
Philip Nee commented on KAFKA-16687:
Also, by looking at the heap. It seems like we've been getting
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16687:
---
Attachment: diff
> Native memory leak by Unsafe_allocatememory in Kafka Clients 3.7.0
>
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846042#comment-17846042
]
Philip Nee edited comment on KAFKA-16687 at 5/13/24 6:51 PM:
-
Hey
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846042#comment-17846042
]
Philip Nee commented on KAFKA-16687:
Hey [~fortherightous] - I did a memory profile and found
[ https://issues.apache.org/jira/browse/KAFKA-16687 ]
Philip Nee deleted comment on KAFKA-16687:
was (Author: JIRAUSER283568):
[~fortherightous] - Not sure if this is what you are seeing:
{code:java}
Native Memory Tracking (reserved=3835KB
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845464#comment-17845464
]
Philip Nee commented on KAFKA-16687:
[~fortherightous] - Not sure if this is what you are seeing:
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845421#comment-17845421
]
Philip Nee commented on KAFKA-16687:
"Looks like it's caused by this" - mind elaborate?
> Native
[
https://issues.apache.org/jira/browse/KAFKA-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-7300:
-
Assignee: Philip Nee (was: Kevin Lu)
> Add KafkaConsumer fetch-error-rate and
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845045#comment-17845045
]
Philip Nee commented on KAFKA-16687:
Since you mentioned `disabled JMX reporter` would resolve the
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845042#comment-17845042
]
Philip Nee commented on KAFKA-16687:
Thank you.
> Native memory leak by Unsafe_allocatememory in
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844742#comment-17844742
]
Philip Nee commented on KAFKA-16687:
Hey @FTR - I wrote a simple consume-produce application and
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844400#comment-17844400
]
Philip Nee commented on KAFKA-16687:
thanks for the information this is massively helpful. how do
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844395#comment-17844395
]
Philip Nee commented on KAFKA-16687:
Your application uses KafkaConsumer only right?
> Native
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844387#comment-17844387
]
Philip Nee commented on KAFKA-16687:
But this is native memory leak so I suspect it's a different
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-16687:
--
Assignee: Philip Nee
> Native memory leak by Unsafe_allocatememory in Kafka Clients 3.7.0
[
https://issues.apache.org/jira/browse/KAFKA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844379#comment-17844379
]
Philip Nee commented on KAFKA-16687:
Hey [~fortherightous] - we also observed some (possible) memory
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16474.
Resolution: Fixed
Ran the test several times, the client log also looks fine.
>
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843326#comment-17843326
]
Philip Nee commented on KAFKA-16474:
Yeah I think we still need to figure why network thread isn't
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843320#comment-17843320
]
Philip Nee commented on KAFKA-16474:
Hey [~lianetm] - i'm planning to verify the fix and close out
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-16474:
--
Assignee: Philip Nee (was: Lianet Magrans)
> AsyncKafkaConsumer might send out heartbeat
[
https://issues.apache.org/jira/browse/KAFKA-16022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842730#comment-17842730
]
Philip Nee commented on KAFKA-16022:
hi [~phuctran] - I believe this came up during integration
[
https://issues.apache.org/jira/browse/KAFKA-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-13447:
--
Assignee: Philip Nee
> Consumer should not reuse committed offset after topic recreation
>
[
https://issues.apache.org/jira/browse/KAFKA-16110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16110:
---
Issue Type: Task (was: New Feature)
> Document and publicize performance test results for
[
https://issues.apache.org/jira/browse/KAFKA-16110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16110:
---
Summary: Document and publicize performance test results for
AsyncKafkaConsumer (was: Implement
[
https://issues.apache.org/jira/browse/KAFKA-16639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842187#comment-17842187
]
Philip Nee edited comment on KAFKA-16639 at 4/29/24 11:55 PM:
--
hey - sorry.
[
https://issues.apache.org/jira/browse/KAFKA-16639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842187#comment-17842187
]
Philip Nee commented on KAFKA-16639:
hey - sorry. I took this because I wasn't sure if you wanted
[
https://issues.apache.org/jira/browse/KAFKA-16639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-16639:
--
Assignee: Philip Nee (was: Chia-Ping Tsai)
> AsyncKafkaConsumer#close does not send
[
https://issues.apache.org/jira/browse/KAFKA-16639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841678#comment-17841678
]
Philip Nee commented on KAFKA-16639:
thanks for reporting. will do.
> AsyncKafkaConsumer#close does
[
https://issues.apache.org/jira/browse/KAFKA-16579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16579.
Resolution: Fixed
> Revert changes to consumer_rolling_upgrade_test.py for the new async Consumer
[
https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16389.
Resolution: Fixed
> consumer_test.py’s test_valid_assignment fails with new consumer
>
[
https://issues.apache.org/jira/browse/KAFKA-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837836#comment-17837836
]
Philip Nee commented on KAFKA-15250:
Added a testing branch under my fork:
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837342#comment-17837342
]
Philip Nee commented on KAFKA-16474:
The log was attached:
See line 7481 and 7492 in :
{code:java}
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16474:
---
Attachment: failing_results.zip
> AsyncKafkaConsumer might send out heartbeat request without
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16474:
---
Summary: AsyncKafkaConsumer might send out heartbeat request without
waiting for its response
[
https://issues.apache.org/jira/browse/KAFKA-16474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16474:
---
Summary: AsyncKafkaConsumer might rapidly send out successive heartbeat
without waiting for the
Philip Nee created KAFKA-16474:
--
Summary: AsyncKafkaConsumer might rapidly send out successive
heartbeat causing partitions getting revoked
Key: KAFKA-16474
URL: https://issues.apache.org/jira/browse/KAFKA-16474
[
https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833744#comment-17833744
]
Philip Nee commented on KAFKA-16389:
[^consumer.log]
It seems like the consumer receives empty
[
https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16389:
---
Attachment: consumer.log
> consumer_test.py’s test_valid_assignment fails with new consumer
>
[
https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833704#comment-17833704
]
Philip Nee commented on KAFKA-16389:
Hi [~kirktrue] Thanks for the initial investigation. I think
[
https://issues.apache.org/jira/browse/KAFKA-16433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16433:
---
Labels: consumer-threading-refactor (was: )
> beginningOffsets and offsetsForTimes don't behave
Philip Nee created KAFKA-16433:
--
Summary: beginningOffsets and offsetsForTimes don't behave
consistently when providing a zero timeout
Key: KAFKA-16433
URL: https://issues.apache.org/jira/browse/KAFKA-16433
[
https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831016#comment-17831016
]
Philip Nee edited comment on KAFKA-16389 at 3/26/24 5:27 PM:
-
Hey
[
https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831016#comment-17831016
]
Philip Nee commented on KAFKA-16389:
Hey [~chia7712] - We are currently setting up the system tests
[
https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-16389:
--
Assignee: Philip Nee
> consumer_test.py’s test_valid_assignment fails with new consumer
>
[
https://issues.apache.org/jira/browse/KAFKA-16405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee reassigned KAFKA-16405:
--
Assignee: Philip Nee
> Mismatch assignment error when running consumer rolling upgrade
Philip Nee created KAFKA-16405:
--
Summary: Mismatch assignment error when running consumer rolling
upgrade system tests
Key: KAFKA-16405
URL: https://issues.apache.org/jira/browse/KAFKA-16405
Project:
Philip Nee created KAFKA-16390:
--
Summary: consumer_bench_test.py failed using AsyncKafkaConsumer
Key: KAFKA-16390
URL: https://issues.apache.org/jira/browse/KAFKA-16390
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-16116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16116.
Resolution: Fixed
> AsyncKafkaConsumer: Add missing rebalance metrics
>
[
https://issues.apache.org/jira/browse/KAFKA-16156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816239#comment-17816239
]
Philip Nee commented on KAFKA-16156:
There seem to be a subtle difference in behavior between the
[
https://issues.apache.org/jira/browse/KAFKA-16156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815820#comment-17815820
]
Philip Nee commented on KAFKA-16156:
This issue seems easily reproducible by simply running
[
https://issues.apache.org/jira/browse/KAFKA-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16115.
Resolution: Fixed
> AsyncKafkaConsumer: Add missing heartbeat metrics
>
[
https://issues.apache.org/jira/browse/KAFKA-16178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808801#comment-17808801
]
Philip Nee commented on KAFKA-16178:
Seems to be an issue with the RequestState - I wonder if we've
[
https://issues.apache.org/jira/browse/KAFKA-16113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16113.
Resolution: Fixed
> AsyncKafkaConsumer: Add missing offset commit metrics
>
Philip Nee created KAFKA-16160:
--
Summary: AsyncKafkaConsumer is trying to connect to a disconnected
note in a tight loop
Key: KAFKA-16160
URL: https://issues.apache.org/jira/browse/KAFKA-16160
Project:
[
https://issues.apache.org/jira/browse/KAFKA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16160:
---
Description:
Observing some excessive logging running AsyncKafkaConsumer and observing
excessive
[
https://issues.apache.org/jira/browse/KAFKA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16160:
---
Labels: consumer-threading-refactor (was: )
> AsyncKafkaConsumer is trying to connect to a
[
https://issues.apache.org/jira/browse/KAFKA-16160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16160:
---
Parent: KAFKA-14246
Issue Type: Sub-task (was: Task)
> AsyncKafkaConsumer is trying to
[
https://issues.apache.org/jira/browse/KAFKA-16159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16159:
---
Description:
While running system tests locally, I've noticed excessive logging of the
Telemtry
[
https://issues.apache.org/jira/browse/KAFKA-16159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16159:
---
Fix Version/s: 3.8.0
> Prune excessive logging from Telemetry Reporter
>
[
https://issues.apache.org/jira/browse/KAFKA-16159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16159:
---
Labels: consumer logging (was: logging)
> Prune excessive logging from Telemetry Reporter
>
[
https://issues.apache.org/jira/browse/KAFKA-16159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16159:
---
Labels: logging (was: )
> Prune excessive logging from Telemetry Reporter
>
Philip Nee created KAFKA-16159:
--
Summary: Prune excessive logging from Telemetry Reporter
Key: KAFKA-16159
URL: https://issues.apache.org/jira/browse/KAFKA-16159
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-16112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-16112.
Resolution: Fixed
These are the results of this ticket
|KAFKA-16113|
|KAFKA-16116|
[
https://issues.apache.org/jira/browse/KAFKA-16116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16116:
---
Labels: consumer-threading-refactor (was: )
> AsyncKafkaConsumer: Add missing rebalance metrics
>
[
https://issues.apache.org/jira/browse/KAFKA-16116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16116:
---
Parent: KAFKA-14246
Issue Type: Sub-task (was: Improvement)
> AsyncKafkaConsumer: Add
[
https://issues.apache.org/jira/browse/KAFKA-16116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16116:
---
Component/s: consumer
metrics
> AsyncKafkaConsumer: Add missing rebalance metrics
Philip Nee created KAFKA-16116:
--
Summary: AsyncKafkaConsumer: Add missing rebalance metrics
Key: KAFKA-16116
URL: https://issues.apache.org/jira/browse/KAFKA-16116
Project: Kafka
Issue Type:
Philip Nee created KAFKA-16115:
--
Summary: AsyncKafkaConsumer: Add missing heartbeat metrics
Key: KAFKA-16115
URL: https://issues.apache.org/jira/browse/KAFKA-16115
Project: Kafka
Issue Type:
[
https://issues.apache.org/jira/browse/KAFKA-16115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16115:
---
Parent: KAFKA-14246
Issue Type: Sub-task (was: Improvement)
> AsyncKafkaConsumer: Add
[
https://issues.apache.org/jira/browse/KAFKA-16113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16113:
---
Parent: KAFKA-14246
Issue Type: Sub-task (was: Improvement)
> AsyncKafkaConsumer: Add
Philip Nee created KAFKA-16113:
--
Summary: AsyncKafkaConsumer: Add missing offset commit metrics
Key: KAFKA-16113
URL: https://issues.apache.org/jira/browse/KAFKA-16113
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-16110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805272#comment-17805272
]
Philip Nee commented on KAFKA-16110:
My proposal here is
- Let's run trogdor to see what can we get
[
https://issues.apache.org/jira/browse/KAFKA-16110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805271#comment-17805271
]
Philip Nee commented on KAFKA-16110:
Hi [~kirktrue] - Thanks for filing this JIRA. There are two
[
https://issues.apache.org/jira/browse/KAFKA-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-15250.
Fix Version/s: (was: 3.8.0)
Resolution: Fixed
> DefaultBackgroundThread is running
[
https://issues.apache.org/jira/browse/KAFKA-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804576#comment-17804576
]
Philip Nee commented on KAFKA-15250:
i believe this is resolved.
> DefaultBackgroundThread is
[
https://issues.apache.org/jira/browse/KAFKA-15872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804574#comment-17804574
]
Philip Nee commented on KAFKA-15872:
related https://issues.apache.org/jira/browse/KAFKA-15475
>
[ https://issues.apache.org/jira/browse/KAFKA-15872 ]
Philip Nee deleted comment on KAFKA-15872:
was (Author: JIRAUSER283568):
this can be closed as duplicate of KAFKA-15946
> Investigate autocommit retry logic
>
[
https://issues.apache.org/jira/browse/KAFKA-15872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804573#comment-17804573
]
Philip Nee commented on KAFKA-15872:
this can be closed as duplicate of KAFKA-15946
> Investigate
[
https://issues.apache.org/jira/browse/KAFKA-16034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801921#comment-17801921
]
Philip Nee commented on KAFKA-16034:
Hi [~phuctran] - I think the issue might already been fixed.
[
https://issues.apache.org/jira/browse/KAFKA-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee resolved KAFKA-15948.
Assignee: Philip Nee (was: Phuc Hong Tran)
Resolution: Fixed
> Refactor AsyncKafkaConsumer
[
https://issues.apache.org/jira/browse/KAFKA-15818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800506#comment-17800506
]
Philip Nee commented on KAFKA-15818:
thank u stan. it was merged.
> Implement max poll interval
>
[
https://issues.apache.org/jira/browse/KAFKA-15818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799043#comment-17799043
]
Philip Nee commented on KAFKA-15818:
hi stan -
Philip Nee created KAFKA-16034:
--
Summary: AsyncKafkaConsumer will get Invalid Request error when
trying to rejoin on fenced/unknown member Id
Key: KAFKA-16034
URL: https://issues.apache.org/jira/browse/KAFKA-16034
[
https://issues.apache.org/jira/browse/KAFKA-16034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Nee updated KAFKA-16034:
---
Parent: KAFKA-14246
Issue Type: Sub-task (was: Bug)
> AsyncKafkaConsumer will get Invalid
[
https://issues.apache.org/jira/browse/KAFKA-16026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798843#comment-17798843
]
Philip Nee commented on KAFKA-16026:
For the PR [15035|https://github.com/apache/kafka/pull/15035] -
[
https://issues.apache.org/jira/browse/KAFKA-16010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798772#comment-17798772
]
Philip Nee commented on KAFKA-16010:
I thought KAFKA-16026 (fixing the max poll) would fix this;
1 - 100 of 413 matches
Mail list logo
