[jira] [Comment Edited] (KAFKA-5406) NoNodeException result in rebalance failed

[ https://issues.apache.org/jira/browse/KAFKA-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042157#comment-16042157 ] xiaoguy edited comment on KAFKA-5406 at 6/8/17 5:23 AM: [~huxi_2b] thanks for your

[jira] [Commented] (KAFKA-5314) Improve exception handling for state stores

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

[jira] [Resolved] (KAFKA-5314) Improve exception handling for state stores

[ https://issues.apache.org/jira/browse/KAFKA-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5314. -- Resolution: Fixed Issue resolved by pull request 3135

[GitHub] kafka pull request #3135: KAFKA-5314: exception handling and cleanup for sta...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3135 --- 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

Re: KIP-160 - Augment KStream.print() to allow users pass in extra parameters in the printed string

Folks, Since KIP-159 is still under discussion while KIP-160 already have a PR ready for review, I'd suggest we do not block James for too long but vote on the current proposal while we can further expand the APIs piggy-backed with KIP-159. Thoughts? Guozhang On Wed, Jun 7, 2017 at 6:54 PM,

[GitHub] kafka pull request #3264: MINOR: improve JavaDocs for TimestampExtractor int...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3264 --- 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

[GitHub] kafka pull request #3262: MINOR: Cache metrics were missing

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3262 --- 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-5406) NoNodeException result in rebalance failed

[ https://issues.apache.org/jira/browse/KAFKA-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042157#comment-16042157 ] xiaoguy commented on KAFKA-5406: [~huxi_2b] thanks for your replay ,this is the code of props ,

[jira] [Updated] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

[ https://issues.apache.org/jira/browse/KAFKA-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5403: Status: Patch Available (was: Open) > Transactions system test should dedup consumed messages by

[GitHub] kafka pull request #3266: KAFKA-5403: Transaction system test consumer shoul...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3266 KAFKA-5403: Transaction system test consumer should dedup messages by offset Since the consumer can consume duplicate offsets due to rebalances, we should dedup consumed messages by offset in order

[jira] [Commented] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

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

[jira] [Updated] (KAFKA-4768) Single-request latency for streams can be very high

[ https://issues.apache.org/jira/browse/KAFKA-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4768: --- Fix Version/s: (was: 0.11.0.0) > Single-request latency for streams can be very high >

[jira] [Updated] (KAFKA-4838) Export buffer cache metrics in JMX

[ https://issues.apache.org/jira/browse/KAFKA-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4838: --- Fix Version/s: (was: 0.11.0.0) > Export buffer cache metrics in JMX >

[jira] [Updated] (KAFKA-4770) KStreamAggregationDedupIntegrationTest fails occasionally

[ https://issues.apache.org/jira/browse/KAFKA-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4770: --- Fix Version/s: (was: 0.11.0.0) > KStreamAggregationDedupIntegrationTest fails occasionally >

[jira] [Updated] (KAFKA-4842) Streams integration tests occasionally fail with connection error

[ https://issues.apache.org/jira/browse/KAFKA-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4842: --- Fix Version/s: (was: 0.11.0.0) > Streams integration tests occasionally fail with connection

[jira] [Updated] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3455: --- Fix Version/s: (was: 0.11.0.0) > Connect custom processors with the streams DSL >

[jira] [Updated] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3543: --- Fix Version/s: (was: 0.11.0.0) > Allow a variant of transform() which can emit multiple values >

[jira] [Resolved] (KAFKA-5312) Improve exception handling for StreamsKafkaClient

[ https://issues.apache.org/jira/browse/KAFKA-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5312. Resolution: Duplicate > Improve exception handling for StreamsKafkaClient >

[jira] [Updated] (KAFKA-4956) Add system tests for request quotas

[ https://issues.apache.org/jira/browse/KAFKA-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4956: --- Fix Version/s: (was: 0.11.0.0) > Add system tests for request quotas >

[jira] [Updated] (KAFKA-5312) Improve exception handling for StreamsKafkaClient

[ https://issues.apache.org/jira/browse/KAFKA-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5312: --- Fix Version/s: (was: 0.11.0.0) > Improve exception handling for StreamsKafkaClient >

[jira] [Updated] (KAFKA-5024) Old clients don't support message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5024: --- Fix Version/s: (was: 0.11.0.0) > Old clients don't support message format V2 >

[jira] [Resolved] (KAFKA-5392) AdminClient leaking resources

[ https://issues.apache.org/jira/browse/KAFKA-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5392. Resolution: Duplicate Duplicate of KAFKA-5394. > AdminClient leaking resources >

[jira] [Updated] (KAFKA-5271) Producer only needs to send AddOffsetsToTxn one time for each group

[ https://issues.apache.org/jira/browse/KAFKA-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5271: --- Fix Version/s: (was: 0.11.0.0) > Producer only needs to send AddOffsetsToTxn one time for each

[jira] [Reopened] (KAFKA-5312) Improve exception handling for StreamsKafkaClient

[ https://issues.apache.org/jira/browse/KAFKA-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-5312: > Improve exception handling for StreamsKafkaClient > -

Jenkins build is back to normal : kafka-trunk-jdk8 #1674

See

[jira] [Updated] (KAFKA-5396) Transactions System Test: Consumer reading uninterrupted from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5396: --- Fix Version/s: (was: 0.11.0.0) > Transactions System Test: Consumer reading uninterrupted from

[jira] [Commented] (KAFKA-3532) add principal.builder.class that can extract user from a field

[ https://issues.apache.org/jira/browse/KAFKA-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042102#comment-16042102 ] Kaufman Ng commented on KAFKA-3532: --- @Sriharsha Chintalapani are you still working on this? Wondering if

[jira] [Updated] (KAFKA-5329) Replica list in the metadata cache on the broker may have different order from zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5329: --- Resolution: Fixed Fix Version/s: (was: 0.11.0.1) 0.11.0.0

[GitHub] kafka pull request #3257: KAFKA-5329: Fix order of replica list in metadata ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3257 --- 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-5329) Replica list in the metadata cache on the broker may have different order from zookeeper

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

Jenkins build is back to normal : kafka-trunk-jdk7 #2365

See

[jira] [Commented] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042086#comment-16042086 ] Ismael Juma commented on KAFKA-4815: I moved this JIRA to 0.11.1.0 as it includes a number of subtasks

[jira] [Updated] (KAFKA-4815) Idempotent/transactional Producer Checklist (KIP-98)

[ https://issues.apache.org/jira/browse/KAFKA-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4815: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Idempotent/transactional Producer

[jira] [Commented] (KAFKA-5342) Distinguish abortable failures in transactional producer

[ https://issues.apache.org/jira/browse/KAFKA-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042080#comment-16042080 ] Ismael Juma commented on KAFKA-5342: Are we still planning to include this in 0.11.0.0? > Distinguish

[jira] [Commented] (KAFKA-5286) Producer should await transaction completion in close

[ https://issues.apache.org/jira/browse/KAFKA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042081#comment-16042081 ] Ismael Juma commented on KAFKA-5286: Are we still planning to include this in 0.11.0.0? > Producer

[jira] [Work started] (KAFKA-5276) Support derived and prefixed configs in DescribeConfigs (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5276 started by Ismael Juma. -- > Support derived and prefixed configs in DescribeConfigs (KIP-133) >

[jira] [Commented] (KAFKA-5406) NoNodeException result in rebalance failed

[ https://issues.apache.org/jira/browse/KAFKA-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042077#comment-16042077 ] huxihx commented on KAFKA-5406: --- Maybe could estimate the total time period for the network recovery and

[jira] [Updated] (KAFKA-5292) Fix authorization checks in AdminClient

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

[jira] [Commented] (KAFKA-5402) JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled

[ https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042069#comment-16042069 ] huxihx commented on KAFKA-5402: --- Is it a duplicate of

Re: KIP-160 - Augment KStream.print() to allow users pass in extra parameters in the printed string

I agree with Matthias's comment. I check everyone's comment which all agree about this(Matthias's comment) :D James Chien

[jira] [Updated] (KAFKA-5406) NoNodeException result in rebalance failed

[ https://issues.apache.org/jira/browse/KAFKA-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaoguy updated KAFKA-5406: --- Description: hey guys , I got this problem this days, because of the network is unstable， consumer rebalance

[jira] [Assigned] (KAFKA-5405) Request log should log throttle time

[ https://issues.apache.org/jira/browse/KAFKA-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx reassigned KAFKA-5405: - Assignee: huxihx > Request log should log throttle time > > >

[jira] [Updated] (KAFKA-5406) NoNodeException result in rebalance failed

[ https://issues.apache.org/jira/browse/KAFKA-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaoguy updated KAFKA-5406: --- Attachment: log.log Description: hey guys , I got this problem this days, because of the network is

[jira] [Commented] (KAFKA-5405) Request log should log throttle time

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

[GitHub] kafka pull request #3265: KAFKA-5405: Request log should log throttle time

GitHub user huxihx opened a pull request: https://github.com/apache/kafka/pull/3265 KAFKA-5405: Request log should log throttle time Record `apiThrottleTime` in RequestChannel. @junrao A trivial change. Please review. Thanks. You can merge this pull request into a Git

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

Just bringing people's attention to the vote thread for my KIP. I started it before another round of discussion happened. Not sure the protocol so someone let me know if I am supposed to restart the vote. Thanks, Kyle On May 24, 2017 8:49 AM, "Bill Bejeck" wrote: > +1 for

[jira] [Commented] (KAFKA-5292) Fix authorization checks in AdminClient

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

[GitHub] kafka pull request #3240: KAFKA-5292. Fix authorization checks in AdminClien...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3240 --- 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-1561) Data Loss for Incremented Replica Factor and Leader Election

[ https://issues.apache.org/jira/browse/KAFKA-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042014#comment-16042014 ] Jun Rao commented on KAFKA-1561: [~vinayak10], did you set acks=all in the producer? > Data Loss for

[jira] [Updated] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

[ https://issues.apache.org/jira/browse/KAFKA-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4830: --- Labels: kip newbie (was: kip needs-kip newbie) > Augment KStream.print() to allow users pass

Re: [DISCUSS] KIP-132: Augment KStream.print to allow extra parameters in the printed string

Hi, as it turns out, we got two KIPs for the same Jira. KIP-160 duplicates KIP-132. @Marc: as you did start the first KIP-132 but did not carry it on from some point on, I am wondering if you are still interested to work on it? Sorry for this mix up. Hope we can resolve this properly...

[jira] [Updated] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

[ https://issues.apache.org/jira/browse/KAFKA-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4830: --- Description: Today {{KStream.print}} use the hard-coded result string as: {code} "[" +

[jira] [Updated] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

[ https://issues.apache.org/jira/browse/KAFKA-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4830: --- Labels: kip needs-kip newbie (was: needs-kip newbie) > Augment KStream.print() to allow

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

See Changes: [jason] KAFKA-5385; ProducerBatch expiry should go through Sender.failBatch -- [...truncated 4.53 MB...]

[GitHub] kafka pull request #3264: MINOR: improve JavaDocs for TimestampExtractor int...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3264 MINOR: improve JavaDocs for TimestampExtractor interface You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

[jira] [Comment Edited] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041869#comment-16041869 ] Dmitry Minkovsky edited comment on KAFKA-4628 at 6/7/17 11:15 PM: -- on

[jira] [Comment Edited] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041869#comment-16041869 ] Dmitry Minkovsky edited comment on KAFKA-4628 at 6/7/17 11:13 PM: -- on

[jira] [Comment Edited] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041869#comment-16041869 ] Dmitry Minkovsky edited comment on KAFKA-4628 at 6/7/17 11:14 PM: -- on

[jira] [Commented] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041869#comment-16041869 ] Dmitry Minkovsky commented on KAFKA-4628: - on KAFKA-4880 (a dupe of this ticket), Michale Noll

[jira] [Updated] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Vega updated KAFKA-5407: - Environment: Operating system CentOS 6.8 HW Board Mfg : HP Board Product :

[jira] [Updated] (KAFKA-5407) Mirrormaker dont start after upgrade

[ https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Vega updated KAFKA-5407: - Description: Currently Im upgrading the cluster from 0.8.2-beta to 0.10.2.1 So I followed the

[jira] [Created] (KAFKA-5407) Mirrormaker dont start after upgrade

Fernando Vega created KAFKA-5407: Summary: Mirrormaker dont start after upgrade Key: KAFKA-5407 URL: https://issues.apache.org/jira/browse/KAFKA-5407 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-5406) NoNodeException result in rebalance failed

xiaoguy created KAFKA-5406: -- Summary: NoNodeException result in rebalance failed Key: KAFKA-5406 URL: https://issues.apache.org/jira/browse/KAFKA-5406 Project: Kafka Issue Type: Bug

Jenkins build is back to normal : kafka-0.11.0-jdk7 #117

See

[jira] [Created] (KAFKA-5405) Request log should log throttle time

Jun Rao created KAFKA-5405: -- Summary: Request log should log throttle time Key: KAFKA-5405 URL: https://issues.apache.org/jira/browse/KAFKA-5405 Project: Kafka Issue Type: Improvement Affects

[jira] [Commented] (KAFKA-4633) Always use regex pattern subscription to avoid auto create topics

[ https://issues.apache.org/jira/browse/KAFKA-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041772#comment-16041772 ] Matthias J. Sax commented on KAFKA-4633: [~agomez] It's by desing. All topic specified by

[jira] [Commented] (KAFKA-5404) Add more AdminClient checks to ClientCompatibilityTest

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

[GitHub] kafka pull request #3263: KAFKA-5404: Add more AdminClient checks to ClientC...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3263 KAFKA-5404: Add more AdminClient checks to ClientCompatibilityTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-5404

Re: Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

Yeah I have thought about that but that would involve Apache Infra. The current proposal is based on the assumption that removing the notification can be done by ourselves. Guozhang On Wed, Jun 7, 2017 at 1:24 PM, Matthias J. Sax wrote: > Have you considered starting a

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Sriram, I think there is one way to explain why the ability to move replica between disks can save space. Let's say the load is distributed to disks independent of the broker. Sooner or later, the load imbalance will exceed a threshold and we will need to rebalance load across disks. Now our

Build failed in Jenkins: kafka-0.11.0-jdk7 #116

See -- Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H17 (ubuntu xenial) in workspace

[jira] [Created] (KAFKA-5404) Add more AdminClient checks to ClientCompatibilityTest

Colin P. McCabe created KAFKA-5404: -- Summary: Add more AdminClient checks to ClientCompatibilityTest Key: KAFKA-5404 URL: https://issues.apache.org/jira/browse/KAFKA-5404 Project: Kafka

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Hi Eno, On 07.06.2017 22:49, Eno Thereska wrote: Comments inline: On 5 Jun 2017, at 18:19, Jan Filipiak wrote: Hi just my few thoughts On 05.06.2017 11:44, Eno Thereska wrote: Hi there, Sorry for the late reply, I was out this past week. Looks like good

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Sriram, Thanks for raising these concerns. Let me answer these questions below: - The benefit of those additional complexity to move the data stored on a disk within the broker is to avoid network bandwidth usage. Creating replica on another broker is less efficient than creating replica on

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

See Changes: [jason] KAFKA-5385; ProducerBatch expiry should go through Sender.failBatch -- [...truncated 5.99 MB...] at

[jira] [Updated] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

[ https://issues.apache.org/jira/browse/KAFKA-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5403: Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Transactions system test should

[jira] [Updated] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

[ https://issues.apache.org/jira/browse/KAFKA-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5403: Affects Version/s: 0.11.0.0 > Transactions system test should dedup consumed messages by offset >

[jira] [Created] (KAFKA-5403) Transactions system test should dedup consumed messages by offset

Apurva Mehta created KAFKA-5403: --- Summary: Transactions system test should dedup consumed messages by offset Key: KAFKA-5403 URL: https://issues.apache.org/jira/browse/KAFKA-5403 Project: Kafka

[jira] [Created] (KAFKA-5402) JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled

Koelli Mungee created KAFKA-5402: Summary: JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled Key: KAFKA-5402 URL: https://issues.apache.org/jira/browse/KAFKA-5402

Build failed in Jenkins: kafka-0.11.0-jdk7 #115

See Changes: [jason] MINOR: A few logging improvements in group coordinator -- [...truncated 957.66 KB...] kafka.producer.ProducerTest > testUpdateBrokerPartitionInfo

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Comments inline: > On 5 Jun 2017, at 18:19, Jan Filipiak wrote: > > Hi > > just my few thoughts > > On 05.06.2017 11:44, Eno Thereska wrote: >> Hi there, >> >> Sorry for the late reply, I was out this past week. Looks like good progress >> was made with the

[GitHub] kafka pull request #3262: MINOR: Cache metrics were missing

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/3262 MINOR: Cache metrics were missing You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka minor-missing-metric Alternatively you

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Dong, Thanks for the explanation. I don't think anyone is denying that we should rebalance at the disk level. I think it is important to restore the disk and not wait for disk replacement. There are also other benefits of doing that which is that you don't need to opt for hot swap racks that

Re: Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

Have you considered starting a new mailing list "issues@" that gets the full load of all emails? -Matthias On 6/6/17 7:26 PM, Jeff Widman wrote: > What about also adding "Issue Resolved" to the events that hit dev? > > While I don't generally care about updates on issue progress, I do want to >

[jira] [Resolved] (KAFKA-5288) Failure in org.apache.kafka.streams.integration.ResetIntegrationTest.testReprocessingFromScratchAfterResetWithoutIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5288. Resolution: Cannot Reproduce Can't reproduce and did not reoccur. Closing for now. >

[jira] [Resolved] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5063. Resolution: Fixed Can't reproduce and did not reoccur. Closing for now. > Flaky >

[jira] [Resolved] (KAFKA-5396) Transactions System Test: Consumer reading uninterrupted from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5396. Resolution: Not A Problem Closing this since it is just a case of the consumer resetting

[jira] [Commented] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

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

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Jay, Sriram, Great point. If I understand you right, you are suggesting that we can simply use RAID-0 so that the load can be evenly distributed across disks. And even though a disk failure will bring down the enter broker, the reduced availability as compared to using KIP-112 and KIP-113

[GitHub] kafka pull request #3252: KAFKA-5385: ProducerBatch expiry should go through...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3252 --- 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-5385) Transactional Producer allows batches to expire and commits transactions regardless

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

[jira] [Assigned] (KAFKA-5396) Transactions System Test: Consumer reading uninterrupted from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5396: --- Assignee: Apurva Mehta > Transactions System Test: Consumer reading uninterrupted from

[jira] [Commented] (KAFKA-5396) Transactions System Test: Consumer reading uninterrupted from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041501#comment-16041501 ] Apurva Mehta commented on KAFKA-5396: - Yes. This is a test issue, so it isn't a blocker for the

[jira] [Updated] (KAFKA-5396) Transactions System Test: Consumer reading uninterrupted from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5396: Summary: Transactions System Test: Consumer reading uninterrupted from beginning of log can read

[GitHub] kafka pull request #3259: MINOR: A few logging improvements in group coordin...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3259 --- 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-5401) Kafka Over TLS Error - Failed to send SSL Close message - Broken Pipe

PaVan created KAFKA-5401: Summary: Kafka Over TLS Error - Failed to send SSL Close message - Broken Pipe Key: KAFKA-5401 URL: https://issues.apache.org/jira/browse/KAFKA-5401 Project: Kafka Issue

[jira] [Updated] (KAFKA-5389) Replace zkClient.exists method with zkUtils.pathExists

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

[jira] [Commented] (KAFKA-5389) Replace zkClient.exists method with zkUtils.pathExists

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

[GitHub] kafka pull request #3243: KAFKA-5389 Replace zkClient.exists method with zkU...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3243 --- 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

[GitHub] kafka pull request #3261: MINOR: Set log level for producer internals to tra...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3261 MINOR: Set log level for producer internals to trace for transactions test We need to debug most issues with the transactions system test. You can merge this pull request into a Git repository by

  1   2   >