[jira] [Commented] (KAFKA-4065) Property missing in ProcuderConfig.java - KafkaProducer API 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434215#comment-15434215 ] Manikumar Reddy commented on KAFKA-4065: "compression.type" config property is used in New

[jira] [Commented] (KAFKA-4071) Corruptted replication-offset-checkpoint leads to kafka server disfunctional

[ https://issues.apache.org/jira/browse/KAFKA-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434207#comment-15434207 ] Zane Zhang commented on KAFKA-4071: --- Sorry the original file is lost. > Corruptted

[jira] [Commented] (KAFKA-3754) Kafka default -Xloggc settings should include GC log rotation flags

[ https://issues.apache.org/jira/browse/KAFKA-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434194#comment-15434194 ] Jim Hoagland commented on KAFKA-3754: - I haven't tried it yet, but it looks like from the code that

[jira] [Commented] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434061#comment-15434061 ] ASF GitHub Bot commented on KAFKA-3940: --- Github user imandhan closed the pull request at:

[jira] [Commented] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434062#comment-15434062 ] ASF GitHub Bot commented on KAFKA-3940: --- GitHub user imandhan reopened a pull request:

[GitHub] kafka pull request #1748: KAFKA-3940 Log should check the return value of di...

GitHub user imandhan reopened a pull request: https://github.com/apache/kafka/pull/1748 KAFKA-3940 Log should check the return value of dir.mkdirs() This commit changes all the occurrences of dir.mkdirs() with Files.createDirectory(dir.toPath()) You can merge this pull request

[GitHub] kafka pull request #1748: KAFKA-3940 Log should check the return value of di...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/1748 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Build failed in Jenkins: kafka-trunk-jdk7 #1496

See Changes: [ismael] KAFKA-3937; Kafka Clients Leak Native Memory For Longer Than Needed With [ismael] KAFKA-4082; Upgrade to Gradle 3.0 -- [...truncated 13496 lines...]

Build failed in Jenkins: kafka-trunk-jdk8 #836

See Changes: [ismael] KAFKA-3937; Kafka Clients Leak Native Memory For Longer Than Needed With [ismael] KAFKA-4082; Upgrade to Gradle 3.0 -- Started by an SCM change [EnvInject] - Loading node

[jira] [Commented] (KAFKA-4082) Support Gradle 3.0

[ https://issues.apache.org/jira/browse/KAFKA-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433807#comment-15433807 ] ASF GitHub Bot commented on KAFKA-4082: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-4082) Support Gradle 3.0

[ https://issues.apache.org/jira/browse/KAFKA-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4082: --- Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was: Patch Available)

[GitHub] kafka pull request #1774: KAFKA-4082: Upgrade to Gradle 3.0

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1774 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3937: --- Assignee: William Yu > Kafka Clients Leak Native Memory For Longer Than Needed With Compressed >

[jira] [Resolved] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3937. Resolution: Fixed Reviewer: Ismael Juma Fix Version/s: 0.10.1.0 > Kafka Clients

[GitHub] kafka pull request #1760: KAFKA-3937: Kafka Clients Leak Native Memory For L...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1760 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433791#comment-15433791 ] ASF GitHub Bot commented on KAFKA-3937: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #1771: KAFKA-2894: WorkerSinkTask should rewind offsets o...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1771 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-2894) WorkerSinkTask doesn't handle rewinding offsets on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433790#comment-15433790 ] ASF GitHub Bot commented on KAFKA-2894: --- Github user asfgit closed the pull request at:

[jira] [Work started] (KAFKA-4001) Improve Kafka Streams Join Semantics (KIP-76)

[ https://issues.apache.org/jira/browse/KAFKA-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4001 started by Matthias J. Sax. -- > Improve Kafka Streams Join Semantics (KIP-76) >

[jira] [Commented] (KAFKA-4001) Improve Kafka Streams Join Semantics (KIP-76)

[ https://issues.apache.org/jira/browse/KAFKA-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433774#comment-15433774 ] ASF GitHub Bot commented on KAFKA-4001: --- GitHub user mjsax opened a pull request:

[GitHub] kafka pull request #1777: KAFKA-4001: Improve Kafka Streams Join Semantics (...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1777 KAFKA-4001: Improve Kafka Streams Join Semantics (KIP-76) [WiP] You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka kafka-4001-joins

[jira] [Commented] (KAFKA-3083) a soft failure in controller may leave a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433768#comment-15433768 ] Jun Rao commented on KAFKA-3083: Someone encountered another issue related to this. After a broker's ZK

Re: [VOTE] KIP-73 - Replication Quotas

For the record, there were 4 binding +1s. Ismael On Tue, Aug 23, 2016 at 11:16 PM, Ben Stopford wrote: > Thanks everyone. It looks like this KIP has now been accepted. > > There is a corresponding PR > for the implementation also.

Re: [VOTE] KIP-73 - Replication Quotas

Thanks everyone. It looks like this KIP has now been accepted. There is a corresponding PR for the implementation also. All the best B > On 23 Aug 2016, at 22:39, Joel Koshy wrote: > > +1 > (sent some very minor edits to you

[jira] [Commented] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433738#comment-15433738 ] Greg Fodor commented on KAFKA-3758: --- Excited to try this, as our state stores have grown, it's become

Re: [VOTE] KIP-73 - Replication Quotas

+1 (sent some very minor edits to you off-thread) On Fri, Aug 19, 2016 at 1:21 AM, Ben Stopford wrote: > I’d like to initiate the voting process for KIP-73: > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 73+Replication+Quotas

[GitHub] kafka pull request #1776: KIP-73 - Replication Quotas

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/1776 KIP-73 - Replication Quotas This applies to Replication Quotas based on KIP-73 [()](https://cwiki.apache.org/confluence/display/KAFKA/KIP-73+Replication+Quotas) originally motivated by

[jira] [Commented] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433652#comment-15433652 ] Guozhang Wang commented on KAFKA-3758: -- [~stliu] [~gfodor] With KAFKA-3888 merged into trunk this

[jira] [Commented] (KAFKA-3559) Task creation time taking too long in rebalance callback

[ https://issues.apache.org/jira/browse/KAFKA-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433648#comment-15433648 ] Guozhang Wang commented on KAFKA-3559: -- With KIP-62 (KAFKA-3888) merged into trunk, this issue should

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Ashish, Yes, I will send out a KIP invite for next week to discuss KIP-48 and other remaining KIPs. Thanks, Jun On Tue, Aug 23, 2016 at 1:22 PM, Ashish Singh wrote: > Thanks Harsha! > > Jun, can we add KIP-48 to next KIP hangout's agenda. Also, we did not > actually make

Re: Kafka KIP meeting Aug 23 at 11:00am PST

KIP-48 delegation token : Ashish will ping Harsh to see if this is still active. Harsha just replied and he will be willing to join in next KIP call to discuss more about KIP-48. On Tue, Aug 23, 2016 at 1:22 PM, Jun Rao wrote: The following are the notes from today's KIP

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Thanks Harsha! Jun, can we add KIP-48 to next KIP hangout's agenda. Also, we did not actually make a call on when we should have next KIP call. As there are a few outstanding KIPs that could not be discussed this week, can we have a KIP hangout call next week? On Tue, Aug 23, 2016 at 1:10 PM,

Re: Kafka KIP meeting Aug 23 at 11:00am PST

The following are the notes from today's KIP discussion. - time-based release: No one seems to have objections. Ismael will follow up with a release wiki. - KIP-4: We discussed having separate ACL requests of add and delete. No one seems to object to it. We discussed the admin

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Ashish, Yes we are working on it. Lets discuss in the next KIP meeting. I'll join. -Harsha On Tue, Aug 23, 2016 at 12:07 PM Ashish Singh wrote: > Hello Harsha, > > Are you still working on this? Wondering if we can discuss this in next KIP > meeting, if you can

[jira] [Updated] (KAFKA-1573) Transient test failures on LogTest.testCorruptLog

[ https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-1573: -- Assignee: Priyank Shah > Transient test failures on LogTest.testCorruptLog >

[jira] [Updated] (KAFKA-2081) testUncleanLeaderElectionEnabledByTopicOverride transient failure

[ https://issues.apache.org/jira/browse/KAFKA-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-2081: -- Assignee: Priyank Shah > testUncleanLeaderElectionEnabledByTopicOverride

[jira] [Updated] (KAFKA-3168) Failure in kafka.integration.PrimitiveApiTest.testPipelinedProduceRequests

[ https://issues.apache.org/jira/browse/KAFKA-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-3168: -- Assignee: Priyank Shah > Failure in

Build failed in Jenkins: kafka-trunk-jdk8 #835

See Changes: [me] KAFKA-2894: WorkerSinkTask should rewind offsets on rebalance -- [...truncated 12131 lines...] org.apache.kafka.streams.processor.internals.RecordQueueTest > testTimeTracking

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Hello Harsha, Are you still working on this? Wondering if we can discuss this in next KIP meeting, if you can join. On Mon, Jul 18, 2016 at 9:51 AM, Harsha Chintalapani wrote: > Hi Grant, > We are working on it. Will add the details to KIP about the > request

Build failed in Jenkins: kafka-trunk-jdk7 #1495

See Changes: [me] KAFKA-2894: WorkerSinkTask should rewind offsets on rebalance -- [...truncated 3385 lines...] kafka.coordinator.GroupMetadataManagerTest > testStoreNonEmptyGroup STARTED

[jira] [Comment Edited] (KAFKA-2014) Chaos Monkey / Failure Inducer for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433359#comment-15433359 ] Mayuresh Gharat edited comment on KAFKA-2014 at 8/23/16 6:37 PM: - This is

[jira] [Commented] (KAFKA-2014) Chaos Monkey / Failure Inducer for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433359#comment-15433359 ] Mayuresh Gharat commented on KAFKA-2014: https://github.com/linkedin/simoorg > Chaos Monkey /

[jira] [Resolved] (KAFKA-2014) Chaos Monkey / Failure Inducer for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat resolved KAFKA-2014. Resolution: Fixed > Chaos Monkey / Failure Inducer for Kafka >

[jira] [Resolved] (KAFKA-2976) Mirror maker dies if we delete a topic from destination cluster

[ https://issues.apache.org/jira/browse/KAFKA-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat resolved KAFKA-2976. Resolution: Won't Fix > Mirror maker dies if we delete a topic from destination cluster >

[jira] [Updated] (KAFKA-3722) PlaintextChannelBuilder should not use ChannelBuilders.createPrincipalBuilder(configs) for creating instance of PrincipalBuilder

[ https://issues.apache.org/jira/browse/KAFKA-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-3722: --- Status: Patch Available (was: In Progress) > PlaintextChannelBuilder should not use >

[jira] [Work started] (KAFKA-3722) PlaintextChannelBuilder should not use ChannelBuilders.createPrincipalBuilder(configs) for creating instance of PrincipalBuilder

[ https://issues.apache.org/jira/browse/KAFKA-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3722 started by Mayuresh Gharat. -- > PlaintextChannelBuilder should not use >

[jira] [Resolved] (KAFKA-2894) WorkerSinkTask doesn't handle rewinding offsets on rebalance

[ https://issues.apache.org/jira/browse/KAFKA-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-2894. -- Resolution: Fixed Issue resolved by pull request 1771

Re: [VOTE] KIP-73 - Replication Quotas

Thanks for the reviews guys. Jun, I’ll removed both LeaderOverThrottledRate as it’s not necessary. PartitionBytesInRate could be quite useful, if you want to work out what bandwidth a broker requires, based on some arbitrary set of replicas. I might keep that one in. Ismael - I’m happy with

[jira] [Updated] (KAFKA-4015) Change cleanup.policy config to accept a list of valid policies

[ https://issues.apache.org/jira/browse/KAFKA-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4015: -- Summary: Change cleanup.policy config to accept a list of valid policies (was: Add new cleanup.policy,

[GitHub] kafka pull request #1775: MINOR: Move a few methods from the `ZKUtils` class...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1775 MINOR: Move a few methods from the `ZKUtils` class to the companion object They don't require access to `ZkClient`. Also include a few obvious clean-ups in `ZKUtils`: * Remove redundant

Build failed in Jenkins: kafka-trunk-jdk7 #1494

See Changes: [ismael] KAFKA-3680; Enable Kafka clients to run in any classloader env -- [...truncated 12108 lines...] org.apache.kafka.streams.processor.internals.MinTimestampTrackerTest >

[jira] [Updated] (KAFKA-4082) Support Gradle 3.0

[ https://issues.apache.org/jira/browse/KAFKA-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4082: --- Status: Patch Available (was: Open) > Support Gradle 3.0 > -- > >

[GitHub] kafka pull request #1774: Upgrade to Gradle 3.0

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1774 Upgrade to Gradle 3.0 Also upgrade scoverage (required for compatibility) and remove usage of `useAnt` which doesn't exist in Gradle 3.0 It turns out that one cannot even run `gradle` to

[jira] [Created] (KAFKA-4082) Support Gradle 3.0

Ismael Juma created KAFKA-4082: -- Summary: Support Gradle 3.0 Key: KAFKA-4082 URL: https://issues.apache.org/jira/browse/KAFKA-4082 Project: Kafka Issue Type: Bug Reporter: Ismael

Re: [VOTE] KIP-73 - Replication Quotas

Thanks for the KIP, +1 (binding) with a couple of minor suggestions: //Sample configuration for throttled replicas { "version":1, "config": { "throttled-replicas":"0-0:0-1:0-2:1-0:1-1:1-2" } } I think it would be nicer if the "throttled-replicas" value was a JSON array instead of a String.

[jira] [Comment Edited] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432704#comment-15432704 ] Ismael Juma edited comment on KAFKA-2063 at 8/23/16 12:31 PM: -- Quick

[jira] [Commented] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432704#comment-15432704 ] Ismael Juma commented on KAFKA-2063: Quick implementation note: for the client to set the order, we'll

Build failed in Jenkins: kafka-trunk-jdk8 #834

See Changes: [ismael] KAFKA-3680; Enable Kafka clients to run in any classloader env -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1

[jira] [Updated] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3218: --- Fix Version/s: 0.10.1.0 > Kafka-0.9.0.0 does not work as OSGi module >

[jira] [Updated] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3218: -- Resolution: Fixed Status: Resolved (was: Patch Available) [~omkreddy] Yes, this has

[jira] [Commented] (KAFKA-3742) Can't run connect-distributed.sh with -daemon flag

[ https://issues.apache.org/jira/browse/KAFKA-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432679#comment-15432679 ] Hoon Park commented on KAFKA-3742: -- Hi. I'v created PR for this issue at

[jira] [Commented] (KAFKA-3218) Kafka-0.9.0.0 does not work as OSGi module

[ https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432667#comment-15432667 ] Manikumar Reddy commented on KAFKA-3218: [~ rajinisivaram]KAFKA-3680 fixes this issue right?

Re: [jira] [Created] (KAFKA-4078) VIP for Kafka doesn't work

If you change the url the broker is available on, you need to change the public advertised hostname in the configuration of the broker, this is not a bug, there is no way the broker could know how it can be reached from the outside, and when it changes. On Tue, Aug 23, 2016 at 10:33 AM chao

[jira] [Created] (KAFKA-4081) Consumer API consumer new interface commitSyn does not verify the validity of offset

lifeng created KAFKA-4081: - Summary: Consumer API consumer new interface commitSyn does not verify the validity of offset Key: KAFKA-4081 URL: https://issues.apache.org/jira/browse/KAFKA-4081 Project: Kafka

Re: Should we have a KIP call?

KIP call sounds good. Given that we only have an hour, it may make sense to prioritise the items that would benefit from KIP call discussion. I am leaving some comments below to hopefully help with prioritisation. >- KIP-33: Add a time based log index This has been merged. >- KIP-50:

[jira] [Commented] (KAFKA-3680) Make Java client classloading more flexible

[ https://issues.apache.org/jira/browse/KAFKA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432651#comment-15432651 ] ASF GitHub Bot commented on KAFKA-3680: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-3680) Make Java client classloading more flexible

[ https://issues.apache.org/jira/browse/KAFKA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3680: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request #1421: KAFKA-3680: Enable Kafka clients to run in any cla...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1421 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (KAFKA-4080) For the absence of topic, partitionsFor interface in the producer and consumer end performance is different

lifeng created KAFKA-4080: - Summary: For the absence of topic, partitionsFor interface in the producer and consumer end performance is different Key: KAFKA-4080 URL: https://issues.apache.org/jira/browse/KAFKA-4080

[jira] [Created] (KAFKA-4079) Document quota configuration changes from KIP-55

Rajini Sivaram created KAFKA-4079: - Summary: Document quota configuration changes from KIP-55 Key: KAFKA-4079 URL: https://issues.apache.org/jira/browse/KAFKA-4079 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-4057) Allow to specify the request version and replica ID in kafka.javaapi.FetchRequest

[ https://issues.apache.org/jira/browse/KAFKA-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-4057. --- Resolution: Won't Fix > Allow to specify the request version and replica ID in >

Re: [VOTE] KIP-74: Add FetchResponse size limit in bytes

Hi all! I declare the vote as passed. :) Thank you all for valuable input - really appreciate it. I’ll update KIP soon. I believe it should be ready early next week. Andrey. > On 23 Aug 2016, at 12:43, Ismael Juma wrote: > > Thanks Andrey. It has been 7 days since the vote

[GitHub] kafka pull request #1754: KAFKA-4057: Allow to specify the request version a...

Github user mimaison closed the pull request at: https://github.com/apache/kafka/pull/1754 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-4057) Allow to specify the request version and replica ID in kafka.javaapi.FetchRequest

[ https://issues.apache.org/jira/browse/KAFKA-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432522#comment-15432522 ] ASF GitHub Bot commented on KAFKA-4057: --- Github user mimaison closed the pull request at:

Re: [VOTE] KIP-74: Add FetchResponse size limit in bytes

Thanks Andrey. It has been 7 days since the vote started and there are 3 binding +1 votes (and 3 non-binding +1 votes), so you are free to declare the vote as passed whenever you're ready. :) Will you be able to update the PR to match the KIP soon? Thanks, Ismael On Mon, Aug 22, 2016 at 12:01

[jira] [Created] (KAFKA-4078) VIP for Kafka doesn't work

chao created KAFKA-4078: --- Summary: VIP for Kafka doesn't work Key: KAFKA-4078 URL: https://issues.apache.org/jira/browse/KAFKA-4078 Project: Kafka Issue Type: Bug Components: clients

[jira] [Created] (KAFKA-4077) Backdate validity of certificates in system tests to cope with clock skew

Rajini Sivaram created KAFKA-4077: - Summary: Backdate validity of certificates in system tests to cope with clock skew Key: KAFKA-4077 URL: https://issues.apache.org/jira/browse/KAFKA-4077 Project:

Build failed in Jenkins: kafka-0.10.0-jdk7 #194

See Changes: [junrao] KAFKA-4073; MirrorMaker should handle messages without timestamp -- [...truncated 5777 lines...] org.apache.kafka.streams.kstream.internals.KTableImplTest > testKTable

Build failed in Jenkins: kafka-trunk-jdk7 #1493

See Changes: [me] MINOR: Refactor TopologyBuilder with ApplicationID Prefix [junrao] KAFKA-4073; MirrorMaker should handle messages without timestamp -- [...truncated 12086 lines...]

Build failed in Jenkins: kafka-trunk-jdk8 #833

See Changes: [me] MINOR: Refactor TopologyBuilder with ApplicationID Prefix [junrao] KAFKA-4073; MirrorMaker should handle messages without timestamp -- [...truncated 7105 lines...]

[jira] [Commented] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432252#comment-15432252 ] Manikumar Reddy commented on KAFKA-4076: You are storing kafka data logs to /tmp folder. This is

[jira] [Commented] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432235#comment-15432235 ] Anyun commented on KAFKA-4076: --- kafka-server shuts down sometimes ,but only server.log display the error

[jira] [Created] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

Anyun created KAFKA-4076: - Summary: Kafka broker shuts down due to irrecoverable IO error Key: KAFKA-4076 URL: https://issues.apache.org/jira/browse/KAFKA-4076 Project: Kafka Issue Type: Bug

Build failed in Jenkins: kafka-trunk-jdk8 #832

See Changes: [ismael] KAFKA-3916; Check for disconnects properly before sending from the -- [...truncated 10986 lines...]