[jira] [Created] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

The Data Lorax created KAFKA-3456: - Summary: In-house KafkaMetric misreports metrics when periodically observed Key: KAFKA-3456 URL: https://issues.apache.org/jira/browse/KAFKA-3456 Project: Kafka

[jira] [Commented] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210084#comment-15210084 ] Li Jinyu commented on KAFKA-493: I have the same problem with 0.8.2.2 cluster, the CPU usage is really

[jira] [Updated] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] The Data Lorax updated KAFKA-3456: -- Description: The metrics captured by Kafka through the in-house {{SampledStat}} suffer from

[jira] [Commented] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210092#comment-15210092 ] Cosmin Marginean commented on KAFKA-493: I can confirm that we're been running 0.9.0.1 for over a

[jira] [Updated] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] The Data Lorax updated KAFKA-3456: -- Description: The metrics captured by Kafka through the in-house {{SampledStat}} suffer from

[GitHub] kafka pull request: Update Sender.java

GitHub user SoyeeDst opened a pull request: https://github.com/apache/kafka/pull/1130 Update Sender.java Avoid expired RecordBatch to be sent out to network You can merge this pull request into a Git repository by running: $ git pull https://github.com/SoyeeDst/kafka soyee

[jira] [Comment Edited] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210092#comment-15210092 ] Cosmin Marginean edited comment on KAFKA-493 at 3/24/16 11:19 AM: -- I can

[jira] [Updated] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cosmin Marginean updated KAFKA-493: --- Attachment: 0.9.0.1-upgrade.png > High CPU usage on inactive server >

[jira] [Commented] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

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

[GitHub] kafka pull request: KAFKA-3453; Transient test failures due to Min...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1131 KAFKA-3453; Transient test failures due to MiniKDC port allocation strategy Temporarily copy fixed `MiniKdc` class until `MiniKdc` 2.8.0 is released. You can merge this pull request into a Git

[jira] [Commented] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210060#comment-15210060 ] The Data Lorax commented on KAFKA-3456: --- [~aauradkar], I see you've made changes in this area -

[jira] [Commented] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210094#comment-15210094 ] Ismael Juma commented on KAFKA-493: --- Thanks for reporting back Cosmin. > High CPU usage on inactive

[GitHub] kafka pull request: KAFKA-3445

GitHub user rnpridgeon opened a pull request: https://github.com/apache/kafka/pull/1132 KAFKA-3445 Currently the property TASKS_MAX_CONFIG is not validated against nonsensical values such as 0. This patch leverages the Range.atLeast() method to ensure value is at least 1. You

Kafka Connect ++ Kafka Streams

Hello Kafka people! Great to see Kafka Streams coming along, the design validates (and in many way supersedes) my own findings from working with various stream processing systems/frameworks and eventually ending-up using just a small custom library built directly around Kafka. I have set out

Reg : kafka consumer to dynamically detect topics added

Hi Team, I'm using KafkaConsumer to consume messages from Kafka server (topics).. * It works fine for topics created before starting Consumer code... * But the problem is, it will not work if the topics created dynamically(i mean to say after consumer code started), but

[jira] [Commented] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

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

[jira] [Updated] (KAFKA-3465) kafka.tools.ConsumerOffsetChecker won't align with kafka New Consumer mode

[ https://issues.apache.org/jira/browse/KAFKA-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BrianLing updated KAFKA-3465: - Description: 1. When we enable mirrorMake to migrate Kafka event from one to other with "new.consumer"

[jira] [Created] (KAFKA-3465) kafka.tools.ConsumerOffsetChecker won't align with kafka New Consumer mode

BrianLing created KAFKA-3465: Summary: kafka.tools.ConsumerOffsetChecker won't align with kafka New Consumer mode Key: KAFKA-3465 URL: https://issues.apache.org/jira/browse/KAFKA-3465 Project: Kafka

[jira] [Created] (KAFKA-3457) KafkaConsumer.committed(...) hangs forever if port number is wrong

Harald Kirsch created KAFKA-3457: Summary: KafkaConsumer.committed(...) hangs forever if port number is wrong Key: KAFKA-3457 URL: https://issues.apache.org/jira/browse/KAFKA-3457 Project: Kafka

[jira] [Commented] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210492#comment-15210492 ] Andrea Cosentino commented on KAFKA-3449: - PR submitted:

[GitHub] kafka pull request: [KAFKA-3458] Selector should throw InterruptEx...

GitHub user sruehl opened a pull request: https://github.com/apache/kafka/pull/1135 [KAFKA-3458] Selector should throw InterruptException when interrupted. https://issues.apache.org/jira/browse/KAFKA-3458 You can merge this pull request into a Git repository by running: $ git

[GitHub] kafka pull request: KAFKA-3349: Rename filterOut() to filterNot() ...

Github user oscerd closed the pull request at: https://github.com/apache/kafka/pull/1133 --- 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-3349) Add system tests for upgrade from 0.8.2.x to 0.10.0.0

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

Re: Reg : kafka consumer to dynamically detect topics added

Hi Siddu, The consumer supports a configuration option "metadata.max.age.ms" which basically controls how often topic metadata is fetched. By default, this is set fairly high (5 minutes), which means it will take up to 5 minutes to discover new topics matching your regular expression. You can set

[jira] [Commented] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210419#comment-15210419 ] Simon Cooper commented on KAFKA-3296: - No, these are the only references to Expired in the logs:

[jira] [Commented] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210423#comment-15210423 ] Ryan P commented on KAFKA-3445: --- [~ewencp], sorry about that I should have read that beforehand. >

[GitHub] kafka pull request: KAFKA-3349: Rename filterOut() to filterNot() ...

GitHub user oscerd opened a pull request: https://github.com/apache/kafka/pull/1133 KAFKA-3349: Rename filterOut() to filterNot() to achieve better termi… …nology Hi all, This is my first contribution and I hope it will be good. The PR is related to

[jira] [Comment Edited] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210492#comment-15210492 ] Andrea Cosentino edited comment on KAFKA-3449 at 3/24/16 4:25 PM: -- PR

[jira] [Commented] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

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

[jira] [Commented] (KAFKA-3349) Add system tests for upgrade from 0.8.2.x to 0.10.0.0

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

[jira] [Created] (KAFKA-3458) Selector should throw InterruptException when interrupted

Sebastian Rühl created KAFKA-3458: - Summary: Selector should throw InterruptException when interrupted Key: KAFKA-3458 URL: https://issues.apache.org/jira/browse/KAFKA-3458 Project: Kafka

[jira] [Commented] (KAFKA-3458) Selector should throw InterruptException when interrupted

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

consumer group, why commit requests are not considered as effective heartbeats?

Hi there! It was probably sent to the wrong list? Wish I can get some answer here. -- Forwarded message -- From: Zaiming Shi Date: Wed, Mar 23, 2016 at 6:03 PM Subject: consumer group, why commit requests are not considered as effective heartbeats? To:

[jira] [Commented] (KAFKA-2939) Make AbstractConfig.logUnused() tunable for clients

[ https://issues.apache.org/jira/browse/KAFKA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15210641#comment-15210641 ] Guozhang Wang commented on KAFKA-2939: -- I feel that the second option, i.e. making sure all

[jira] [Commented] (KAFKA-3407) ErrorLoggingCallback trims helpful diagnostic information.

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

[GitHub] kafka pull request: KAFKA-3407 - ErrorLoggingCallback trims helpfu...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1079 --- 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-3459) Returning zero task configurations from a connector does not properly clean up existing tasks

Ewen Cheslack-Postava created KAFKA-3459: Summary: Returning zero task configurations from a connector does not properly clean up existing tasks Key: KAFKA-3459 URL:

[GitHub] kafka pull request: KAFKA-3453; Transient test failures due to Min...

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

Re: consumer group, why commit requests are not considered as effective heartbeats?

Hi Zaiming, I responded on the user list. -Jason On Thu, Mar 24, 2016 at 8:31 AM, Zaiming Shi wrote: > Hi there! > > It was probably sent to the wrong list? > Wish I can get some answer here. > > -- Forwarded message -- > From: Zaiming Shi

[jira] [Commented] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

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

[jira] [Commented] (KAFKA-3434) Add old ConsumerRecord constructor for compatibility

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

[GitHub] kafka pull request: KAFKA-3445

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1132 --- 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-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3445: - Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved

[jira] [Commented] (KAFKA-3453) Transient test failures due to MiniKDC port allocation strategy

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

Consumer Errors...

I am running into ILLEGAL_GENERATION occurred while committing offsets for group reported by ConsumerCoordinator. I have auto commit enabled. Can someone give any tips as to what this means? After this error, the consumer is pretty much rendered useless - unable to consume any more messages.

Re: [VOTE] KIP-43: Kafka SASL enhancements

Gwen, Thank you. I have pinged Ismael, Harsha and Jun Rao for PR review. If any of them has time for reviewing the PR, I will update the PR over the weekend. If you can suggest any other reviewers, I can ping them too. Many thanks. On Thu, Mar 24, 2016 at 5:03 PM, Gwen Shapira

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

See Changes: [me] KAFKA-3445: Validate TASKS_MAX_CONFIG's lower bound -- [...truncated 1637 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASSED

Re: [VOTE] KIP-43: Kafka SASL enhancements

This can be discussed in the review. If there's good test coverage, is low risk and passes review and gets merged before Monday morning... We won't be doing an extra release candidate just for this though. Gwen On Thu, Mar 24, 2016 at 1:21 AM, Rajini Sivaram < rajinisiva...@googlemail.com>

Re: Kafka Connect ++ Kafka Streams

On Thu, Mar 24, 2016 at 4:46 AM, Michal Hariš wrote: > Hello Kafka people! > > Great to see Kafka Streams coming along, the design validates (and in many > way supersedes) my own findings from working with various stream processing > systems/frameworks and eventually

[jira] [Resolved] (KAFKA-3407) ErrorLoggingCallback trims helpful diagnostic information.

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

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

See Changes: [me] KAFKA-3407 - ErrorLoggingCallback trims helpful diagnostic information. -- [...truncated 1631 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest >

[GitHub] kafka pull request: KAFKA-3460: Remove old 0.7 KafkaMigrationTool

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1136 KAFKA-3460: Remove old 0.7 KafkaMigrationTool You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka remove-07-migration

[jira] [Commented] (KAFKA-3460) Remove old 0.7 KafkaMigrationTool

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

[jira] [Updated] (KAFKA-3460) Remove old 0.7 KafkaMigrationTool

[ https://issues.apache.org/jira/browse/KAFKA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3460: --- Status: Patch Available (was: Open) > Remove old 0.7 KafkaMigrationTool >

[jira] [Created] (KAFKA-3460) Remove old 0.7 KafkaMigrationTool

Grant Henke created KAFKA-3460: -- Summary: Remove old 0.7 KafkaMigrationTool Key: KAFKA-3460 URL: https://issues.apache.org/jira/browse/KAFKA-3460 Project: Kafka Issue Type: Task Affects

Re: Messages corrupted in kafka

You mentioned that you saw few corrupted messages, (< 0.1%). If so are you able to see some corrupted messages if you produce, say, 10M messages? On Wed, Mar 23, 2016 at 9:40 PM, sunil kalva wrote: > I am using java client and kafka 0.8.2, since events are corrupted in >

[GitHub] kafka pull request: HOTFIX: set timestamp in SinkNode

GitHub user ymatsuda opened a pull request: https://github.com/apache/kafka/pull/1137 HOTFIX: set timestamp in SinkNode @guozhangwang Setting the timestamp in produced records in SinkNode. This forces the producer record's timestamp same as the context's timestamp. You can

Re: [VOTE] KIP-43: Kafka SASL enhancements

Rajini, I think the vote didn't pass yet? If I can see correctly, Harsha and I are the only committers who voted, so we are missing a 3rd vote. Gwen On Thu, Mar 24, 2016 at 11:24 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > Gwen, > > Thank you. I have pinged Ismael, Harsha and

Re: [VOTE] KIP-43: Kafka SASL enhancements

Gwen, Ah, I clearly don't know the rules. So it looks like it would not really be possible to get this into 0.10.0.0 after all. Rajini On Thu, Mar 24, 2016 at 8:38 PM, Gwen Shapira wrote: > Rajini, > > I think the vote didn't pass yet? > If I can see correctly, Harsha and I

Re: [VOTE] KIP-43: Kafka SASL enhancements

I'm afraid it will be a challenge. I see few options: 1. Jun should be back in the office tomorrow. If he votes +1 and agrees that the PR is ready to merge and is safe and important enough to double-commit - this could get in yet. 2. Same as above, but not in time for the Monday release

[jira] [Commented] (KAFKA-2939) Make AbstractConfig.logUnused() tunable for clients

[ https://issues.apache.org/jira/browse/KAFKA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209825#comment-15209825 ] Ewen Cheslack-Postava commented on KAFKA-2939: -- Probably worth thinking through how this is

[GitHub] kafka pull request: KAFKA-3463: change default receive buffer size...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1140 KAFKA-3463: change default receive buffer size for consumer to 64K You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3463

[jira] [Commented] (KAFKA-3463) Change default consumer receive buffer size to 64K

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

[jira] [Created] (KAFKA-3464) Connect security system tests

Ewen Cheslack-Postava created KAFKA-3464: Summary: Connect security system tests Key: KAFKA-3464 URL: https://issues.apache.org/jira/browse/KAFKA-3464 Project: Kafka Issue Type: Bug

[GitHub] kafka pull request: KAFKA-3464: Add system tests for Connect with ...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1141 KAFKA-3464: Add system tests for Connect with Kafka security enabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka

[jira] [Commented] (KAFKA-3464) Connect security system tests

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

KStream/KTable prioritization/initial offset

Really digging Kafka Streams so far, nice work all. I'm interested in being able to materialize one or more KTables in full before the rest of the topology begins processing messages. This seems fundamentally useful since it allows you to get your database tables replicated up off the change

Re: [VOTE] KIP-43: Kafka SASL enhancements

Gwen, Is it still possible to include this in 0.10.0.0? Thanks, Rajini On Wed, Mar 23, 2016 at 11:08 PM, Gwen Shapira wrote: > Sorry! Got distracted by the impending release! > > +1 on the current revision of the KIP. > > On Wed, Mar 23, 2016 at 3:33 PM, Harsha

RE: [VOTE] KIP-43: Kafka SASL enhancements

+1 (non-binding) on the revised KIP > Date: Thu, 24 Mar 2016 08:21:14 + > Subject: Re: [VOTE] KIP-43: Kafka SASL enhancements > From: rajinisiva...@googlemail.com > To: dev@kafka.apache.org > > Gwen, > > Is it still possible to include this in

[jira] [Commented] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209863#comment-15209863 ] Ewen Cheslack-Postava commented on KAFKA-3445: -- [~Ryan P] Not nit picky at all, this is

[jira] [Created] (KAFKA-3461) Fix typos in Kafka web documentations

Dongjoon Hyun created KAFKA-3461: Summary: Fix typos in Kafka web documentations Key: KAFKA-3461 URL: https://issues.apache.org/jira/browse/KAFKA-3461 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3461) Fix typos in Kafka web documentations

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

[jira] [Commented] (KAFKA-3462) Allow SinkTasks to disable consumer offset commit

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

[GitHub] kafka pull request: KAFKA-3462: Allow SinkTasks to disable consume...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1139 KAFKA-3462: Allow SinkTasks to disable consumer offset commit You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka

[jira] [Updated] (KAFKA-3462) Allow SinkTasks to disable consumer offset commit

[ https://issues.apache.org/jira/browse/KAFKA-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3462: -- Description: SinkTasks should be able to disable consumer offset commit if they manage offsets in the

[jira] [Updated] (KAFKA-3463) Change default consumer receive buffer size to 64K

[ https://issues.apache.org/jira/browse/KAFKA-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3463: --- Fix Version/s: 0.10.0.0 > Change default consumer receive buffer size to 64K >

[jira] [Created] (KAFKA-3463) Change default consumer receive buffer size to 64K

Jason Gustafson created KAFKA-3463: -- Summary: Change default consumer receive buffer size to 64K Key: KAFKA-3463 URL: https://issues.apache.org/jira/browse/KAFKA-3463 Project: Kafka Issue

[GitHub] kafka pull request: KAFKA-3461: Fix typos in Kafka web documentati...

GitHub user dongjoon-hyun opened a pull request: https://github.com/apache/kafka/pull/1138 KAFKA-3461: Fix typos in Kafka web documentations. This PR fixes 8 typos in HTML files of `docs` module. I wrote explicitly here since Github sometimes does not highlight the corrections on

[jira] [Work started] (KAFKA-3462) Allow SinkTasks to disable consumer offset commit

[ https://issues.apache.org/jira/browse/KAFKA-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3462 started by Liquan Pei. - > Allow SinkTasks to disable consumer offset commit >

[jira] [Created] (KAFKA-3462) Allow SinkTasks to disable consumer offset commit

Liquan Pei created KAFKA-3462: - Summary: Allow SinkTasks to disable consumer offset commit Key: KAFKA-3462 URL: https://issues.apache.org/jira/browse/KAFKA-3462 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3462) Allow SinkTasks to disable consumer offset commit

[ https://issues.apache.org/jira/browse/KAFKA-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3462: -- Status: Patch Available (was: In Progress) > Allow SinkTasks to disable consumer offset commit >

[jira] [Commented] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15211302#comment-15211302 ] Jay Kreps commented on KAFKA-3456: -- I think the tradeoff is between getting a current estimate and using

Reg: Contribution to Kafka

Hi Kafka Contributors, I am interested in contributing to kafka open source. Can you please provide some suggestions in understanding the code of kafka. Can you please provide any method you have followed to understand the code. Regards, BigDataDev