[jira] [Commented] (KAFKA-5396) 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&focusedCommentId=16040367#comment-16040367 ] Apurva Mehta commented on KAFKA-5396: - [~hachikuji] found the issue. {noformat} [2017

[jira] [Updated] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5395: --- Fix Version/s: 0.11.0.0 > Distributed Herder Deadlocks on Shutdown > -

[jira] [Updated] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5395: --- Priority: Critical (was: Major) > Distributed Herder Deadlocks on Shutdown >

[jira] [Commented] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040399#comment-16040399 ] Ismael Juma commented on KAFKA-5395: [~rsivaram], would you have time to look into thi

[jira] [Updated] (KAFKA-5396) 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: 0.11.0.0 > Consumer reading uninterrupted from beginning of log can read the same > me

[jira] [Commented] (KAFKA-5396) 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&focusedCommentId=16040405#comment-16040405 ] Ismael Juma commented on KAFKA-5396: I assume we need to fix this for 0.11.0.0? > Con

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040449#comment-16040449 ] Magnus Reftel commented on KAFKA-5390: -- Our records are typically small, but potentia

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040468#comment-16040468 ] Ismael Juma commented on KAFKA-5390: [~magnus.reftel], I am not sure I understand. By

[jira] [Resolved] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Reftel resolved KAFKA-5390. -- Resolution: Invalid Working as intended. The testcase ends up sending two batches, the first one

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040485#comment-16040485 ] Magnus Reftel commented on KAFKA-5390: -- Will do. Thanks! > First records in batch re

[jira] [Assigned] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-5395: - Assignee: Rajini Sivaram > Distributed Herder Deadlocks on Shutdown > ---

[jira] [Commented] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040490#comment-16040490 ] Rajini Sivaram commented on KAFKA-5395: --- [~ijuma] Will take a look at this today, th

[jira] [Commented] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040511#comment-16040511 ] Rajini Sivaram commented on KAFKA-5395: --- This was fixed in trunk, I will add the fix

[jira] [Comment Edited] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040511#comment-16040511 ] Rajini Sivaram edited comment on KAFKA-5395 at 6/7/17 8:40 AM: -

[GitHub] kafka pull request #3253: MINOR: Fixed Non-Final Close Method + its Duplicat...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3253 MINOR: Fixed Non-Final Close Method + its Duplication Cherry-picked from trunk. You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivar

[jira] [Created] (KAFKA-5397) streams are not recovering from LockException during rebalancing

Jozef Koval created KAFKA-5397: -- Summary: streams are not recovering from LockException during rebalancing Key: KAFKA-5397 URL: https://issues.apache.org/jira/browse/KAFKA-5397 Project: Kafka I

[jira] [Work started] (KAFKA-5388) Replace zkClient.subscribe*Changes method with an equivalent zkUtils method

[ https://issues.apache.org/jira/browse/KAFKA-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5388 started by Balint Molnar. > Replace zkClient.subscribe*Changes method with an equivalent zkUtils method > -

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

I'm largely in agreement with what Guozhang has suggested, i.e., StateRestoreContext shouldn't have any setters on it and also need to have the end offset available such that people can use it derive progress. Slightly different, maybe the StateRestoreContext interface could be: long beginOffset()

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

Hi Jun/Ismael, Sounds good to me. Thanks, Damian On Tue, 6 Jun 2017 at 23:08 Ismael Juma wrote: > Hi Jun, > > The console consumer issue also came up in a conversation I was having > recently. Seems like the config/server.properties change is a reasonable > compromise given that we have other

[GitHub] kafka pull request #3254: MINOR: set group initial rebalance delay to 0 in s...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3254 MINOR: set group initial rebalance delay to 0 in server.properties override the setting of `group.initial.rebalance.delay` in server.properties You can merge this pull request into a Git repository by

Starting contribution on Apache Kafka project

Hi Kafka devs, I'd like to start contributing on Kafka and as I read here (http://kafka.apache.org/contributing.html) I'm contacting you to be added to the contributor list so that I could pick up easy JIRAs for getting familiar with it. Is that possible ? Thanks ! Paolo. Paolo Patierno S

[jira] [Assigned] (KAFKA-3741) KStream config for changelog min.in.sync.replicas

[ https://issues.apache.org/jira/browse/KAFKA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-3741: - Assignee: Damian Guy > KStream config for changelog min.in.sync.replicas > --

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

I forgot to address the broker versus client-side point that Jun raised. We discussed passing the delay via the request and we were unable to make a strong case for it. It seems like tools that use a single consumer and group management (like the Console Consumer) are such a case though. Changing t

[jira] [Created] (KAFKA-5398) Joins on GlobalKTable don't work properly when combined with Avro and the Confluent Schema Registry

Benjamin Bargeton created KAFKA-5398: Summary: Joins on GlobalKTable don't work properly when combined with Avro and the Confluent Schema Registry Key: KAFKA-5398 URL: https://issues.apache.org/jira/browse/KAF

[GitHub] kafka pull request #3255: KAFKA-3741: add min.insync.replicas config to Stre...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3255 KAFKA-3741: add min.insync.replicas config to Streams Allow users to specify `min.insync.replicas` via StreamsConfig. Default to `null` so that the server settting will be used. If `replication.factor`

[jira] [Commented] (KAFKA-3741) KStream config for changelog min.in.sync.replicas

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

[jira] [Updated] (KAFKA-3741) KStream config for changelog min.in.sync.replicas

[ https://issues.apache.org/jira/browse/KAFKA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3741: -- Status: Patch Available (was: Open) > KStream config for changelog min.in.sync.replicas > -

[jira] [Resolved] (KAFKA-5380) Transient test failure: KafkaConsumerTest.testChangingRegexSubscription

[ https://issues.apache.org/jira/browse/KAFKA-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-5380. --- Resolution: Fixed Fix Version/s: 0.11.1.0 0.11.0.0 Issue resolved by

[GitHub] kafka pull request #3238: KAFKA-5380: Fix transient failure in KafkaConsumer...

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

[jira] [Commented] (KAFKA-5380) Transient test failure: KafkaConsumerTest.testChangingRegexSubscription

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

[jira] [Resolved] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-5395. --- Resolution: Fixed Fix Version/s: (was: 0.11.0.0) 0.10.2.2 Issue

[jira] [Updated] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5395: --- Fix Version/s: 0.11.0.0 > Distributed Herder Deadlocks on Shutdown > -

[GitHub] kafka pull request #3256: MINOR: Updated .gitignore for excluding out direct...

GitHub user ppatierno opened a pull request: https://github.com/apache/kafka/pull/3256 MINOR: Updated .gitignore for excluding out directory While building the project using IntelliJ IDEA, the "out" directory is generated but not excluded for commit by the .gitignore. Someone could

[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&focusedCommentId=16040795#comment-16040795 ] Andres Gomez Ferrer commented on KAFKA-4633: Hi all, I have some question abo

[jira] [Comment Edited] (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&focusedCommentId=16040795#comment-16040795 ] Andres Gomez Ferrer edited comment on KAFKA-4633 at 6/7/17 12:42 PM: ---

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

All: Solid state drives Depreciation - straightline vs accelerated Cost of capital - present value versus future value of the dollar Outright buy or loan from from bank(interest rate of loan) Frequency of the SATA drive failure Cost of the

Build failed in Jenkins: kafka-0.10.2-jdk7 #171

See Changes: [rajinisivaram] KAFKA-5395; Remove synchronization from AbstractCoordinator.close, -- [...truncated 159.08 KB...] kafka.log.LogTest > testParseTopicPartition

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

See

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

See Changes: [rajinisivaram] KAFKA-5380: Fix transient failure in KafkaConsumerTest, close consumers -- [...truncated 2.38 MB...] org.apache.kafka.streams.kstream.intern

[jira] [Updated] (KAFKA-5363) Add ability to batch restore and receive restoration stats.

[ https://issues.apache.org/jira/browse/KAFKA-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-5363: --- Description: Currently, when restoring a state store in a Kafka Streams application, we put one key-v

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

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3257 KAFKA-5329: Fix order of replica list in metadata cache You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-5329-fix-order-of-repli

[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&focusedCommentId=16040942#comment-16040942 ] ASF GitHub Bot commented on KAFKA-5329: --- GitHub user ijuma opened a pull request:

[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: --- Status: Patch Available (was: Open) > Replica list in the metadata cache on the broker may have diffe

[jira] [Assigned] (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 reassigned KAFKA-5329: -- Assignee: Ismael Juma > Replica list in the metadata cache on the broker may have different ord

[GitHub] kafka pull request #3254: MINOR: set group initial rebalance delay to 0 in s...

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

[GitHub] kafka pull request #3214: MINOR: syntax brush for java / bash / json / text

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

[GitHub] kafka pull request #3253: KAFKA-5395: Remove synchronization from AbstractCo...

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

[jira] [Commented] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040965#comment-16040965 ] ASF GitHub Bot commented on KAFKA-5395: --- Github user rajinisivaram closed the pull r

[GitHub] kafka pull request #3258: KAFKA-5394; Fix disconnections due to timeouts in ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3258 KAFKA-5394; Fix disconnections due to timeouts in AdminClient You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-5394-admin-client-

[jira] [Commented] (KAFKA-5394) KafkaAdminClient#timeoutCallsInFlight does not work as expected

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

[jira] [Created] (KAFKA-5399) Crash Kafka & Zookeper with an basic Nmap Scan

Ivan Morozov created KAFKA-5399: --- Summary: Crash Kafka & Zookeper with an basic Nmap Scan Key: KAFKA-5399 URL: https://issues.apache.org/jira/browse/KAFKA-5399 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-5378) Last Stable Offset not returned in Fetch request

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

[GitHub] kafka pull request #3248: KAFKA-5378: Return LSO in FetchResponse plus some ...

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

[jira] [Commented] (KAFKA-5378) Last Stable Offset not returned in Fetch request

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

[GitHub] kafka pull request #3247: MINOR: log4j template should accept log_level

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

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

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3259 MINOR: A few logging improvements in group coordinator You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka group-coordinator-logg

[jira] [Created] (KAFKA-5400) NetworkClient should have timeouts which can be set differently on each request

Colin P. McCabe created KAFKA-5400: -- Summary: NetworkClient should have timeouts which can be set differently on each request Key: KAFKA-5400 URL: https://issues.apache.org/jira/browse/KAFKA-5400 Pro

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

See

[jira] [Assigned] (KAFKA-5382) Log recovery can fail if topic names contain one of the index suffixes

[ https://issues.apache.org/jira/browse/KAFKA-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5382: -- Assignee: (was: Jason Gustafson) > Log recovery can fail if topic names contain one

[jira] [Updated] (KAFKA-5382) Log recovery can fail if topic names contain one of the index suffixes

[ https://issues.apache.org/jira/browse/KAFKA-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5382: --- Fix Version/s: 0.10.2.2 > Log recovery can fail if topic names contain one of the index suffix

[jira] [Resolved] (KAFKA-5394) KafkaAdminClient#timeoutCallsInFlight does not work as expected

[ https://issues.apache.org/jira/browse/KAFKA-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5394. Resolution: Fixed Fix Version/s: 0.11.0.0 Issue resolved by pull request 3250 [https://github

[jira] [Commented] (KAFKA-5394) KafkaAdminClient#timeoutCallsInFlight does not work as expected

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

[GitHub] kafka pull request #3250: KAFKA-5394. KafkaAdminClient#timeoutCallsInFlight ...

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

[GitHub] kafka pull request #3260: Fixed path to log4j config file

GitHub user iotmani opened a pull request: https://github.com/apache/kafka/pull/3260 Fixed path to log4j config file While running the quickstart tutorial, I came across this exception due to bad file URI: D:\gdrive\workspace\Pulse\kafka_2.11-0.10.2.0>bin\windows\kafka-ser

[GitHub] kafka pull request #3258: KAFKA-5394; Fix disconnections due to timeouts in ...

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

[jira] [Commented] (KAFKA-5394) KafkaAdminClient#timeoutCallsInFlight does not work as expected

[ https://issues.apache.org/jira/browse/KAFKA-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041364#comment-16041364 ] ASF GitHub Bot commented on KAFKA-5394: --- Github user ijuma closed the pull request a

[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 ru

[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 enab

[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&focusedCommentId=16041384#comment-16041384 ] ASF GitHub Bot commented on KAFKA-5389: --- Github user asfgit closed the pull request

[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) I

[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 Ty

[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 enab

[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 the

[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 beginn

[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&focusedCommentId=16041501#comment-16041501 ] Apurva Mehta commented on KAFKA-5396: - Yes. This is a test issue, so it isn't a blocke

[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 requ

[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 enab

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 will

[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&focusedCommentId=16041515#comment-16041515 ] ASF GitHub Bot commented on KAFKA-5385: --- Github user asfgit closed the pull request

[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 off

[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 > ResetInt

[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. > Failur

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 >

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 c

[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-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 discussions either way. Let me rec

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 PAS

[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

[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] [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 ded

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 java.nio.file.Files.createDirectory(Fi

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 a

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 progress was made with the discus

[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 Issu

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

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 q

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 new mailing list "issues

[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 Alt

[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&focusedCommentId=16041718#comment-16041718 ] ASF GitHub Bot commented on KAFKA-5404: --- GitHub user cmccabe opened a pull request:

  1   2   >