I already have a jira account:
Username: dheerajsharma1990
Name: Dheeraj Sharma
But as mentioned in the http://kafka.apache.org/contributing.html page
"Please contact us to be added the contributor list.After that you can
assign yourself to the JIRA ticket you have started working on so others
Do we want to deprecate anything before 0.9.0 is released? Maybe the old
producer?
Ismael
On Thu, Sep 17, 2015 at 8:07 PM, Dong Lin wrote:
> Hey Jun,
>
> Should we also include https://issues.apache.org/jira/browse/KAFKA-2390 in
> 0.9.0? Becket told me that this is one of
GitHub user becketqin opened a pull request:
https://github.com/apache/kafka/pull/221
KAFKA-2555: Infinite recursive function call when call commitSync in â¦
@hachikuji @ewencp I found this problem when adding new consumer to mirror
maker which commits offset in the rebalance
[
https://issues.apache.org/jira/browse/KAFKA-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876044#comment-14876044
]
ASF GitHub Bot commented on KAFKA-2555:
---
GitHub user becketqin opened a pull request:
Jiangjie Qin created KAFKA-2557:
---
Summary: Separate RebalanceNeededException from
IllegalGenerationIdException
Key: KAFKA-2557
URL: https://issues.apache.org/jira/browse/KAFKA-2557
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-2557:
Description:
The ILLEGAL_GENERATION error is a bit confusing today. When a consumer receives
an
[
https://issues.apache.org/jira/browse/KAFKA-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-2557:
Summary: Separate RebalanceInProgress from IllegalGeneration Error Code
(was: Separate
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36858/
---
(Updated Sept. 19, 2015, 2:27 a.m.)
Review request for kafka.
Bugs:
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayuresh Gharat updated KAFKA-2120:
---
Status: Patch Available (was: Reopened)
> Add a request timeout to NetworkClient
>
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876838#comment-14876838
]
Mayuresh Gharat commented on KAFKA-2120:
Updated reviewboard
[
https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayuresh Gharat updated KAFKA-2120:
---
Attachment: KAFKA-2120_2015-09-18_19:27:48.patch
> Add a request timeout to NetworkClient
>
[
https://issues.apache.org/jira/browse/KAFKA-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876545#comment-14876545
]
Joel Koshy commented on KAFKA-2438:
---
FYI, I find that this patch appears to exacerbate timing-related
[
https://issues.apache.org/jira/browse/KAFKA-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876574#comment-14876574
]
Ismael Juma commented on KAFKA-2438:
Jenkins has indeed been less stable since this went in from what
Hey Bhavesh,
I think it is useful to notify the user about the partition change.
The problem of having a listener in producer is that it is hard to
guarantee the synchronization. For example, consider the following sequence:
1. producer sender thread refreshes the metadata with partition change.
GitHub user onurkaraman opened a pull request:
https://github.com/apache/kafka/pull/222
KAFKA-2557: separate REBALANCE_IN_PROGRESS and ILLEGAL_GENERATION error
codes
You can merge this pull request into a Git repository by running:
$ git pull
[
https://issues.apache.org/jira/browse/KAFKA-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1487#comment-1487
]
ASF GitHub Bot commented on KAFKA-2557:
---
GitHub user onurkaraman opened a pull request:
[
https://issues.apache.org/jira/browse/KAFKA-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876573#comment-14876573
]
Onur Karaman commented on KAFKA-2438:
-
I am running into transient failures for some
im using gradle version 2.7
i have two environment to build kafka, linux and mac;
find that on linux it goes well, but on mac I run into problem below:
To honour the JVM settings for this build a new JVM will be forked. Please
consider using the daemon:
Denis created KAFKA-2556:
Summary: Corrupted index on log.dir updates
Key: KAFKA-2556
URL: https://issues.apache.org/jira/browse/KAFKA-2556
Project: Kafka
Issue Type: Bug
Components: core
[
https://issues.apache.org/jira/browse/KAFKA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Stratiychuk updated KAFKA-2478:
--
Status: Patch Available (was: Open)
Here's a PR
Apologies in advance for continuously pestering about the releases. I
know there was a mail sent out for voting the 0.8.2.2 release a couple
of weeks back, but from what I see, the release is still pending. Any
idea if this will be released the coming week?
Overall, I'm wondering whether a
[
https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14875986#comment-14875986
]
Joel Koshy commented on KAFKA-2419:
---
However, we should think through the effect of doing this. i.e.,
Done.
Thanks,
Joel
On Fri, Sep 18, 2015 at 2:57 AM, Dheeraj Sharma
wrote:
> I already have a jira account:
>
> Username: dheerajsharma1990
> Name: Dheeraj Sharma
>
> But as mentioned in the http://kafka.apache.org/contributing.html page
> "Please contact us to be
23 matches
Mail list logo