es.
>
> Hope this answers your question.
>
> Thanks,
> Apurva
>
> On Tue, Dec 6, 2016 at 3:22 PM, Ben Kirwin wrote:
>
> > Thanks for this! I'm looking forward to going through the full proposal
> in
> > detail soon; a few early questions:
>
Thanks for this! I'm looking forward to going through the full proposal in
detail soon; a few early questions:
First: what happens when a consumer rebalances in the middle of a
transaction? The full documentation suggests that such a transaction ought
to be rejected:
> [...] if a rebalance has ha
[
https://issues.apache.org/jira/browse/KAFKA-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313267#comment-15313267
]
Ben Kirwin commented on KAFKA-3335:
---
Excellent -- thanks for following up on
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313258#comment-15313258
]
Ben Kirwin commented on KAFKA-2260:
---
Hi! I haven't had time to push on this
Ben Kirwin created KAFKA-3335:
-
Summary: Kafka Connect hangs in shutdown hook
Key: KAFKA-3335
URL: https://issues.apache.org/jira/browse/KAFKA-3335
Project: Kafka
Issue Type: Bug
t;>> daniel.schierb...@gmail.com> wrote:
> >>>
> >>>> Jiangjie: I think giving users the possibility of defining a custom
> >>> policy
> >>>> for handling rejections is a good idea. For instance, this will allow
> >>> Kafka
&
hould just move on.
>
> It looks to me even a transient multiple producer scenario will cause issue
> because user need to think about what should do if a request got rejected
> and the answer varies for different use cases.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
> O
ll be considered
>> as
>> > atomic. The only possibility of a batch got rejected should be it is
>> > already appended. So the producer should just move on.
>> >
>> > It looks to me even a transient multiple producer scenario will cause
>> issue
>>
; We plan to fill the relative offset to the offset field in the batch sent
>> > by producer to avoid broker side re-compression. The message offset would
>> > become batch base offset + relative offset. I guess maybe the expected
>> > offset in KIP-27 can be only se
e
> commit log, the zombie writer can publish new messages to the log after the
> new writer takes over, but before it publishes any message. We probably
> need to outline how this case can be handled properly.
>
> Thanks,
>
> Jun
>
> On Mon, Jul 20, 2015 at 12:05 PM, B
@yahoo.com.invalid> wrote:
>> >
>> > > I like this feature, it reminds me of conditional updates in zookeeper.
>> > > I'm not sure if it'd be best to have some mechanism for fencing rather
>> > than
>> > > a conditional write like you'
some cases where the offsets are
already available -- like the commit-log-for-KV-store example -- but
in general, being able to get the offsets from the producer interface
does sound convenient.
> We plan to have a KIP discussion meeting tomorrow at 11am PST. Perhaps you
> can describe this KI
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632537#comment-14632537
]
Ben Kirwin commented on KAFKA-2260:
---
Ah, clever! Thanks for sharing this -- I'
le of the drawbacks of the per-key approach mentioned
at the bottom of the KIP.
On Fri, Jul 17, 2015 at 6:47 PM, Ben Kirwin wrote:
> Hi all,
>
> So, perhaps it's worth adding a couple specific examples of where this
> feature is useful, to make this a bit more concrete:
>
>
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632120#comment-14632120
]
Ben Kirwin commented on KAFKA-2260:
---
Interesting -- the idea is that we track the
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632113#comment-14632113
]
Ben Kirwin commented on KAFKA-2260:
---
Ah, sorry! Let me try again.
Suppose you try
7;m not sure if it'd be best to have some mechanism for fencing rather
>> than
>> > a conditional write like you're proposing. The reason I'm saying this is
>> > that the conditional write applies to requests individually, while it
>> > sounds lik
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630870#comment-14630870
]
Ben Kirwin commented on KAFKA-2260:
---
Opened a KIP for this here:
h
Hi there,
I just added a KIP for a 'conditional publish' operation: a simple
CAS-like mechanism for the Kafka producer. The wiki page is here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-27+-+Conditional+Publish
And there's some previous discussion on the ticket and the users list:
ht
Great -- thank you!
On Wed, Jul 15, 2015 at 9:13 PM, Jun Rao wrote:
> Done.
>
> Thanks,
>
> Jun
>
> On Wed, Jul 15, 2015 at 5:22 PM, Ben Kirwin wrote:
>
>> Hi there,
>>
>> I'm interested in posting a KIP (for this ticket:
>> https://issues.a
Hi there,
I'm interested in posting a KIP (for this ticket:
https://issues.apache.org/jira/browse/KAFKA-2260) but I don't seem to
have the right permissions to create the wiki page.
Can anyone here set that up? (Username is `bkirwi`.)
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627484#comment-14627484
]
Ben Kirwin commented on KAFKA-2260:
---
Will do; thanks!
> Allow specifying e
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627460#comment-14627460
]
Ben Kirwin commented on KAFKA-2260:
---
Hi [~ewencp] -- thanks for the interest! I&
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Kirwin updated KAFKA-2260:
--
Attachment: expected-offsets.patch
> Allow specifying expected offset on prod
[
https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Kirwin updated KAFKA-2260:
--
Status: Patch Available (was: Open)
Worked up a draft of this over the weekend, implementing the
&quo
Ben Kirwin created KAFKA-2260:
-
Summary: Allow specifying expected offset on produce
Key: KAFKA-2260
URL: https://issues.apache.org/jira/browse/KAFKA-2260
Project: Kafka
Issue Type: Improvement
26 matches
Mail list logo
