By centralizing offset management (with the new Commit/FetchOffsets
APIs), consuming is now much simpler and no longer relies on clients
connecting directly to ZooKeeper.
As such, I'm wondering what the fate of ZookeeperConsumerConnector is.
Will it continue to be supported, or will it be repl
> As such, I'm wondering what the fate of ZookeeperConsumerConnector is.
> Will it continue to be supported, or will it be replaced by a non-ZK
> implementation (one that uses SimpleConsumer maybe?).
We've been collecting feedback on a client re-design proposal for Kafka
0.9. Feel free to add com
[
https://issues.apache.org/jira/browse/KAFKA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-708:
Attachment: kafka-708-v2.patch
1. Good point. I moved setting the leader to -1 to the removeReplicaF
[
https://issues.apache.org/jira/browse/KAFKA-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559793#comment-13559793
]
Neha Narkhede commented on KAFKA-705:
-
+1
> Controlled shutdown doesn'
[
https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559813#comment-13559813
]
Neha Narkhede commented on KAFKA-330:
-
Hey Prashanth, how's this JIRA coming along ?
Jay Kreps created KAFKA-718:
---
Summary: kafka-run-class.sh should use reasonable gc settings
Key: KAFKA-718
URL: https://issues.apache.org/jira/browse/KAFKA-718
Project: Kafka
Issue Type: Bug
Af
Neha Narkhede created KAFKA-719:
---
Summary: Kafka broker shuts down due to irrecoverable IO error
Key: KAFKA-719
URL: https://issues.apache.org/jira/browse/KAFKA-719
Project: Kafka
Issue Type: B
Neha Narkhede created KAFKA-720:
---
Summary: Migration tool halts
Key: KAFKA-720
URL: https://issues.apache.org/jira/browse/KAFKA-720
Project: Kafka
Issue Type: Bug
Components: core
[
https://issues.apache.org/jira/browse/KAFKA-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede reassigned KAFKA-718:
---
Assignee: Neha Narkhede
> kafka-run-class.sh should use reasonable gc settings
> -
[
https://issues.apache.org/jira/browse/KAFKA-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-720:
Attachment: migration-tool-halts
> Migration tool halts
>
>
>
[
https://issues.apache.org/jira/browse/KAFKA-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559875#comment-13559875
]
Jay Kreps commented on KAFKA-719:
-
Isn't this the same as KAFKA-695?
> Kaf
Jun Rao created KAFKA-721:
-
Summary: FileNotFoundException on index file
Key: KAFKA-721
URL: https://issues.apache.org/jira/browse/KAFKA-721
Project: Kafka
Issue Type: Bug
Components: core,
John Fung created KAFKA-722:
---
Summary: Path typos in kafka-run-class.sh
Key: KAFKA-722
URL: https://issues.apache.org/jira/browse/KAFKA-722
Project: Kafka
Issue Type: Bug
Reporter: John
[
https://issues.apache.org/jira/browse/KAFKA-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559897#comment-13559897
]
Jun Rao commented on KAFKA-721:
---
The following is what happened:
1. We are starting a followe
[
https://issues.apache.org/jira/browse/KAFKA-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559901#comment-13559901
]
Neha Narkhede commented on KAFKA-721:
-
>> Not quite sure how the index file can be gone
[
https://issues.apache.org/jira/browse/KAFKA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-722:
Attachment: kafka-722.patch
Upload kafka-722.patch
> Path typos in kafka-run-class.sh
> ---
[
https://issues.apache.org/jira/browse/KAFKA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-722:
Status: Patch Available (was: Open)
Fixing the path from scala_2.8.0 => scala-2.8.0
> Path
Neha Narkhede created KAFKA-723:
---
Summary: Scala's default case class toString() is very inefficient
Key: KAFKA-723
URL: https://issues.apache.org/jira/browse/KAFKA-723
Project: Kafka
Issue Typ
[
https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559935#comment-13559935
]
Jay Kreps commented on KAFKA-695:
-
Some research:
1. Taking also KAFKA-719 we have examples
[
https://issues.apache.org/jira/browse/KAFKA-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559968#comment-13559968
]
Joel Koshy commented on KAFKA-705:
--
Thanks for reviewing. I checked-in the incremental pat
[
https://issues.apache.org/jira/browse/KAFKA-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-716:
Priority: Blocker (was: Major)
> SimpleConsumerPerformance does not consume all available messa
[
https://issues.apache.org/jira/browse/KAFKA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-722.
---
> Path typos in kafka-run-class.sh
>
>
> Key: KAFKA-7
[
https://issues.apache.org/jira/browse/KAFKA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559972#comment-13559972
]
Neha Narkhede commented on KAFKA-722:
-
+1
> Path typos in kafka-run-c
[
https://issues.apache.org/jira/browse/KAFKA-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-722:
Resolution: Fixed
Assignee: John Fung
Status: Resolved (was: Patch Available)
> P
Pablo Barrera created KAFKA-724:
---
Summary: Allow automatic socket.send.buffer from operating system
Key: KAFKA-724
URL: https://issues.apache.org/jira/browse/KAFKA-724
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559984#comment-13559984
]
Pablo Barrera commented on KAFKA-724:
-
Apparently this is already fixed in 0.8.
[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560026#comment-13560026
]
Rajasekar Elango commented on KAFKA-133:
[~charmalloc] Are we expecting 0.7.3 rele
[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560026#comment-13560026
]
Rajasekar Elango edited comment on KAFKA-133 at 1/22/13 9:13 PM:
[
https://issues.apache.org/jira/browse/KAFKA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-703:
Labels: p3 (was: )
> A fetch request in Fetch Purgatory can double count the bytes from the sam
[
https://issues.apache.org/jira/browse/KAFKA-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-699.
---
> Disallow clients to set replicaId in FetchRequest
>
[
https://issues.apache.org/jira/browse/KAFKA-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-720:
Labels: p1 (was: )
> Migration tool halts
>
>
> Key: KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-695:
Labels: p1 (was: p2)
> Broker shuts down due to attempt to read a closed index file
> -
[
https://issues.apache.org/jira/browse/KAFKA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-703:
Affects Version/s: (was: 0.8)
0.8.1
> A fetch request in Fetch Purgat
[
https://issues.apache.org/jira/browse/KAFKA-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-703:
Labels: (was: p3)
> A fetch request in Fetch Purgatory can double count the bytes from the sam
[
https://issues.apache.org/jira/browse/KAFKA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-570:
Labels: bugs (was: bugs p4)
> Kafka should not need snappy jar at runtime
> ---
[
https://issues.apache.org/jira/browse/KAFKA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-570:
Priority: Major (was: Blocker)
> Kafka should not need snappy jar at runtime
>
[
https://issues.apache.org/jira/browse/KAFKA-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-700:
Labels: p2 (was: p1)
> log client ip when we log each request on the broker
> -
[
https://issues.apache.org/jira/browse/KAFKA-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-696:
Priority: Critical (was: Major)
> Fix toString() API for all requests to make logging easier to
[
https://issues.apache.org/jira/browse/KAFKA-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede reassigned KAFKA-720:
---
Assignee: Sriram Subramanian
> Migration tool halts
>
>
>
[
https://issues.apache.org/jira/browse/KAFKA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede reassigned KAFKA-695:
---
Assignee: Jun Rao
> Broker shuts down due to attempt to read a closed index file
> ---
[
https://issues.apache.org/jira/browse/KAFKA-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-721:
Labels: p1 (was: )
> FileNotFoundException on index file
> ---
[
https://issues.apache.org/jira/browse/KAFKA-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-719:
Labels: bugs p1 (was: bugs)
> Kafka broker shuts down due to irrecoverable IO error
> -
[
https://issues.apache.org/jira/browse/KAFKA-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560156#comment-13560156
]
John Fung commented on KAFKA-714:
-
Thanks Jun for the patch. I have verified it with the la
Chris Riccomini created KAFKA-725:
-
Summary: Broker Exception: Attempt to read with a maximum offset
less than start offset
Key: KAFKA-725
URL: https://issues.apache.org/jira/browse/KAFKA-725
Project:
Swapnil Ghike created KAFKA-726:
---
Summary: Add ReplicaFetcherThread name to mbean names
Key: KAFKA-726
URL: https://issues.apache.org/jira/browse/KAFKA-726
Project: Kafka
Issue Type: Bug
Af
[
https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560246#comment-13560246
]
Neha Narkhede commented on KAFKA-725:
-
This looks exactly like KAFKA-698. Chris, did yo
[
https://issues.apache.org/jira/browse/KAFKA-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-726:
Attachment: KAFKA-726.patch
As described in the description above.
> Add ReplicaFet
Neha,
I see, so that is a fairly substantial change, ofcourse it has its
advantage of guaranteeing a higher degree of durability but as a
significant cost (round trip that the consumer has to wait for). I know
someone mentioned creating a asych. consumer with a future.
Do you have a 'gut' feelin
This is a good question.
As mentioned we have some experience running this with no ack and there are
a lot of downsides. We considered making the ack optional, but this would
complicate the producer api since we could give back the offset only in the
case where there is an ack.
Thinking about it
Jun Rao created KAFKA-727:
-
Summary: broker can still expose uncommitted data to a consumer
Key: KAFKA-727
URL: https://issues.apache.org/jira/browse/KAFKA-727
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560402#comment-13560402
]
Jun Rao commented on KAFKA-727:
---
One way to fix this is for FileMessageSet.searchFor() to ret
[
https://issues.apache.org/jira/browse/KAFKA-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560410#comment-13560410
]
Jay Kreps commented on KAFKA-727:
-
Fantastic catch.
I think another fix is to just save th
[
https://issues.apache.org/jira/browse/KAFKA-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao reassigned KAFKA-727:
-
Assignee: Jay Kreps
> broker can still expose uncommitted data to a consumer
> ---
[
https://issues.apache.org/jira/browse/KAFKA-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560412#comment-13560412
]
Jun Rao commented on KAFKA-727:
---
Jay, sure, you can take this on. The way we saw this is that
[
https://issues.apache.org/jira/browse/KAFKA-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560421#comment-13560421
]
Jun Rao commented on KAFKA-726:
---
Thanks for the patch. In ReplicaFetcherManager, it's actuall
[
https://issues.apache.org/jira/browse/KAFKA-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560423#comment-13560423
]
Swapnil Ghike commented on KAFKA-726:
-
I actually deleted brokerConfig.brokerId. Replic
[
https://issues.apache.org/jira/browse/KAFKA-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560428#comment-13560428
]
Jun Rao commented on KAFKA-726:
---
Sorry, I missed the brokerId change. Yes, you are right.
Th
57 matches
Mail list logo
