[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252123#comment-15252123 ] Jiangjie Qin commented on KAFKA-3565: - [~jkreps] The google doc should be access

[jira] [Comment Edited] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252123#comment-15252123 ] Jiangjie Qin edited comment on KAFKA-3565 at 4/21/16 4:0

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252352#comment-15252352 ] Jiangjie Qin commented on KAFKA-3565: - [~jkreps] Yes, I agree that "free&q

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254550#comment-15254550 ] Jiangjie Qin commented on KAFKA-3565: - [~jkreps] [~ijuma] I ran the tests a few

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265529#comment-15265529 ] Jiangjie Qin commented on KAFKA-3565: - [~gwenshap] I ran a few tests and it seems

[jira] [Issue Comment Deleted] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3565: Comment: was deleted (was: [~gwenshap] I ran a few tests and it seems the performance change but

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265530#comment-15265530 ] Jiangjie Qin commented on KAFKA-3565: - [ [~gwenshap] I ran a few tests and was

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268242#comment-15268242 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I updated the results in the Go

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268998#comment-15268998 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] The tests run above have

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269491#comment-15269491 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] Thanks for help looking into thi

[jira] [Updated] (KAFKA-3565) bceunbfjcvtdvidckvjrrcklvtdnjgvlj

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3565: Summary: bceunbfjcvtdvidckvjrrcklvtdnjgvlj (was: Producer's throughput lower with compressed

[jira] [Updated] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3565: Summary: Producer's throughput lower with compressed data after KIP-31/32

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269854#comment-15269854 ] Jiangjie Qin commented on KAFKA-3565: - Woops...Touched the the yubi key accident

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270062#comment-15270062 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] The result with consumer perform

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271051#comment-15271051 ] Jiangjie Qin commented on KAFKA-725: [~junrao] I asked this question in the RB

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271795#comment-15271795 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I noticed that the consumer t

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272619#comment-15272619 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I ran the tests again with more

[jira] [Created] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

Jiangjie Qin created KAFKA-3664: --- Summary: When subscription set changes on new consumer, the partitions may be removed without offset being committed. Key: KAFKA-3664 URL: https://issues.apache.org/jira/browse

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274470#comment-15274470 ] Jiangjie Qin commented on KAFKA-3664: - [~hachikuji] I am not sure. If we still re

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274969#comment-15274969 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I didn't have time to run

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275431#comment-15275431 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I think I figured out the reason

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275924#comment-15275924 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] Yes, you are right. I changed

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275934#comment-15275934 ] Jiangjie Qin commented on KAFKA-3565: - [~ijuma] We should absolutely mention t

[jira] [Created] (KAFKA-3677) Add a producer performance tuning tool

Jiangjie Qin created KAFKA-3677: --- Summary: Add a producer performance tuning tool Key: KAFKA-3677 URL: https://issues.apache.org/jira/browse/KAFKA-3677 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275948#comment-15275948 ] Jiangjie Qin commented on KAFKA-3565: - BTW, I just created KAFKA-3677 to provi

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275970#comment-15275970 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] Yes, the value bound was suppose

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275971#comment-15275971 ] Jiangjie Qin commented on KAFKA-3565: - The batch size was 80K. It is not quite c

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275974#comment-15275974 ] Jiangjie Qin commented on KAFKA-3565: - Actually, never mind. The buffer size is

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276663#comment-15276663 ] Jiangjie Qin commented on KAFKA-3664: - [~hachikuji] That sounds reasonable. That

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277072#comment-15277072 ] Jiangjie Qin commented on KAFKA-3565: - [~guozhang] It seems that we are using

[jira] [Assigned] (KAFKA-3698) Update website documentation when it comes to the message format

[ https://issues.apache.org/jira/browse/KAFKA-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3698: --- Assignee: Jiangjie Qin > Update website documentation when it comes to the message for

[jira] [Commented] (KAFKA-3698) Update website documentation when it comes to the message format

[ https://issues.apache.org/jira/browse/KAFKA-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280310#comment-15280310 ] Jiangjie Qin commented on KAFKA-3698: - [~ijuma] Sure, just assigned it my

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280721#comment-15280721 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] [~guozhang] I think it makes s

[jira] [Commented] (KAFKA-3698) Update website documentation when it comes to the message format

[ https://issues.apache.org/jira/browse/KAFKA-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280937#comment-15280937 ] Jiangjie Qin commented on KAFKA-3698: - [~ijuma] Is the message format section of

[jira] [Updated] (KAFKA-3698) Update website documentation when it comes to the message format

[ https://issues.apache.org/jira/browse/KAFKA-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3698: Status: Patch Available (was: Open) > Update website documentation when it comes to the mess

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281192#comment-15281192 ] Jiangjie Qin commented on KAFKA-3565: - [~gwenshap] I am not sure if 32K is m

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281735#comment-15281735 ] Jiangjie Qin commented on KAFKA-3565: - Thanks for the clarification, Gwen.

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281803#comment-15281803 ] Jiangjie Qin commented on KAFKA-3565: - Got it. Yes, if the messages are k

[jira] [Commented] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282288#comment-15282288 ] Jiangjie Qin commented on KAFKA-3163: - [~xiaotao183] No, this KIP will not b

[jira] [Commented] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282348#comment-15282348 ] Jiangjie Qin commented on KAFKA-3163: - [~xiaotao183] The KIP doc listed two diffe

[jira] [Commented] (KAFKA-2960) DelayedProduce may cause message lose during repeatly leader change

[ https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047198#comment-15047198 ] Jiangjie Qin commented on KAFKA-2960: - [~iBuddha] In Kafka, the persistence guara

[jira] [Commented] (KAFKA-2948) Kafka producer does not cope well with topic deletions

[ https://issues.apache.org/jira/browse/KAFKA-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047326#comment-15047326 ] Jiangjie Qin commented on KAFKA-2948: - [~mgharat] I think TTL should not be a co

[jira] [Commented] (KAFKA-2960) DelayedProduce may cause message lose during repeatly leader change

[ https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047825#comment-15047825 ] Jiangjie Qin commented on KAFKA-2960: - Not sure I follow the issue, in that case

[jira] [Commented] (KAFKA-2960) DelayedProduce may cause message lose during repeatly leader change

[ https://issues.apache.org/jira/browse/KAFKA-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049028#comment-15049028 ] Jiangjie Qin commented on KAFKA-2960: - [~guozhang] Got it. Thanks for the explana

[jira] [Created] (KAFKA-2980) ZookeeperConsumerConnector may enter deadlock if a rebalance occurs during a stream creation.

Jiangjie Qin created KAFKA-2980: --- Summary: ZookeeperConsumerConnector may enter deadlock if a rebalance occurs during a stream creation. Key: KAFKA-2980 URL: https://issues.apache.org/jira/browse/KAFKA-2980

[jira] [Work started] (KAFKA-2980) ZookeeperConsumerConnector may enter deadlock if a rebalance occurs during a stream creation.

[ https://issues.apache.org/jira/browse/KAFKA-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2980 started by Jiangjie Qin. --- > ZookeeperConsumerConnector may enter deadlock if a rebalance occurs durin

[jira] [Updated] (KAFKA-2980) ZookeeperConsumerConnector may enter deadlock if a rebalance occurs during a stream creation.

[ https://issues.apache.org/jira/browse/KAFKA-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2980: Status: Patch Available (was: In Progress) > ZookeeperConsumerConnector may enter deadlock i

[jira] [Commented] (KAFKA-2980) ZookeeperConsumerConnector may enter deadlock if a rebalance occurs during a stream creation.

[ https://issues.apache.org/jira/browse/KAFKA-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056529#comment-15056529 ] Jiangjie Qin commented on KAFKA-2980: - [~guozhang] Can you take a looks that

[jira] [Commented] (KAFKA-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056999#comment-15056999 ] Jiangjie Qin commented on KAFKA-2143: - [~ottomata], KAFKA-2477 is a more likely c

[jira] [Commented] (KAFKA-2987) error of producing messages after topic was marked for deleteion

[ https://issues.apache.org/jira/browse/KAFKA-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057228#comment-15057228 ] Jiangjie Qin commented on KAFKA-2987: - Have you set delete.topic.enabled to

[jira] [Commented] (KAFKA-2987) error of producing messages after topic was marked for deleteion

[ https://issues.apache.org/jira/browse/KAFKA-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057242#comment-15057242 ] Jiangjie Qin commented on KAFKA-2987: - If I remember correctly, delete topi

[jira] [Updated] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3003: Component/s: core > The fetch.wait.max.ms is not honored when new log segment rolled for

[jira] [Created] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

Jiangjie Qin created KAFKA-3003: --- Summary: The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics. Key: KAFKA-3003 URL: https://issues.apache.org/jira/browse/KAFKA-3003

[jira] [Updated] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3003: Fix Version/s: 0.9.0.1 > The fetch.wait.max.ms is not honored when new log segment rolled for

[jira] [Updated] (KAFKA-3003) The fetch.wait.max.ms is not honored when new log segment rolled for low volume topics.

[ https://issues.apache.org/jira/browse/KAFKA-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3003: Affects Version/s: 0.9.0.0 > The fetch.wait.max.ms is not honored when new log segment rolled

[jira] [Updated] (KAFKA-2511) KIP-31 & KIP-32: message format change + adding timestamp to messages

[ https://issues.apache.org/jira/browse/KAFKA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2511: Summary: KIP-31 & KIP-32: message format change + adding timestamp to messages (was: KI

[jira] [Commented] (KAFKA-3025) KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068715#comment-15068715 ] Jiangjie Qin commented on KAFKA-3025: - [~apovzner] Thanks for creating the ticket

[jira] [Updated] (KAFKA-3025) KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3025: Issue Type: Sub-task (was: Improvement) Parent: KAFKA-2511 > KIP-32 (part 1):

[jira] [Updated] (KAFKA-2511) KIP-31 & KIP-32: message format change + adding timestamp to messages

[ https://issues.apache.org/jira/browse/KAFKA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2511: Description: This ticket is created for KIP 31 and KIP-32. Please refer to the KIPs for details

[jira] [Updated] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

[ https://issues.apache.org/jira/browse/KAFKA-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3026: Issue Type: Sub-task (was: Improvement) Parent: KAFKA-2511 > KIP-32 (part 2): Changes

[jira] [Assigned] (KAFKA-3025) KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3025: --- Assignee: Jiangjie Qin (was: Anna Povzner) > KIP-32 (part 1): Add timestamp field

[jira] [Assigned] (KAFKA-3026) KIP-32 (part 2): Changes in broker to over-write timestamp or reject message

[ https://issues.apache.org/jira/browse/KAFKA-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3026: --- Assignee: Jiangjie Qin (was: Anna Povzner) > KIP-32 (part 2): Changes in broker to o

[jira] [Updated] (KAFKA-3025) KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3025: Description: This JIRA is for changes for KIP-32 excluding broker checking and acting on timestamp

[jira] [Updated] (KAFKA-3025) KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3025: Summary: KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and Prod

[jira] [Work started] (KAFKA-3025) KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3025 started by Jiangjie Qin. --- > KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and >

[jira] [Created] (KAFKA-3036) Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker.

Jiangjie Qin created KAFKA-3036: --- Summary: Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker. Key: KAFKA-3036 URL: https://issues.apache.org/jira/browse/KAFKA-3036

[jira] [Updated] (KAFKA-3025) KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3025: Status: Patch Available (was: In Progress) > KIP-31&KIP-32 (part 1): Add timestamp f

[jira] [Commented] (KAFKA-2066) Replace FetchRequest / FetchResponse with their org.apache.kafka.common.requests equivalents

[ https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111034#comment-15111034 ] Jiangjie Qin commented on KAFKA-2066: - [~dajac] [~ijuma] I was thinking about

[jira] [Commented] (KAFKA-3126) Weird behavior in kafkaController on Controlled shutdowns. The leaderAndIsr in zookeeper is not updated during controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111099#comment-15111099 ] Jiangjie Qin commented on KAFKA-3126: - Currently the controlled shutdown and

[jira] [Commented] (KAFKA-3126) Weird behavior in kafkaController on Controlled shutdowns. The leaderAndIsr in zookeeper is not updated during controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111364#comment-15111364 ] Jiangjie Qin commented on KAFKA-3126: - It is because of step 4, where any ISR ch

[jira] [Commented] (KAFKA-3126) Weird behavior in kafkaController on Controlled shutdowns. The leaderAndIsr in zookeeper is not updated during controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111935#comment-15111935 ] Jiangjie Qin commented on KAFKA-3126: - [~mgharat] I thought you original confu

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111990#comment-15111990 ] Jiangjie Qin commented on KAFKA-725: [~gwenshap] [~mauzhang] Not sure if it is rel

[jira] [Commented] (KAFKA-2066) Replace FetchRequest / FetchResponse with their org.apache.kafka.common.requests equivalents

[ https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112481#comment-15112481 ] Jiangjie Qin commented on KAFKA-2066: - [~dajac] I think it would be better if you

[jira] [Commented] (KAFKA-3126) Weird behavior in kafkaController on Controlled shutdowns. The leaderAndIsr in zookeeper is not updated during controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112883#comment-15112883 ] Jiangjie Qin commented on KAFKA-3126: - That is exactly what I said. You

[jira] [Commented] (KAFKA-3130) Consistent option names for command-line tools

[ https://issues.apache.org/jira/browse/KAFKA-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112928#comment-15112928 ] Jiangjie Qin commented on KAFKA-3130: - [~ijuma] I don't think anyone's

[jira] [Commented] (KAFKA-1332) Add functionality to the offsetsBeforeTime() API

[ https://issues.apache.org/jira/browse/KAFKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115744#comment-15115744 ] Jiangjie Qin commented on KAFKA-1332: - This ticket seems a subset of KAFKA-

[jira] [Updated] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2076: Issue Type: Sub-task (was: Improvement) Parent: KAFKA-1326 > Add an API to new consumer

[jira] [Commented] (KAFKA-3147) Memory records is not writable in MirrorMaker

[ https://issues.apache.org/jira/browse/KAFKA-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120004#comment-15120004 ] Jiangjie Qin commented on KAFKA-3147: - [~junrao] [~mgharat] I think the issue is

[jira] [Commented] (KAFKA-2076) Add an API to new consumer to allow user get high watermark of partitions.

[ https://issues.apache.org/jira/browse/KAFKA-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120501#comment-15120501 ] Jiangjie Qin commented on KAFKA-2076: - [~jkreps] Good point. From consumer poin

[jira] [Commented] (KAFKA-3147) Memory records is not writable in MirrorMaker

[ https://issues.apache.org/jira/browse/KAFKA-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120613#comment-15120613 ] Jiangjie Qin commented on KAFKA-3147: - Yes, we should do that as well. >

[jira] [Created] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

Jiangjie Qin created KAFKA-3163: --- Summary: KIP-33 - Add a time based log index to Kafka Key: KAFKA-3163 URL: https://issues.apache.org/jira/browse/KAFKA-3163 Project: Kafka Issue Type: Task

[jira] [Commented] (KAFKA-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123866#comment-15123866 ] Jiangjie Qin commented on KAFKA-2143: - Thanks, [~guozhang]. I almost forgot I

[jira] [Commented] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123956#comment-15123956 ] Jiangjie Qin commented on KAFKA-1464: - It looks our purpose is to minimize

[jira] [Created] (KAFKA-3174) Re-evaluate the CRC32 class performance.

Jiangjie Qin created KAFKA-3174: --- Summary: Re-evaluate the CRC32 class performance. Key: KAFKA-3174 URL: https://issues.apache.org/jira/browse/KAFKA-3174 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3174: Affects Version/s: 0.9.0.0 Fix Version/s: 0.9.0.1 > Re-evaluate the CRC32 class performa

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124630#comment-15124630 ] Jiangjie Qin commented on KAFKA-3174: - [~ijuma] I just started writing the p

[jira] [Updated] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3174: Description: We used org.apache.kafka.common.utils.CRC32 in clients because it has better

[jira] [Assigned] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3174: --- Assignee: Jiangjie Qin > Re-evaluate the CRC32 class performa

[jira] [Updated] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3174: Status: Patch Available (was: Open) > Re-evaluate the CRC32 class performa

[jira] [Created] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

Jiangjie Qin created KAFKA-3176: --- Summary: Allow console consumer to consume from particular partitions when new consumer is used. Key: KAFKA-3176 URL: https://issues.apache.org/jira/browse/KAFKA-3176

[jira] [Created] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

Jiangjie Qin created KAFKA-3177: --- Summary: Kafka consumer can hang when position() is called on a non-existing partition. Key: KAFKA-3177 URL: https://issues.apache.org/jira/browse/KAFKA-3177 Project

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125180#comment-15125180 ] Jiangjie Qin commented on KAFKA-3177: - [~hachikuji] [~guozhang] Not sure what is

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125186#comment-15125186 ] Jiangjie Qin commented on KAFKA-3174: - Thanks for the info [~gwenshap]. We have

[jira] [Created] (KAFKA-3179) Kafka consumer delivers message whose offset is earlier than sought offset.

Jiangjie Qin created KAFKA-3179: --- Summary: Kafka consumer delivers message whose offset is earlier than sought offset. Key: KAFKA-3179 URL: https://issues.apache.org/jira/browse/KAFKA-3179 Project

[jira] [Updated] (KAFKA-3179) Kafka consumer delivers message whose offset is earlier than sought offset.

[ https://issues.apache.org/jira/browse/KAFKA-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3179: Status: Patch Available (was: Open) > Kafka consumer delivers message whose offset is earlier t

[jira] [Assigned] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3177: --- Assignee: Jiangjie Qin > Kafka consumer can hang when position() is called on a non-exist

[jira] [Work started] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3177 started by Jiangjie Qin. --- > Kafka consumer can hang when position() is called on a non-existing partit

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126619#comment-15126619 ] Jiangjie Qin commented on KAFKA-3177: - Thanks [~hachikuji], I'll submit patc

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126959#comment-15126959 ] Jiangjie Qin commented on KAFKA-3174: - [~ijuma] My test code was as below. Initi

[jira] [Commented] (KAFKA-3174) Re-evaluate the CRC32 class performance.

[ https://issues.apache.org/jira/browse/KAFKA-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127131#comment-15127131 ] Jiangjie Qin commented on KAFKA-3174: - [~ijuma] I modified the test a bit to gene

<    5   6   7   8   9   10   11   12   13   14   >