[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682981#comment-15682981
]
Ismael Juma commented on KAFKA-4425:
[~Fristi], which broker are you sending the metad
Rajini Sivaram created KAFKA-4426:
-
Summary: Add consumer.close(timeout, unit) for graceful close with
timeout
Key: KAFKA-4426
URL: https://issues.apache.org/jira/browse/KAFKA-4426
Project: Kafka
GitHub user enothereska opened a pull request:
https://github.com/apache/kafka/pull/2154
HOTFIX: Increased wait time
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/enothereska/kafka hotfix_streams
Alternatively you can review a
[
https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683056#comment-15683056
]
Michal Borowiecki commented on KAFKA-3514:
--
IMO, 2) *is* a severe problem. Punctu
[
https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eno Thereska updated KAFKA-3038:
Assignee: (was: Eno Thereska)
> Speeding up partition reassignment after broker failure
> --
Eno Thereska created KAFKA-4427:
---
Summary: Skip topicGroups with no tasks
Key: KAFKA-4427
URL: https://issues.apache.org/jira/browse/KAFKA-4427
Project: Kafka
Issue Type: Bug
Componen
[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683086#comment-15683086
]
Mark de Jong commented on KAFKA-4425:
-
I had the same idea about sending a metadata re
[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683132#comment-15683132
]
Mark de Jong commented on KAFKA-4425:
-
It seems I've solved the issue. My codec for bo
[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683132#comment-15683132
]
Mark de Jong edited comment on KAFKA-4425 at 11/21/16 10:29 AM:
[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683238#comment-15683238
]
Mark de Jong commented on KAFKA-4425:
-
Interesting, with metadata v2 request no topics
[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683245#comment-15683245
]
Ismael Juma commented on KAFKA-4425:
You have to pass `null` to get all topics. An emp
[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683246#comment-15683246
]
Ismael Juma commented on KAFKA-4425:
You have to pass `null` to get all topics. An emp
[
https://issues.apache.org/jira/browse/KAFKA-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683522#comment-15683522
]
Mark de Jong commented on KAFKA-4425:
-
Great, that works! Just added a test for deleti
[
https://issues.apache.org/jira/browse/KAFKA-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitch Seymour updated KAFKA-3701:
-
Assignee: (was: Mitch Seymour)
> Expose KafkaStreams metrics in public API
> -
Zeynep Arikoglu created KAFKA-4428:
--
Summary: Kafka does not exit when it receives "Address already in
use" error during startup
Key: KAFKA-4428
URL: https://issues.apache.org/jira/browse/KAFKA-4428
[
https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zeynep Arikoglu updated KAFKA-4428:
---
Description:
[2016-11-21 14:58:04,136] FATAL [Kafka Server 0], Fatal error during
KafkaServer
[
https://issues.apache.org/jira/browse/KAFKA-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683783#comment-15683783
]
Balint Molnar commented on KAFKA-4307:
--
Hi, [~manasvigupta] can I take this?
> Incon
[
https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15684271#comment-15684271
]
mjuarez commented on KAFKA-3994:
I've been running the ConsumerBounceTest, both with and w
Hi Michael,
I have updated the migration section of the KIP. Can you please take a look?
Thanks,
Mayuresh
On Fri, Nov 18, 2016 at 9:07 AM, Mayuresh Gharat wrote:
> Hi Michael,
>
> That whilst sending tombstone and non null value, the consumer can expect
> only to receive the non-null message
[
https://issues.apache.org/jira/browse/KAFKA-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15684468#comment-15684468
]
Vahid Hashemian commented on KAFKA-4271:
[~huxi] Thanks for responding. I checked
[
https://issues.apache.org/jira/browse/KAFKA-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15684523#comment-15684523
]
Damian Guy commented on KAFKA-4270:
---
Hi,
I still don't really follow what the issue is.
Hi folks,
We're seeing an issue where an exception inside the main processing loop of
a consumer doesn't cause the JVM to exit, as expected (and, in our case,
desired). From the thread dump, it appears that what's blocking exit is the
"kafka-coordinator-heartbeat-thread". From what I understand of
Dong Lin created KAFKA-4429:
---
Summary: records-lag should be zero if FetchResponse is empty
Key: KAFKA-4429
URL: https://issues.apache.org/jira/browse/KAFKA-4429
Project: Kafka
Issue Type: Improvem
GitHub user lindong28 opened a pull request:
https://github.com/apache/kafka/pull/2155
KAFKA-4429; records-lag should be zero if FetchResponse is empty
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lindong28/kafka KAFKA-4429
A
[
https://issues.apache.org/jira/browse/KAFKA-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685240#comment-15685240
]
ASF GitHub Bot commented on KAFKA-4429:
---
GitHub user lindong28 opened a pull request
[
https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huxi reassigned KAFKA-4428:
---
Assignee: huxi
> Kafka does not exit when it receives "Address already in use" error during
> startup
>
Srinivas Dhruvakumar created KAFKA-4430:
---
Summary: Broker logging Topic and partition to exceptions:
[topic,6] -> kafka.common.MessageSizeTooLargeException
Key: KAFKA-4430
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Summary: Broker logging "Topic and partition to exceptions: [topic,6] ->
kafka.commo
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
[
https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685562#comment-15685562
]
huxi commented on KAFKA-4428:
-
During Acceptor initialization, if "Address already in use" err
[
https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685562#comment-15685562
]
huxi edited comment on KAFKA-4428 at 11/22/16 3:32 AM:
---
During Accep
[
https://issues.apache.org/jira/browse/KAFKA-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685562#comment-15685562
]
huxi edited comment on KAFKA-4428 at 11/22/16 3:39 AM:
---
During Accep
GitHub user amethystic opened a pull request:
https://github.com/apache/kafka/pull/2156
kafka-4428: Kafka does not exit when it receives "Address already in use"
error during startup
kafka-4428: Kafka does not exit when it receives "Address already in use"
error during startup
Hi, all. I use the kafka which the version is 0.8.2.1. When partiton
transferring， KafkaProducer needs about 5mins to recovery, so do you know how
to fix it.
Thanks!!!
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Priority: Major (was: Minor)
> Broker logging "Topic and partition to exceptions: [
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivas Dhruvakumar updated KAFKA-4430:
Description:
I have a setup as below
DC Kafka
Mirrormaker
Aggregate Kafka
Here is
Hey David,
It probably should be a daemon thread. Perhaps open a JIRA?
Thanks,
Jason
On Mon, Nov 21, 2016 at 2:03 PM, David Judd
wrote:
> Hi folks,
>
> We're seeing an issue where an exception inside the main processing loop of
> a consumer doesn't cause the JVM to exit, as expected (and, in o
David Judd created KAFKA-4431:
-
Summary: HeartbeatThread should be a daemon thread
Key: KAFKA-4431
URL: https://issues.apache.org/jira/browse/KAFKA-4431
Project: Kafka
Issue Type: Bug
C
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685848#comment-15685848
]
huxi commented on KAFKA-4430:
-
Check broker config 'message.max.bytes' for Aggregate Kafka clu
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685885#comment-15685885
]
Srinivas Dhruvakumar commented on KAFKA-4430:
-
Sorry I forgot to mention. I ha
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685911#comment-15685911
]
huxi commented on KAFKA-4430:
-
Maybe you could confirm this: complete serialized size of the
[
https://issues.apache.org/jira/browse/KAFKA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685998#comment-15685998
]
Srinivas Dhruvakumar commented on KAFKA-4430:
-
I am still a noob . How do I co
48 matches
Mail list logo
