[
https://issues.apache.org/jira/browse/KAFKA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-734:
Status: Patch Available (was: Open)
Migration tool needs a revamp, it was poorly written and
[
https://issues.apache.org/jira/browse/KAFKA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian updated KAFKA-671:
-
Attachment: outOfMemFix-v2-rebase.patch
rebased
DelayedProduce requests
I don't think this is actually that hard to handle, you just need a config
to enable the new fields:
Step 1: Implement optional support for the new field with some option that
controls whether it is used
Step 2: Push all servers, still using the old format.
Step 3: Now enable the new field on
Chris Curtin created KAFKA-742:
--
Summary: Existing directories under the Kafka data directory
without any data cause process to not start
Key: KAFKA-742
URL: https://issues.apache.org/jira/browse/KAFKA-742
[
https://issues.apache.org/jira/browse/KAFKA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565696#comment-13565696
]
Jay Kreps commented on KAFKA-742:
-
Getting an error is not really bad since we assume we
[
https://issues.apache.org/jira/browse/KAFKA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565709#comment-13565709
]
Chris Curtin commented on KAFKA-742:
Thanks Jay, a better error is a good idea for
[
https://issues.apache.org/jira/browse/KAFKA-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-720.
---
Migration tool halts
Key: KAFKA-720
URL:
[
https://issues.apache.org/jira/browse/KAFKA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-568:
Labels: unit-test (was: bugs)
LogTest started failing after KAFKA-506
[
https://issues.apache.org/jira/browse/KAFKA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriram Subramanian updated KAFKA-671:
-
Attachment: outOfMemFix-v3.patch
DelayedProduce requests should not hold full
[
https://issues.apache.org/jira/browse/KAFKA-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-738:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks for the
[
https://issues.apache.org/jira/browse/KAFKA-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede closed KAFKA-738.
---
correlationId is not set in FetchRequest in AbstractFetcherThread
[
https://issues.apache.org/jira/browse/KAFKA-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-737:
--
Resolution: Fixed
Fix Version/s: 0.8
Status: Resolved (was: Patch Available)
Thanks for the
Fiddling with my Python client on 0.8, noticed something has changed
with offsets.
It seems that instead of a byte offset in the log file, the offset is
now a logical one. I had a few questions about this:
1) How is the byte offset determined by the broker? Since messages are
not fixed
Yes, offsets are now logical 0,1,2,3...
Some details on this change are here:
https://cwiki.apache.org/confluence/display/KAFKA/Keyed+Messages+Proposal
https://issues.apache.org/jira/browse/KAFKA-506
https://issues.apache.org/jira/browse/KAFKA-631
There was some previous threads on this that
[
https://issues.apache.org/jira/browse/KAFKA-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps reopened KAFKA-683:
-
Guys, this patch adds request specific stuff to RequestChannel. RequestChannel
is really not the place to be
[
https://issues.apache.org/jira/browse/KAFKA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566188#comment-13566188
]
Jay Kreps commented on KAFKA-671:
-
Took a look at this. Looks reasonable.
Other atrocities
[
https://issues.apache.org/jira/browse/KAFKA-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566215#comment-13566215
]
Jay Kreps commented on KAFKA-736:
-
This is basically good, but the comments and naming are
[
https://issues.apache.org/jira/browse/KAFKA-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566234#comment-13566234
]
Jay Kreps commented on KAFKA-683:
-
Yeah, I am on the fence about the metrics stuff, maybe
[
https://issues.apache.org/jira/browse/KAFKA-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566240#comment-13566240
]
Jay Kreps commented on KAFKA-671:
-
Okay let's sync up. I think requestObj is the devil. :-)
19 matches
Mail list logo