[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

[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

[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

[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

[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

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

See

[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

[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

[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=16041086#comment-16041086 ] ASF GitHub Bot commented on KAFKA-5378: --- Github user asfgit closed the pull request at:

[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

[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

[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] [Created] (KAFKA-5396) Consumer reading from beginning of log can read the same message multiple times.

Apurva Mehta created KAFKA-5396: --- Summary: Consumer reading from beginning of log can read the same message multiple times. Key: KAFKA-5396 URL: https://issues.apache.org/jira/browse/KAFKA-5396

[jira] [Commented] (KAFKA-5396) Consumer reading 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=16040297#comment-16040297 ] Apurva Mehta commented on KAFKA-5396: - The logs for the entire run (including debug broker logs and

[jira] [Updated] (KAFKA-5396) Consumer reading 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: Attachment: KAFKA-5396.tar.gz > Consumer reading from beginning of log can read the same message

[jira] [Commented] (KAFKA-5396) Consumer reading 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=16040301#comment-16040301 ] Apurva Mehta commented on KAFKA-5396: - Also, there are no aborted transactions in the log. >

[jira] [Commented] (KAFKA-5396) Consumer reading 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=16040316#comment-16040316 ] Apurva Mehta commented on KAFKA-5396: - 38012 out of 38500 duplicates were from this one partition. >

[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=16040257#comment-16040257 ] Michael Jaschob commented on KAFKA-5395: Probably didn't mean to synchronize the public

[jira] [Commented] (KAFKA-5396) Consumer reading 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=16040309#comment-16040309 ] Apurva Mehta commented on KAFKA-5396: - Running the following {noformat} amehta-macbook-pro:3 apurva$

[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 ] Apurva Mehta updated KAFKA-5396: Summary: Consumer reading uninterrupted from beginning of log can read the same message multiple

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

I think Ram's point is that in place failure is pretty complicated, and this is meant to be a cost saving feature, we should construct an argument for it grounded in data. Assume an annual failure rate of 1% (reasonable, but data is available online), and assume it takes 3 days to get the drive

[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

[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=16041364#comment-16041364 ] ASF GitHub Bot commented on KAFKA-5394: --- Github user ijuma closed the pull request at:

[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

[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

[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=16041232#comment-16041232 ] ASF GitHub Bot commented on KAFKA-5394: --- Github user asfgit closed the pull request at:

[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

[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

[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] [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 #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:

[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-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=16040485#comment-16040485 ] Magnus Reftel commented on KAFKA-5390: -- Will do. Thanks! > First records in batch rejected but

[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=16040367#comment-16040367 ] Apurva Mehta commented on KAFKA-5396: - [~hachikuji] found the issue. {noformat} [2017-06-07

[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=16040399#comment-16040399 ] Ismael Juma commented on KAFKA-5395: [~rsivaram], would you have time to look into this? cc [~ewencp]

[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=16040468#comment-16040468 ] Ismael Juma commented on KAFKA-5390: [~magnus.reftel], I am not sure I understand. By using `flush`,

[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=16040449#comment-16040449 ] Magnus Reftel commented on KAFKA-5390: -- Our records are typically small, but potentially huge. Doing

[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

[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=16040490#comment-16040490 ] Rajini Sivaram commented on KAFKA-5395: --- [~ijuma] Will take a look at this today, thanks. >

[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

[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

[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=16040511#comment-16040511 ] Rajini Sivaram edited comment on KAFKA-5395 at 6/7/17 8:40 AM: --- This was

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

[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

[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=16040405#comment-16040405 ] Ismael Juma commented on KAFKA-5396: I assume we need to fix this for 0.11.0.0? > Consumer reading

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

[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=16040511#comment-16040511 ] Rajini Sivaram commented on KAFKA-5395: --- This was fixed in trunk, I will add the fix to 0.10.2

[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

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

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

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

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

[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

[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

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

[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

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

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

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

[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

[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

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

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

[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

[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=16040711#comment-16040711 ] ASF GitHub Bot commented on KAFKA-3741: --- GitHub user dguy opened a pull request:

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

[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

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

See

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

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

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

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

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

[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

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

[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

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 newbie (was: kip needs-kip newbie) > Augment KStream.print() to allow users pass

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

[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

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

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

  1   2   >