Fwd: Re: Time synchronization between streams

Hi Devs, May be you can shed some light.. Thanks in advance -- Forwarded message -- From: "m...@muradm.net" Date: 26 Apr 2017 19:53 Subject: Re: Time synchronization between streams To: Cc: Yes, basically I'm ok with how join works including window and retention > periods, unde

[GitHub] kafka-site pull request #55: Add Rajini to committers page

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka-site/pull/55 Add Rajini to committers page You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka-site add-rajini Alternatively you ca

[jira] [Created] (KAFKA-5133) Changing "connection refused" message from logging level "debug" into "warn"

james chien created KAFKA-5133: -- Summary: Changing "connection refused" message from logging level "debug" into "warn" Key: KAFKA-5133 URL: https://issues.apache.org/jira/browse/KAFKA-5133 Project: Kafka

[jira] [Updated] (KAFKA-5133) Changing "connection refused" message from logging level "debug" into "warn"

[ https://issues.apache.org/jira/browse/KAFKA-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james chien updated KAFKA-5133: --- Description: If broker is down, we supply logging message to let user know `java.net.ConnectException

[GitHub] kafka pull request #2924: change connection refused message from level DEBUG...

GitHub user jedichien opened a pull request: https://github.com/apache/kafka/pull/2924 change connection refused message from level DEBUG into WARN. If broker is down, we supply logging message to let user know `java.net.ConnectException: Connection refused` but not should be debug

[jira] [Updated] (KAFKA-5133) Changing "connection refused" message from logging level "debug" into "warn"

[ https://issues.apache.org/jira/browse/KAFKA-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james chien updated KAFKA-5133: --- External issue URL: https://github.com/apache/kafka/pull/2924 (was: https://github.com/apache/kafka/p

[jira] [Updated] (KAFKA-5133) Changing "connection refused" message from logging level "debug" into "warn"

[ https://issues.apache.org/jira/browse/KAFKA-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james chien updated KAFKA-5133: --- External issue URL: https://github.com/apache/kafka/pull/2850 > Changing "connection refused" message

[jira] [Updated] (KAFKA-5133) Changing "connection refused" message from logging level "debug" into "warn"

[ https://issues.apache.org/jira/browse/KAFKA-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james chien updated KAFKA-5133: --- Description: If broker is down, we supply logging message to let user know `java.net.ConnectException

[jira] [Updated] (KAFKA-5133) Changing "connection refused" message from logging level "debug" into "warn"

[ https://issues.apache.org/jira/browse/KAFKA-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james chien updated KAFKA-5133: --- Description: If broker is down, we supply logging message to let user know `java.net.ConnectException

[jira] [Updated] (KAFKA-5133) Changing "connection refused" message from logging level "debug" into "warn"

[ https://issues.apache.org/jira/browse/KAFKA-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james chien updated KAFKA-5133: --- Description: If broker is down, we supply logging message to let user know `java.net.ConnectException

[jira] [Commented] (KAFKA-5132) Abort long running transactions

[ https://issues.apache.org/jira/browse/KAFKA-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986183#comment-15986183 ] Damian Guy commented on KAFKA-5132: --- Hi [~umesh9...@gmail.com] thanks for offering to he

[jira] [Assigned] (KAFKA-5132) Abort long running transactions

[ https://issues.apache.org/jira/browse/KAFKA-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5132: - Assignee: Damian Guy > Abort long running transactions > --- > >

Re: Re: Time synchronization between streams

As i said in my previous email: > Yes. When streams are joined each partition from the joined streams are > grouped together into a single Task. Each Task maintains a record buffer > for all of the topics it is consuming from. When it is time process a > record it will chose a record from the parti

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15986208#comment-15986208 ] james chien commented on KAFKA-4830: the issue still exists? > Augment KStream.print(

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15986208#comment-15986208 ] james chien edited comment on KAFKA-4830 at 4/27/17 8:51 AM: -

RE: Kafka Connect and Partitions

Hi Gwen, Many thanks for your much appreciated offer to help with this. In answer to your questions: * Are you writing a connector or trying to use an existing one? I'm writing a new source/sink connector pipeline: folderToTopics piped into topicsToFolders. * Is the connector reading from the to

[jira] [Commented] (KAFKA-5005) JoinIntegrationTest fails occasionally

[ https://issues.apache.org/jira/browse/KAFKA-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986370#comment-15986370 ] Armin Braun commented on KAFKA-5005: No problem! Added the general fix to this PR as r

[jira] [Updated] (KAFKA-5005) JoinIntegrationTest fails occasionally

[ https://issues.apache.org/jira/browse/KAFKA-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun updated KAFKA-5005: --- Status: Patch Available (was: Open) > JoinIntegrationTest fails occasionally > --

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986384#comment-15986384 ] Arpan commented on KAFKA-4477: -- [~apurva] Request you to please check once and let us know.

[jira] [Commented] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986445#comment-15986445 ] Domenico Di Giulio commented on KAFKA-5016: --- Yes, thanks again. > Consumer hang

[jira] [Created] (KAFKA-5134) Replace zkClient.getChildren method with zkUtils.getChildren

Balint Molnar created KAFKA-5134: Summary: Replace zkClient.getChildren method with zkUtils.getChildren Key: KAFKA-5134 URL: https://issues.apache.org/jira/browse/KAFKA-5134 Project: Kafka I

[jira] [Work started] (KAFKA-5134) Replace zkClient.getChildren method with zkUtils.getChildren

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

Re: Re: Time synchronization between streams

Hi, Thanks for clarifying, so Kafka Streams Task attempts to synchronize timestamps of topics on best effort. Then Kafka Clients API users have to maintain similar functionality in order to preserve such behaviour. Does it mean that, if we have two streams having same number of events, assuming

[jira] [Updated] (KAFKA-5135) Additional Controller metrics (KIP-143)

[ https://issues.apache.org/jira/browse/KAFKA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5135: --- Fix Version/s: 0.11.0.0 > Additional Controller metrics (KIP-143) > --

[jira] [Assigned] (KAFKA-5135) Additional Controller metrics (KIP-143)

[ https://issues.apache.org/jira/browse/KAFKA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5135: -- Assignee: Ismael Juma > Additional Controller metrics (KIP-143) > -

[jira] [Created] (KAFKA-5135) Additional Controller metrics (KIP-143)

Ismael Juma created KAFKA-5135: -- Summary: Additional Controller metrics (KIP-143) Key: KAFKA-5135 URL: https://issues.apache.org/jira/browse/KAFKA-5135 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-5135) Controller Health Metrics (KIP-143)

[ https://issues.apache.org/jira/browse/KAFKA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5135: --- Summary: Controller Health Metrics (KIP-143) (was: Additional Controller metrics (KIP-143)) > Contro

[jira] [Updated] (KAFKA-5135) Controller Health Metrics (KIP-143)

[ https://issues.apache.org/jira/browse/KAFKA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5135: --- Description: Ensuring that the Kafka Controller is healthy is an important part of monitoring the hea

[DISCUSS] KIP-143: Controller Health Metrics

Hi all, We've posted "KIP-143: Controller Health Metrics" for discussion: https://cwiki.apache.org/confluence/display/KAFKA/KIP-143%3A+Controller+Health+Metrics Please take a look. Your feedback is appreciated. Thanks, Ismael

Re. Kafka Connect and Partitions

Hi Gwen, Many thanks for your much appreciated offer to help with this. In answer to your questions: * Are you writing a connector or trying to use an existing one? I'm writing a new source/sink connector pipeline: folderToTopics piped into topicsToFolders. * Is the connector reading from

[jira] [Updated] (KAFKA-3878) Exponential backoff for broker reconnect attempts

[ https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3878: --- Summary: Exponential backoff for broker reconnect attempts (was: Support exponential backoff for brok

Re: [DISCUSS] KIP-143: Controller Health Metrics

Hi, We (Heroku) are very excited about this KIP, as we've struggled a bit with controller stability recently. Having these additional metrics would be wonderful. I'd like to ensure polling these metrics *doesn't* hold any locks etc, because, as noted in https://issues.apache.org/jira/browse/KAFKA

[jira] [Created] (KAFKA-5136) Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry

Damian Guy created KAFKA-5136: - Summary: Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry Key: KAFKA-5136 URL: https://issues.apache.org/jira/browse/KAFKA-5136 Project: Kafka I

[jira] [Work started] (KAFKA-5136) Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry

[ https://issues.apache.org/jira/browse/KAFKA-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5136 started by Damian Guy. - > Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry >

[GitHub] kafka pull request #2925: KAFKA-5136: move coordinatorEpoch from WriteTxnMar...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2925 KAFKA-5136: move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry Moving the coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry will generate fewer broker send requests You ca

Re: [DISCUSS] KIP-143: Controller Health Metrics

Hi Tom, Yes, the plan is to merge KAFKA-5028 first and then use a lock-free approach for the new metrics. I considered mentioning that in the KIP given KAFKA-5120, but didn't in the end. I'll add it to make it clear. Regarding locks, they are removed by KAFKA-5028, as you say. So, if I understan

[jira] [Commented] (KAFKA-5136) Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry

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

Re: [DISCUSS] KIP-143: Controller Health Metrics

Ismael, Great, that sounds lovely. I'd like a `Timer` (using yammer metrics parlance) over how long it took to process the event, so we can get at p99 and max times spent processing things. Maybe we could even do a log at warning level if event processing takes over some timeout? Thanks Tom On

[jira] [Resolved] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian resolved KAFKA-5016. Resolution: Not A Bug > Consumer hang in poll method while rebalancing is in progress >

[jira] [Assigned] (KAFKA-5131) WriteTxnMarkers and complete commit/abort on partition immigration

[ https://issues.apache.org/jira/browse/KAFKA-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5131: - Assignee: Damian Guy > WriteTxnMarkers and complete commit/abort on partition immigration > -

[jira] [Updated] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-5028: --- Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Available) Issue res

[GitHub] kafka pull request #2816: KAFKA-5028: convert kafka controller to a single-t...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2816 --- 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-5028) convert kafka controller to a single-threaded event queue model

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

[jira] [Assigned] (KAFKA-3878) Exponential backoff for broker reconnect attempts

[ https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3878: -- Assignee: Ismael Juma > Exponential backoff for broker reconnect attempts > ---

[jira] [Commented] (KAFKA-3878) Exponential backoff for broker reconnect attempts

[ https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986874#comment-15986874 ] Ismael Juma commented on KAFKA-3878: KIP: https://cwiki.apache.org/confluence/display

[jira] [Updated] (KAFKA-3878) Exponential backoff for broker reconnect attempts

[ https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3878: --- Labels: kip (was: ) > Exponential backoff for broker reconnect attempts > ---

[DISCUSS] KIP-144: Exponential backoff for broker reconnect attempts

Hi all, Dana Powers posted a PR a while back for exponential backoff for broker reconnect attempts. Because it adds a config, a KIP is required and Dana seems to be busy so I posted it: https://cwiki.apache.org/confluence/display/KAFKA/KIP- 144%3A+Exponential+backoff+for+broker+reconnect+attempts

Re: Kafka-Streams: Cogroup

Hi Kyle, I believe Guozhang has now given you permission to edit the KIP wiki at https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals. Could you see if you can add this there? Many thanks Eno On Wed, Apr 26, 2017 at 6:00 PM, Kyle Winkelman wrote: > Thank you for your r

Re: [DISCUSS] KIP-144: Exponential backoff for broker reconnect attempts

This is a great suggestion. I like how we just do it by default instead of making it a choice users need to figure out. Avoiding connection storms is great. One concern. If I understand the formula for effective maximum backoff correctly, then with default maximum of 1000ms and default backoff of

Re: Kafka Connect and Partitions

That's great! So we tracked this down to the source connector not properly partitioning data. Do you set both key and value? It sounds a bit like maybe all your records have the exact same key, which means they all get hashed to the same partition. Can you check that? On Thu, Apr 27, 2017 at 3:22

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15987050#comment-15987050 ] Matthias J. Sax commented on KAFKA-4830: This JIRA is still open yes. But it's blo

[GitHub] kafka pull request #2926: KAFKA-5131: WriteTxnMarkers and complete commit/ab...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2926 KAFKA-5131: WriteTxnMarkers and complete commit/abort on partition immigration write txn markers and complete the commit/abort for transactions in PrepareXX state during partition immigration. You ca

[jira] [Commented] (KAFKA-5131) WriteTxnMarkers and complete commit/abort on partition immigration

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

[jira] [Commented] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987101#comment-15987101 ] Onur Karaman commented on KAFKA-5028: - Shortly after check-in, I noticed a bug: the pa

[jira] [Updated] (KAFKA-4755) SimpleBenchmark test fails for streams

[ https://issues.apache.org/jira/browse/KAFKA-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4755: Resolution: Fixed Status: Resolved (was: Patch Available) > SimpleBenchmark test fails for

[jira] [Assigned] (KAFKA-5006) KeyValueStore.put may throw exception unrelated to the current put attempt

[ https://issues.apache.org/jira/browse/KAFKA-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-5006: --- Assignee: Eno Thereska > KeyValueStore.put may throw exception unrelated to the current put a

[GitHub] kafka pull request #2927: KAFKA-5107: remove preferred replica election stat...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2927 KAFKA-5107: remove preferred replica election state from ControllerContext KAFKA-5028 moves the controller to a single-threaded model, so we would no longer have work interleaved between preferr

[jira] [Commented] (KAFKA-5107) remove preferred replica election state from ControllerContext

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

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987228#comment-15987228 ] Apurva Mehta commented on KAFKA-4477: - Your stack trace alone doesn't indicate that yo

[jira] [Work started] (KAFKA-5107) remove preferred replica election state from ControllerContext

[ https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5107 started by Onur Karaman. --- > remove preferred replica election state from ControllerContext >

[jira] [Updated] (KAFKA-5107) remove preferred replica election state from ControllerContext

[ https://issues.apache.org/jira/browse/KAFKA-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5107: Status: Patch Available (was: In Progress) > remove preferred replica election state from Controlle

Re: [DISCUSS] KIP-143: Controller Health Metrics

Thanks for the KIP - couple of comments: - Do you intend to actually use yammer metrics? or use kafka-metrics and split the timer into an explicit rate and time? I think long term we ought to move off yammer and use kafka-metrics only. Actually either is fine, but we should ideally use only one in

[ANNOUCE] Apache Kafka 0.10.2.1 Released

The Apache Kafka community is pleased to announce the release for Apache Kafka 0.10.2.1. This is a bug fix release that fixes 29 issues in 0.10.2.0. All of the changes in this release can be found in the release notes: *https://archive.apache.org/dist/kafka/0.10.2.1/RELEASE_NOTES.html

[GitHub] kafka pull request #2928: HOTFIX [WIP]: Check on not owned partitions

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2928 HOTFIX [WIP]: Check on not owned partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KHotfix-check-not-owned-par

[jira] [Created] (KAFKA-5137) Controlled shutdown timeout message improvement

Dustin Cote created KAFKA-5137: -- Summary: Controlled shutdown timeout message improvement Key: KAFKA-5137 URL: https://issues.apache.org/jira/browse/KAFKA-5137 Project: Kafka Issue Type: Improve

[jira] [Created] (KAFKA-5138) MirrorMaker doesn't exit on send failure occasionally

Dustin Cote created KAFKA-5138: -- Summary: MirrorMaker doesn't exit on send failure occasionally Key: KAFKA-5138 URL: https://issues.apache.org/jira/browse/KAFKA-5138 Project: Kafka Issue Type: B

[jira] [Updated] (KAFKA-5137) Controlled shutdown timeout message improvement

[ https://issues.apache.org/jira/browse/KAFKA-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5137: --- Labels: newbie (was: ) > Controlled shutdown timeout message improvement > --

[jira] [Updated] (KAFKA-5138) MirrorMaker doesn't exit on send failure occasionally

[ https://issues.apache.org/jira/browse/KAFKA-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5138: --- Labels: newbie (was: ) > MirrorMaker doesn't exit on send failure occasionally >

[GitHub] kafka-site pull request #55: Add Rajini to committers page

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

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987661#comment-15987661 ] Joseph Aliase commented on KAFKA-4477: -- [~apurva] Im hitting this issue. Please refer

[GitHub] kafka pull request #2923: MINOR: Fix a few transaction coordinator issues

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

SIEMs Supported

Hi, What SIEMs are supported with Kafka messaging bus? RSA, NetWitness, QRADAR,etc? Would like to have a list. Thanks! -Kristen

Re: [DISCUSS] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

Hi, Colin, Thanks for the KIP. Looks good overall. Just a few minor comments. 1. The controller is responsible for managing the state of topics. So, it makes sense for create/delete topic requests to be sent to the controller. The controller is not responsible for managing ACLs right now. So, it'

[jira] [Resolved] (KAFKA-4818) Implement transactional clients

[ https://issues.apache.org/jira/browse/KAFKA-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4818. Resolution: Fixed Issue resolved by pull request 2840 [https://github.com/apache/kafka/pull/

[GitHub] kafka pull request #2869: KAFKA-5086; Update topic expiry time in Metadata e...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2869 --- 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 #2840: KAFKA-4818: Exactly once transactional clients

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2840 --- 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-4818) Implement transactional clients

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

[jira] [Commented] (KAFKA-5086) Update topic expiry time in Metadata every time the topic metadata is requested

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

[jira] [Resolved] (KAFKA-5086) Update topic expiry time in Metadata every time the topic metadata is requested

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

[jira] [Commented] (KAFKA-5122) Kafka Streams unexpected off-heap memory growth

[ https://issues.apache.org/jira/browse/KAFKA-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987806#comment-15987806 ] Guozhang Wang commented on KAFKA-5122: -- [~jon_fuseelements] Thanks a lots for reporti

[jira] [Comment Edited] (KAFKA-5122) Kafka Streams unexpected off-heap memory growth

[ https://issues.apache.org/jira/browse/KAFKA-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987806#comment-15987806 ] Guozhang Wang edited comment on KAFKA-5122 at 4/27/17 10:16 PM:

[jira] [Assigned] (KAFKA-5122) Kafka Streams unexpected off-heap memory growth

[ https://issues.apache.org/jira/browse/KAFKA-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5122: Assignee: Guozhang Wang > Kafka Streams unexpected off-heap memory growth > ---

[jira] [Resolved] (KAFKA-5122) Kafka Streams unexpected off-heap memory growth

[ https://issues.apache.org/jira/browse/KAFKA-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5122. -- Resolution: Fixed > Kafka Streams unexpected off-heap memory growth > --

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

See Changes: [jason] KAFKA-4818; Exactly once transactional clients -- [...truncated 835.78 KB...] kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > sh

[jira] [Created] (KAFKA-5139) Transient failure ConsumerBounceTest.testConsumptionWithBrokerFailures

Jason Gustafson created KAFKA-5139: -- Summary: Transient failure ConsumerBounceTest.testConsumptionWithBrokerFailures Key: KAFKA-5139 URL: https://issues.apache.org/jira/browse/KAFKA-5139 Project: Kaf

[jira] [Resolved] (KAFKA-5139) Transient failure ConsumerBounceTest.testConsumptionWithBrokerFailures

[ https://issues.apache.org/jira/browse/KAFKA-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5139. Resolution: Duplicate Sorry for the noise. > Transient failure ConsumerBounceTest.testConsu

[jira] [Reopened] (KAFKA-4801) Transient test failure (part 2): ConsumerBounceTest.testConsumptionWithBrokerFailures

[ https://issues.apache.org/jira/browse/KAFKA-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reopened KAFKA-4801: -- > Transient test failure (part 2): > ConsumerBounceTest.testConsumptionWithBrokerFailures > ---

[jira] [Commented] (KAFKA-4801) Transient test failure (part 2): ConsumerBounceTest.testConsumptionWithBrokerFailures

[ https://issues.apache.org/jira/browse/KAFKA-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987843#comment-15987843 ] Jason Gustafson commented on KAFKA-4801: Recent occurrence: https://jenkins.conflu

[GitHub] kafka pull request #2915: KAFKA-5119: Ensure global metrics are empty before...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2915 --- 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-5119) Transient test failure SocketServerTest.testMetricCollectionAfterShutdown

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

[jira] [Resolved] (KAFKA-5119) Transient test failure SocketServerTest.testMetricCollectionAfterShutdown

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

Re: [VOTE] KIP-112 - Handle disk failure for JBOD

Hi, Dong, Thanks for the proposal. +1. Just one minor comment. in "3. Broker bootstraps with bad log directories", when a broker receives a LeaderAndIsrRequest with isNewReplica=False but not found on any good log directory, if all log directories are good, it seems that we should create the repl

[GitHub] kafka pull request #2886: KAFKA-5101 Remove KafkaController's incrementContr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2886 --- 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] [Resolved] (KAFKA-5101) Remove KafkaController's incrementControllerEpoch method parameter

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

[jira] [Commented] (KAFKA-5101) Remove KafkaController's incrementControllerEpoch method parameter

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

Re: [VOTE] KIP-112 - Handle disk failure for JBOD

Thanks for the vote Jun! I think that statement is probably OK because it assumes that broker has bad log directories. If all log directories are good, the replica should be created in one of the good log directories. It is clarified in the wiki that "Even if isNewReplica=false and replica is not

[GitHub] kafka pull request #2929: KAFKA-4763; Handle disk failure for JBOD (KIP-112)

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2929 KAFKA-4763; Handle disk failure for JBOD (KIP-112) You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong28/kafka KAFKA-4763 Alternatively y

[jira] [Commented] (KAFKA-4763) Handle disk failure for JBOD (KIP-112)

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

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

See Changes: [junrao] KAFKA-5028; convert kafka controller to a single-threaded event queue -- [...truncated 2.42 MB...] at hudson.util.SequentialExecutionQueue$Q

Re: [ANNOUCE] Apache Kafka 0.10.2.1 Released

Thanks for managing the release Gwen. And thanks to everyone who contributed. :) Ismael On Thu, Apr 27, 2017 at 7:52 PM, Gwen Shapira wrote: > The Apache Kafka community is pleased to announce the release for Apache > Kafka 0.10.2.1. This is a bug fix release that fixes 29 issues in 0.10.2.0. >

  1   2   >