[jira] [Updated] (KAFKA-1591) Clean-up Unnecessary stack trace in error/warn logs

[ https://issues.apache.org/jira/browse/KAFKA-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Sharma updated KAFKA-1591: --- Attachment: Jira-1591-SocketConnection-Warning.patch First Patch File - Changed SocketConnecti

[jira] [Updated] (KAFKA-1591) Clean-up Unnecessary stack trace in error/warn logs

[ https://issues.apache.org/jira/browse/KAFKA-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Sharma updated KAFKA-1591: --- Status: Patch Available (was: Open) > Clean-up Unnecessary stack trace in error/warn logs > -

Re: High Level Consumer and Commit

Either use the SimpleConsumer which gives you much finer-grained control, or (this worked with 0.7) spin up a ConsumerConnection (this is a HighLevel consumer concept) per partition, turn off auto-commit. Philip - http://www.philipotoole.com On Tuesd

High Level Consumer and Commit

Hi Kafka Group, I have to pull the data from the Topic and index into Elastic Search with Bulk API and wanted to commit only batch that has been committed and still continue to read from topic further on same topic. I have auto commit to be off. List batch . while (iterator.hasNext()) {

[jira] [Resolved] (KAFKA-1061) Break-down sendTime to multipleSendTime

[ https://issues.apache.org/jira/browse/KAFKA-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1061. -- Resolution: Won't Fix > Break-down sendTime to multipleSendTime > --

[jira] [Resolved] (KAFKA-1498) new producer performance and bug improvements

[ https://issues.apache.org/jira/browse/KAFKA-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-1498. -- Resolution: Fixed > new producer performance and bug improvements >

[jira] [Updated] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-998: Resolution: Won't Fix Status: Resolved (was: Patch Available) > Producer should not retry on

[jira] [Commented] (KAFKA-998) Producer should not retry on non-recoverable error codes

[ https://issues.apache.org/jira/browse/KAFKA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118925#comment-14118925 ] Guozhang Wang commented on KAFKA-998: - This ticket can be closed as won't fix since we

Re: How to debug unit test in Eclipse

Yes, it is possible. Looks like you are hitting some issues, so if you can be more specific about the details, someone can help you out. On Tue, Sep 2, 2014 at 2:34 PM, Abhishek Sharma wrote: > Thanks for the reply. > > Everything is working fine. I just wish to execute unit test cases from > e

Re: Review Request 25236: Patch for KAFKA-1619

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25236/#review52093 --- Ship it! Ship It! - Neha Narkhede On Sept. 1, 2014, 5:55 p.m., J

Re: Review Request 24676: Fix KAFKA-1583

> On Sept. 2, 2014, 5:53 p.m., Jun Rao wrote: > > Are you including the changes in kafka-1616 too? That would be fine. > > However, the comments in the other jira also need to be addressed in this > > patch. I was not intending to include the changes of KAFKA-1616. The plan is to first check

Re: Offset Request with timestamp

The semantic of the offset API is to "return the latest possible offset of the message that is appended no later than the given timestamp". For implementation, it will get the starting offset of the log segment that is created no later than the given timestamp, and hence if your log segment contain

Re: Review Request 25136: Patch for KAFKA-1610

> On Aug. 29, 2014, 9:01 p.m., Guozhang Wang wrote: > > LGTM. One minor thing about comments is that we do not need to say > > "Changing mapValues to map" since we do not need to leave comments > > indicating code change, but just comment on the purpose of coding. We can > > generally say sth.

[jira] [Commented] (KAFKA-1583) Kafka API Refactoring

[ https://issues.apache.org/jira/browse/KAFKA-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118696#comment-14118696 ] Guozhang Wang commented on KAFKA-1583: -- Updated reviewboard https://reviews.apache.or

[jira] [Updated] (KAFKA-1583) Kafka API Refactoring

[ https://issues.apache.org/jira/browse/KAFKA-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1583: - Attachment: KAFKA-1583_2014-09-02_13:37:47.patch > Kafka API Refactoring > - >

Re: Review Request 24676: Fix KAFKA-1583

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24676/ --- (Updated Sept. 2, 2014, 8:37 p.m.) Review request for kafka. Bugs: KAFKA-1583

[jira] [Updated] (KAFKA-1616) Purgatory Size and Num.Delayed.Request metrics are incorrect

[ https://issues.apache.org/jira/browse/KAFKA-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1616: - Attachment: KAFKA-1616_2014-09-02_13:23:13.patch > Purgatory Size and Num.Delayed.Request metrics

Re: Review Request 25155: Fix KAFKA-1616

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25155/ --- (Updated Sept. 2, 2014, 8:22 p.m.) Review request for kafka. Bugs: KAFKA-1616

[jira] [Commented] (KAFKA-1616) Purgatory Size and Num.Delayed.Request metrics are incorrect

[ https://issues.apache.org/jira/browse/KAFKA-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118674#comment-14118674 ] Guozhang Wang commented on KAFKA-1616: -- Updated reviewboard https://reviews.apache.or

[jira] [Updated] (KAFKA-1616) Purgatory Size and Num.Delayed.Request metrics are incorrect

[ https://issues.apache.org/jira/browse/KAFKA-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1616: - Attachment: KAFKA-1616_2014-09-02_12:58:07.patch > Purgatory Size and Num.Delayed.Request metrics

[jira] [Commented] (KAFKA-1616) Purgatory Size and Num.Delayed.Request metrics are incorrect

[ https://issues.apache.org/jira/browse/KAFKA-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118628#comment-14118628 ] Guozhang Wang commented on KAFKA-1616: -- Updated reviewboard https://reviews.apache.or

Re: Review Request 25155: Fix KAFKA-1616

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25155/ --- (Updated Sept. 2, 2014, 7:57 p.m.) Review request for kafka. Bugs: KAFKA-1616

Build failed in Jenkins: Kafka-trunk #259

See Changes: [joe.stein] KAFKA-1485 Upgrade to Zookeeper 3.4.6 missing file -- [...truncated 1311 lines...] at kafka.integration.KafkaServerTestHarness$class.setUp(KafkaServerTestHarness.scal

Re: Review Request 25155: Fix KAFKA-1616

> On Sept. 2, 2014, 4:51 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/server/RequestPurgatory.scala, line 251 > > > > > > It's probably better to expose an api that returns the size of the > > queue, instead of

Re: How to debug unit test in Eclipse

Thanks for the reply. Everything is working fine. I just wish to execute unit test cases from eclipse IDE and want to debug them. Is this possible?? On Tuesday 02 September 2014 11:53 PM, Neha Narkhede wrote: Could you give more details about what errors/issues you ran into while trying to ru

[jira] [Commented] (KAFKA-1485) Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run

[ https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118483#comment-14118483 ] Guozhang Wang commented on KAFKA-1485: -- Confirmed it is in now. Thanks. > Upgrade to

Re: How to debug unit test in Eclipse

Could you give more details about what errors/issues you ran into while trying to run the unit tests? On Mon, Sep 1, 2014 at 12:34 AM, Abhishek Sharma wrote: > Hi, > > Recently, I setup Kafka workspace using Eclipse and did try to run several > unit test cases from Eclipse only. > > Hard luck,

[jira] [Commented] (KAFKA-1485) Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run

[ https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118459#comment-14118459 ] Joe Stein commented on KAFKA-1485: -- yup, sorry about that, git pull and try again please

[jira] [Commented] (KAFKA-1485) Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run

[ https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118449#comment-14118449 ] Guozhang Wang commented on KAFKA-1485: -- Hello Joe, it seems the file kafka.tools.Zook

Re: Review Request 24676: Fix KAFKA-1583

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24676/#review52044 --- Are you including the changes in kafka-1616 too? That would be fine.

Offset Request with timestamp

Hi, My usecase is to fetch the offsets for a given topic from X milliseconds ago. If I use the offset api https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-OffsetAPI to do this and pass in a timestamp of (now() - X), I get the earliest offse

Re: Review Request 25155: Fix KAFKA-1616

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25155/#review52036 --- core/src/main/scala/kafka/server/RequestPurgatory.scala

[jira] [Commented] (KAFKA-1507) Using GetOffsetShell against non-existent topic creates the topic unintentionally

[ https://issues.apache.org/jira/browse/KAFKA-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118324#comment-14118324 ] Sriharsha Chintalapani commented on KAFKA-1507: --- 2 weeks ping. [~jkreps] [~j

[jira] [Updated] (KAFKA-1507) Using GetOffsetShell against non-existent topic creates the topic unintentionally

[ https://issues.apache.org/jira/browse/KAFKA-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-1507: -- Reviewer: Jay Kreps > Using GetOffsetShell against non-existent topic creates th

[jira] [Commented] (KAFKA-1282) Disconnect idle socket connection in Selector

[ https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118317#comment-14118317 ] Jun Rao commented on KAFKA-1282: Thanks for the latest patch. I was trying to do some loca

[jira] [Commented] (KAFKA-1510) Force offset commits when migrating consumer offsets from zookeeper to kafka

[ https://issues.apache.org/jira/browse/KAFKA-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118294#comment-14118294 ] nicu marasoiu commented on KAFKA-1510: -- [~jjkoshy] Hi, can you check my patch + comme