Resending to include kafka-clients.
On Sat, Nov 11, 2017 at 12:37 AM, Rajini Sivaram
wrote:
> Hello Kafka users, developers and client-developers,
>
>
> This is the first candidate for release of Apache Kafka 0.11.0.2.
>
>
> This is a bug fix release and it includes fixes
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 0.11.0.2.
This is a bug fix release and it includes fixes and improvements from 16 JIRAs,
including a few critical bugs.
Release notes for the 0.11.0.2 release:
http://home.apache.org
.
- https://issues.apache.org/jira/browse/KAFKA-4827
- https://issues.apache.org/jira/browse/KAFKA-5936
The plan is to build the first RC later today. So please let me know if you
think there are any blockers.
Thank you!
Rajini
On Mon, Nov 6, 2017 at 9:47 PM, Rajini Sivaram
wrote:
> Th
[
https://issues.apache.org/jira/browse/KAFKA-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-6164.
---
Resolution: Fixed
Issue resolved by pull request 4199
[https://github.com/apache/kafka/pull
9:29 PM, Rajini Sivaram
wrote:
> Thanks, Guozhang. I will move KAFKA-1923 out of 0.11.0.2.
>
> On Mon, Nov 6, 2017 at 5:36 PM, Guozhang Wang wrote:
>
>> Thanks Rajini, +1 on releasing a 0.11.0.2.
>>
>> I made a pass over the outstanding issues, and added anoth
uggestion is to move that issue out of the scope while driving to finish
> others sooner.
>
> Guozhang
>
>
> On Mon, Nov 6, 2017 at 2:47 AM, Rajini Sivaram
> wrote:
>
> > Hi all,
> >
> >
> > Since we have fixed some critical issues since 0.11.0.1, it
Congratulations, Onur!
On Mon, Nov 6, 2017 at 8:10 PM, Dong Lin wrote:
> Congratulations Onur!
>
> On Mon, Nov 6, 2017 at 9:24 AM, Jun Rao wrote:
>
> > Hi, everyone,
> >
> > The PMC of Apache Kafka is pleased to announce a new Kafka committer Onur
> > Karaman.
> >
> > Onur's most significant wo
+1 (binding)
Thanks for the KIP, Jorge.
Regards,
Rajini
On Tue, Oct 31, 2017 at 9:58 AM, Damian Guy wrote:
> Thanks for the KIP - +1 (binding)
>
> On Mon, 23 Oct 2017 at 18:39 Guozhang Wang wrote:
>
> > Thanks Jorge for driving this KIP! +1 (binding).
> >
> >
> > Guozhang
> >
> > On Mon, Oct
[
https://issues.apache.org/jira/browse/KAFKA-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-6156.
---
Resolution: Fixed
Fix Version/s: 1.1.0
Issue resolved by pull request 4173
[https
does not have much impact compare with what we have now.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
>
>
> On Fri, Nov 3, 2017 at 3:09 PM, Rajini Sivaram
> wrote:
>
> > Hi Becket,
> >
> > Thank you for the KIP. A few comments:
> >
> > 1.KIP s
Hi all,
Since we have fixed some critical issues since 0.11.0.1, it must be time
for a 0.11.0.2 release.
Since the 0.11.0.1 release we've fixed 14 JIRAs that are targeted for
0.11.0.2:
https://issues.apache.org/jira/browse/KAFKA-6134?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Resolved%2C
Hi Becket,
Thank you for the KIP. A few comments:
1.KIP says: "*No public interface changes are needed. We only propose
behavior change on the broker side.*"
But from the proposed changes, it sounds like clients will be updated to
wait for throttle-time before sending next response, and also no
[
https://issues.apache.org/jira/browse/KAFKA-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-6060.
---
Resolution: Fixed
Fix Version/s: 1.1.0
Issue resolved by pull request 4073
https
kedIn, Netflix, Pinterest,
> Rabobank,
> > > Target, The New York Times, Uber, Yelp, and Zalando, among others.
> > >
> > >
> > > A big thank you for the following 108 contributors to this release!
> > >
> > > Abhishek Mendhekar, Xi H
Rajini Sivaram created KAFKA-6131:
-
Summary: Transaction markers are sometimes discarded if txns
complete concurrently
Key: KAFKA-6131
URL: https://issues.apache.org/jira/browse/KAFKA-6131
Project
Rajini Sivaram created KAFKA-6096:
-
Summary: Add concurrent tests to exercise all paths in
group/transaction managers
Key: KAFKA-6096
URL: https://issues.apache.org/jira/browse/KAFKA-6096
Project
[
https://issues.apache.org/jira/browse/KAFKA-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5970.
---
Resolution: Fixed
The new deadlock will be fixed under KAFKA-6042
> Deadlock due to lock
[
https://issues.apache.org/jira/browse/KAFKA-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram reopened KAFKA-5970:
---
[~corlettb] Thank you for reporting this. Looks like there is another potential
deadlock as well
Rajini Sivaram created KAFKA-6089:
-
Summary: Transient failure in
kafka.network.SocketServerTest.configureNewConnectionException
Key: KAFKA-6089
URL: https://issues.apache.org/jira/browse/KAFKA-6089
+1 (binding)
On Mon, Oct 9, 2017 at 5:32 PM, Manikumar wrote:
> I'm bumping this up to get some attention :)
>
> On Wed, Sep 27, 2017 at 8:46 PM, Tom Bentley
> wrote:
>
> > +1 (nonbinding)
> >
> > On 27 September 2017 at 16:10, Manikumar
> > wrote:
> >
> > > Hi All,
> > >
> > > I'd like to sta
[
https://issues.apache.org/jira/browse/KAFKA-6012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-6012.
---
Resolution: Fixed
Fix Version/s: 1.1.0
Issue resolved by pull request 4024
[https
[
https://issues.apache.org/jira/browse/KAFKA-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5978.
---
Resolution: Fixed
Assignee: Rajini Sivaram
This could be because the times are too
[
https://issues.apache.org/jira/browse/KAFKA-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-6010.
---
Resolution: Fixed
Fix Version/s: 1.0.0
Issue resolved by pull request 4018
[https
[
https://issues.apache.org/jira/browse/KAFKA-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-6004.
---
Resolution: Fixed
Issue resolved by pull request 4015
[https://github.com/apache/kafka/pull
Rajini Sivaram created KAFKA-6004:
-
Summary: Enable custom authentication plugins to return error
messages to clients
Key: KAFKA-6004
URL: https://issues.apache.org/jira/browse/KAFKA-6004
Project
Rajini Sivaram created KAFKA-5978:
-
Summary: Transient failure in
SslTransportLayerTest.testNetworkThreadTimeRecorded
Key: KAFKA-5978
URL: https://issues.apache.org/jira/browse/KAFKA-5978
Project
Rajini Sivaram created KAFKA-5970:
-
Summary: Deadlock due to locking of DelayedProduce and group
Key: KAFKA-5970
URL: https://issues.apache.org/jira/browse/KAFKA-5970
Project: Kafka
Issue
Rajini Sivaram created KAFKA-5968:
-
Summary: Remove all broker metrics during shutdown
Key: KAFKA-5968
URL: https://issues.apache.org/jira/browse/KAFKA-5968
Project: Kafka
Issue Type: Bug
Rajini Sivaram created KAFKA-5964:
-
Summary: Add more unit tests for SslTransportLayer
Key: KAFKA-5964
URL: https://issues.apache.org/jira/browse/KAFKA-5964
Project: Kafka
Issue Type: Test
Rajini Sivaram created KAFKA-5947:
-
Summary: Handle authentication failures from transactional
producer and KafkaAdminClient
Key: KAFKA-5947
URL: https://issues.apache.org/jira/browse/KAFKA-5947
Rajini Sivaram created KAFKA-5945:
-
Summary: Improve handling of authentication failures when
credentials are removed
Key: KAFKA-5945
URL: https://issues.apache.org/jira/browse/KAFKA-5945
Project
Rajini Sivaram created KAFKA-5944:
-
Summary: Add unit tests for handling of authentication failures in
clients
Key: KAFKA-5944
URL: https://issues.apache.org/jira/browse/KAFKA-5944
Project: Kafka
Rajini Sivaram created KAFKA-5942:
-
Summary: Handle authentication failures in streams
Key: KAFKA-5942
URL: https://issues.apache.org/jira/browse/KAFKA-5942
Project: Kafka
Issue Type
Rajini Sivaram created KAFKA-5941:
-
Summary: Handle authentication failures in connect
Key: KAFKA-5941
URL: https://issues.apache.org/jira/browse/KAFKA-5941
Project: Kafka
Issue Type
Rajini Sivaram created KAFKA-5920:
-
Summary: Handle SSL authentication failures as non-retriable
exceptions in clients
Key: KAFKA-5920
URL: https://issues.apache.org/jira/browse/KAFKA-5920
Project
d credentials.
> [kafka-producer-network-thread | producer-1] WARN
> org.apache.kafka.clients.NetworkClient
> - Connection to node -1 terminated during authentication. This may indicate
> that authentication failed due to invalid credentials.
>
>
>
>
>
> Any inputs will
+1 (binding)
Thank you for the KIP, Mickael.
On Thu, Sep 14, 2017 at 10:24 AM, Edoardo Comar wrote:
> +1 (non-binding)
> --
>
> Edoardo Comar
>
> IBM Message Hub
>
> IBM UK Ltd, Hursley Park, SO21 2JN
>
>
>
> From: Ismael Juma
> To: dev@kaf
[
https://issues.apache.org/jira/browse/KAFKA-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5872.
---
Resolution: Fixed
Issue resolved by pull request 3836
[https://github.com/apache/kafka/pull
Rajini Sivaram created KAFKA-5872:
-
Summary: Transient failure in SslSelectorTest.testMuteOnOOM
Key: KAFKA-5872
URL: https://issues.apache.org/jira/browse/KAFKA-5872
Project: Kafka
Issue
Hi Guozhang,
Can KIP-188 be added to the list, please? The vote has passed and PR should
be ready soon.
Thank you,
Rajini
On Thu, Sep 7, 2017 at 10:28 PM, Guozhang Wang wrote:
> Actually my bad, there is already a voting thread and you asked people to
> recast a vote on a small change.
>
> On
This vote has passed with 4 binding votes (Ismael, Jason, Jun, me) and 3
non-binding votes (Manikumar, Thomas Crayford, Mickael). Many thanks for
the votes and feedback.
I will update the KIP page.
Regards,
Rajini
On Fri, Sep 8, 2017 at 5:12 PM, Rajini Sivaram
wrote:
> Thank you, Jun.
>
Thank you, Jun.
If there are no other concerns by the end of the day, I will close the vote
tomorrow.
On Fri, Sep 8, 2017 at 5:09 PM, Jun Rao wrote:
> Hi, Raijini,
>
> Thanks for the explanation. We can leave those as they are then.
>
> Jun
>
> On Thu, Sep 7, 2017 at 3:
Rajini Sivaram created KAFKA-5854:
-
Summary: Handle SASL authentication failures as non-retriable
exceptions in clients
Key: KAFKA-5854
URL: https://issues.apache.org/jira/browse/KAFKA-5854
Project
[
https://issues.apache.org/jira/browse/KAFKA-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5777.
---
Resolution: Fixed
Fix Version/s: 1.0.0
Issue resolved by pull request 3726
[https
; c,topic=([-.\w]+)
>
>
> Also, for the ZK latency metric, Onur added a new ZookeeperClient wrapper
> and is in the middle of converting existing zkClient usage to the new
> wrapper. So, we probably want to add the latency metric in the new wrapper.
>
> Jun
>
> On Thu, Aug
2017 at 5:19 PM, Ismael Juma wrote:
>
> > I think I prefer the names with `Message` in them. For people less
> familiar
> > with Kafka, it makes it a bit clearer, I think.
> >
> > Ismael
> >
> > On Wed, Sep 6, 2017 at 12:39 AM, Rajini Sivaram
> the broker topic metrics:
> > > >
> > > > val totalProduceRequestRate =
> > > > newMeter(BrokerTopicStats.TotalProduceRequestsPerSec, "requests",
> > > > TimeUnit.SECONDS, tags)
> > > > val totalFetchRequestRate =
[
https://issues.apache.org/jira/browse/KAFKA-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5837.
---
Resolution: Fixed
Issue resolved by pull request 3792
[https://github.com/apache/kafka/pull
we maybe we can instead go for FetchMessageConversionsPerSecond and
> ProduceMessageConversionsPerSec.
>
> 2. Sounds good.
>
> Ismael
>
> On Tue, Sep 5, 2017 at 5:46 PM, Rajini Sivaram
> wrote:
>
> > Hi Ismael,
> >
> > 1. At the moment FetchDownConversionsPerSec is a topic
+1 (binding)
Thank you for the KIP, Jason.
On Thu, Aug 31, 2017 at 8:33 PM, Mickael Maison
wrote:
> +1 (non binding)
>
> Thanks for the KIP
>
> On Thu, Aug 31, 2017 at 10:10 AM, Jun Rao wrote:
> > That's also fine as long as it's documented in the interface somehow. The
> > only thing with jav
k about message conversions
> instead of down conversions only.
>
> 2. What will TemporaryMemorySize represent for requests other than
> `ProduceRequest`?
>
> Ismael
>
> On Mon, Sep 4, 2017 at 2:09 PM, Rajini Sivaram
> wrote:
>
> > All the suggestions on the dis
Rajini Sivaram created KAFKA-5837:
-
Summary: ReassignPartitionsCommand fails if default
throttle/timeout used
Key: KAFKA-5837
URL: https://issues.apache.org/jira/browse/KAFKA-5837
Project: Kafka
All the suggestions on the discuss thread have been incorporated into the
KIP. Please let me know if you have any more concerns or else can we
proceed with voting for this KIP?
Thank you,
Rajini
On Thu, Aug 24, 2017 at 6:50 PM, Rajini Sivaram
wrote:
> Hi all,
>
> I would like to
d only
> the produce and the fetch request may have such a component.
>
> Jun
>
> On Wed, Aug 30, 2017 at 1:37 PM, Rajini Sivaram
> wrote:
>
> > Jun,
> >
> > Thank you, your suggestions sound good. I have updated the KIP.
> >
> > Regards,
> &g
:
> Enthusiastic +1 from me :)
> It will be so helpful.
>
> On Wed, Aug 30, 2017 at 9:22 AM Roger Hoover
> wrote:
>
> > Great. Thank you, Rajini.
> >
> > On Wed, Aug 30, 2017 at 7:53 AM, Rajini Sivaram >
> > wrote:
> >
> > > Hi Roger,
>
il all clients support KIP
> 152.
>
> Just to be clear, the ones called `successful-authentication-rate` and
> `failed-authentication-rate` will also have failed-authentication-count
> and successful-authentication-count to match KIP 187?
>
> On Tue, Aug 29, 2017 at 7:26 AM, Ra
t metrics.
>
> Thanks
>
> On Thu, Aug 31, 2017 at 2:07 AM, Rajini Sivaram
> wrote:
>
> > Jun,
> >
> > Thank you, your suggestions sound good. I have updated the KIP.
> >
> > Regards,
> >
> > Rajini
> >
> > On Tue, Aug 29, 201
es
> > from any other error that can cause disconnect. This broker-side metric
> is
> > useful regardless but can help fill this gap until all clients support
> KIP
> > 152.
> >
> > Just to be clear, the ones called `successful-authentication-rate` and
> >
g)
> > > >>
> > > >> On Tue, Aug 29, 2017 at 11:09 AM, Ismael Juma
> > > wrote:
> > > >>
> > > >> > Thanks for the KIP, +1 (binding) from me.
> > > >> >
> > > >> > Ismael
> > > >>
Rajini Sivaram created KAFKA-5810:
-
Summary: Improve authentication logging on the broker-side
Key: KAFKA-5810
URL: https://issues.apache.org/jira/browse/KAFKA-5810
Project: Kafka
Issue Type
config for Kafka
> > separates authorization logs. It seems like a good idea to treat
> > authentication logs the same way whether or not we choose DEBUG or INFO.
> >
> > https://github.com/apache/kafka/blob/trunk/config/log4j.
> properties#L54-L58
> >
> > Che
0 AM, Ismael Juma wrote:
> >
> >> Thanks for the KIP, +1 (binding) from me.
> >>
> >> Ismael
> >>
> >> On Thu, Aug 24, 2017 at 6:29 PM, Rajini Sivaram <
> rajinisiva...@gmail.com>
> >> wrote:
> >>
> >> > Hi all,
rote:
>
> > Hi, Rajini,
> >
> > Yes, if those error metrics are registered dynamically, we could worry
> > about expiration later.
> >
> > Thanks,
> >
> > Jun
> >
> > On Fri, Aug 18, 2017 at 1:55 AM, Rajini Sivaram >
> > wrote
[
https://issues.apache.org/jira/browse/KAFKA-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5776.
---
Resolution: Fixed
Fix Version/s: 1.0.0
Issue resolved by pull request 3699
[https
Hi all,
I would like to start the vote on KIP-188 that adds additional metrics to
support health checks for Kafka Ops. Details are here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-188+-+Add+new+metrics+to+support+health+checks
Thank you,
Rajini
Hi all,
I would like to start the vote on KIP-187 that adds a cumulative count
metric associated with each Kafka rate metric to improve downstream
processing of rate metrics. Details are here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-187+-+Add+cumulative+count+metric+for+all+Kafka+ra
Hi all,
I would like to start vote on KIP-152 to improve diagnostics of
authentication failures and to update clients to treat authentication
failures as fatal exceptions rather than transient errors:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-152+-+Improve+diagnostics+for+SASL+authenti
Congratulations, Becket!
Regards,
Rajini
On Thu, Aug 24, 2017 at 10:02 AM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:
> Congrats Becket!
>
> --Vahid
>
>
>
> From: Abhishek Mendhekar
> To: dev@kafka.apache.org
> Date: 08/24/2017 09:53 AM
> Subject:Re: 答复: [ANNOUNCE] N
Hi all,
If there are no more comments, I will start vote on this KIP tomorrow.
Please let me know if there are any other concerns.
Thanks,
Rajini
On Fri, Aug 18, 2017 at 3:38 AM, Rajini Sivaram
wrote:
> Hi Jun,
>
> I have added constructors for all the variations. Haven't inclu
Hi all,
We can discuss the expiry implementation as part of the PR review. If there
are no further comments, I will start vote on this KIP tomorrow. Please let
me know if there are any other concerns.
On Fri, Aug 18, 2017 at 4:55 AM, Rajini Sivaram
wrote:
> Perhaps we could regis
Hi all,
If there are no more comments, I will start vote on this KIP tomorrow.
Please let me know if there are any concerns.
Thanks,
Rajini
On Mon, Aug 21, 2017 at 9:24 AM, Rajini Sivaram
wrote:
> Hi Jun,
>
> Thank you for the review.
>
> 1. Each token response will indicate
failures.
> There
> > are no log entries on the client-side to indicate that any of these
> > connection failures were due to authentication failure."
> >
> > 0.11.0.x logs a warning with a hint that the disconnect is likely related
> > to authentication.
&g
tion.
>
> Ismael
>
> On Tue, Aug 15, 2017 at 9:23 PM, Rajini Sivaram
> wrote:
>
> > I have updated the KIP based on the discussions so far. It will be good
> if
> > we can get some more feedback so that this can be implemented for 1.0.0.
> >
> &
are
> dynamically registered? Given that the maximum is bounded at development
> time, is it really worth all the extra code?
>
> Ismael
>
> On Fri, Aug 18, 2017 at 9:34 AM, Rajini Sivaram
> wrote:
>
> > Jun,
> >
> > It feels more consistent to add errors a
the gauges, I was thinking that the attribute would be the value
> > (i.e. commit id or version). I understand that Kafka Metrics doesn't
> > support this (unlike Yammer Metrics), but would it make sense to add?
> >
> > Ismael
> >
> > On Thu, Aug 17, 201
totalMetricName)
>
> Thanks,
>
> Jun
>
> On Thu, Aug 17, 2017 at 3:43 AM, Rajini Sivaram
> wrote:
>
> > Thank you, Roger.
> >
> > I have changed the naming of the internal classes slightly and updated
> the
> > example. The new CompoundStat is called
x27;s an argument
> for keeping it simple.
>
> 2. Would it make sense to use 2 gauges for the version and commit id? It
> seems more intuitive than having those values as tags.
>
> Ismael
>
> On Thu, Aug 17, 2017 at 10:19 AM, Rajini Sivaram
> wrote:
>
> > Hi Jun,
&g
> > Feedback and suggestions are appreciated.
> >
> > Thank you...
> >
> > Rajini
> >
> >
> > On Wed, Aug 16, 2017 at 1:34 PM, Rajini Sivaram >
> > wrote:
> >
> > > Hi all,
> > >
> > > I have posted a KIP to add a cumulative count attribute for all Kafka
> > rate
> > > metrics to make downstream processing simpler, more accurate and
> > flexible:
> > >
> > >
> >
>
at the the level of topic
> partition?
> > > For example, if a single ProduceRequest contains messages to append to
> 3
> > > partitions and say all 3 appends are successful, the counter
> > > for kafka.network:type=RequestMetrics,name=ErrorsPerSec,request=
&g
a single ProduceRequest contains messages to append to 3
> > partitions and say all 3 appends are successful, the counter
> > for kafka.network:type=RequestMetrics,name=ErrorsPerSec,request=
> ProduceRequest,error=0
> > will be incremented by 3?
> >
> > Thanks,
> &
Rajini Sivaram created KAFKA-5746:
-
Summary: Add new metrics to support health checks
Key: KAFKA-5746
URL: https://issues.apache.org/jira/browse/KAFKA-5746
Project: Kafka
Issue Type: New
I have created a KIP to add some additional metrics to support health
checks:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-188+-+Add+new+metrics+to+support+health+checks
Feedback and suggestions are welcome.
Regards,
Rajini
Sorry, pressed send by mistake.
The KIP is here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-187+-+Add+cumulative+count+metric+for+all+Kafka+rate+metrics
Feedback and suggestions are appreciated.
Thank you...
Rajini
On Wed, Aug 16, 2017 at 1:34 PM, Rajini Sivaram
wrote:
> Hi
Hi all,
I have posted a KIP to add a cumulative count attribute for all Kafka rate
metrics to make downstream processing simpler, more accurate and flexible:
Rajini Sivaram created KAFKA-5738:
-
Summary: Add cumulative count attribute for all Kafka rate metrics
Key: KAFKA-5738
URL: https://issues.apache.org/jira/browse/KAFKA-5738
Project: Kafka
could refresh the cached data for a user if authentication failed (a
> good implementation would be a bit more involved to avoid going to the
> underlying data source too often).
>
> Given that, not retrying sounds good to me.
>
> Ismael
>
> On Thu, May 4, 2017 at 4:04 PM, Raji
Rajini Sivaram created KAFKA-5735:
-
Summary: Client-ids are not handled consistently by clients and
broker
Key: KAFKA-5735
URL: https://issues.apache.org/jira/browse/KAFKA-5735
Project: Kafka
Thanks for the KIP.
+1 (binding)
On Tue, Jun 6, 2017 at 6:19 PM, BigData dev wrote:
> +1 (non-binding)
>
> Thanks,
> Bharat
>
> On Tue, Jun 6, 2017 at 9:21 AM, Ashwin Sinha
> wrote:
>
> > +1
> >
> > On Tue, Jun 6, 2017 at 11:20 PM, Mickael Maison <
> mickael.mai...@gmail.com>
> > wrote:
> >
>
Rajini Sivaram created KAFKA-5607:
-
Summary: Improve error handling in SocketServer to reduce illegal
states later
Key: KAFKA-5607
URL: https://issues.apache.org/jira/browse/KAFKA-5607
Project: Kafka
Congratulations, Jason!
On Wed, Jul 12, 2017 at 3:53 PM, Ismael Juma wrote:
> Congratulations Jason!
>
> Ismael
>
> On Tue, Jul 11, 2017 at 10:32 PM, Guozhang Wang
> wrote:
>
> > Hi Everyone,
> >
> > Jason Gustafson has been very active in contributing to the Kafka
> community
> > since he beca
Congratulations, Ismael!
On Wed, Jul 5, 2017 at 9:55 PM, Jun Rao wrote:
> Hi, Everyone,
>
> Ismael Juma has been active in the Kafka community since he became
> a Kafka committer about a year ago. I am glad to announce that Ismael is
> now a member of Kafka PMC.
>
> Congratulations, Ismael!
>
>
[
https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5402.
---
Resolution: Fixed
Fix Version/s: 0.11.1.0
Issue resolved by pull request 3303
[https
[
https://issues.apache.org/jira/browse/KAFKA-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5439.
---
Resolution: Fixed
Fix Version/s: 0.11.1.0
Issue resolved by pull request 3314
[https
Rajini Sivaram created KAFKA-5439:
-
Summary: Add checks in integration tests to verify that threads
have been shutdown
Key: KAFKA-5439
URL: https://issues.apache.org/jira/browse/KAFKA-5439
Project
[
https://issues.apache.org/jira/browse/KAFKA-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram resolved KAFKA-5433.
---
Resolution: Fixed
Fix Version/s: 0.11.1.0
0.11.0.0
Issue resolved
Rajini Sivaram created KAFKA-5433:
-
Summary: Transient test failure:
SaslPlainSslEndToEndAuthorizationTest.testNoProduceWithDescribeAcl
Key: KAFKA-5433
URL: https://issues.apache.org/jira/browse/KAFKA-5433
Congratulations, Damian!
On Sat, Jun 10, 2017 at 12:15 PM, Mickael Maison
wrote:
> Congrats Damian!
>
> On Sat, Jun 10, 2017 at 8:46 AM, Damian Guy wrote:
> > Thanks everyone. Looking forward to making many more contributions
> > On Sat, 10 Jun 2017 at 02:46, Joe Stein wrote:
> >
> >> Congrats
[
https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram reassigned KAFKA-5402:
-
Assignee: Rajini Sivaram
> JmxReporter Fetch metrics for kafka.server should not
[
https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044100#comment-16044100
]
Rajini Sivaram commented on KAFKA-5402:
---
[~junrao] Yes, agree that these met
[
https://issues.apache.org/jira/browse/KAFKA-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042627#comment-16042627
]
Rajini Sivaram commented on KAFKA-5401:
---
This is a duplicate of KAFKA-
801 - 900 of 1568 matches
Mail list logo
