[
https://issues.apache.org/jira/browse/KAFKA-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Ozeritskiy updated KAFKA-2164:
-
Description:
If log.logEndOffset < leaderStartOffset the follower resets its offset and
p
Hey Aditya,
This is a great! A couple of comments:
1. Leaving the file config in place is definitely the least disturbance.
But let's really think about getting rid of the files and just have one
config mechanism. There is always a tendency to make everything pluggable
which so often just leads t
+1!
-Jay
On Thu, Apr 30, 2015 at 6:12 AM, Ismael Juma wrote:
> Hi all,
>
> Kafka currently uses a combination of Review Board and JIRA for
> contributions and code review. In my opinion, this makes contribution and
> code review a bit harder than it has to be.
>
> I think the approach used by S
[
https://issues.apache.org/jira/browse/KAFKA-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Ozeritskiy updated KAFKA-2165:
-
Status: Patch Available (was: Open)
> ReplicaFetcherThread: data loss on unknown exceptio
[
https://issues.apache.org/jira/browse/KAFKA-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Ozeritskiy updated KAFKA-2165:
-
Attachment: KAFKA-2165.patch
> ReplicaFetcherThread: data loss on unknown exception
>
Alexey Ozeritskiy created KAFKA-2165:
Summary: ReplicaFetcherThread: data loss on unknown exception
Key: KAFKA-2165
URL: https://issues.apache.org/jira/browse/KAFKA-2165
Project: Kafka
Is
[
https://issues.apache.org/jira/browse/KAFKA-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Ozeritskiy updated KAFKA-2164:
-
Status: Patch Available (was: Open)
> ReplicaFetcherThread: suspicious log message on res
[
https://issues.apache.org/jira/browse/KAFKA-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Ozeritskiy updated KAFKA-2164:
-
Attachment: KAFKA-2164.patch
> ReplicaFetcherThread: suspicious log message on reset offse
Ismael,
We will also need to figure out if we need CONTRIBUTING.md like the
following to take care of the Apache licensing stuff.
https://github.com/apache/spark/blob/master/CONTRIBUTING.md
As for merging changes, I think squashing the commits will be ideal during
merge. Also, it would be great
Alexey Ozeritskiy created KAFKA-2164:
Summary: ReplicaFetcherThread: suspicious log message on reset
offset
Key: KAFKA-2164
URL: https://issues.apache.org/jira/browse/KAFKA-2164
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525421#comment-14525421
]
Jiangjie Qin commented on KAFKA-1788:
-
I took a shot to incorporate the solution to th
[
https://issues.apache.org/jira/browse/KAFKA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525420#comment-14525420
]
Ashish K Singh commented on KAFKA-313:
--
[~nehanarkhede] and [~gwenshap], pinging again
Thanks @Jay for suggesting changes to batch.size and linger.ms. I tried
them out. It appears one can do better than the default batch.size for
this synchronous batch mode with flush().
These new measurements are giving more "rational" numbers which with I can
reason and infer some thumb rules (fo
[
https://issues.apache.org/jira/browse/KAFKA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525408#comment-14525408
]
Jiangjie Qin commented on KAFKA-2142:
-
Updated reviewboard https://reviews.apache.org/
[
https://issues.apache.org/jira/browse/KAFKA-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiangjie Qin updated KAFKA-2142:
Attachment: KAFKA-2142_2015-05-02_11:59:39.patch
> Follow-up patch for KAFKA-2138 Refactor the drain
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33552/
---
(Updated May 2, 2015, 6:59 p.m.)
Review request for kafka.
Bugs: KAFKA-2142
17 matches
Mail list logo
