server: replica.fetch.max.bytes should be >= message.max.bytes. Otherwise,
the follower will get stuck when replicating data from the leader.
Thanks,
Jun
On Wed, Jul 31, 2013 at 10:10 AM, Sam Meder wrote:
> I also noticed that there are two properties related to messages size on
> the server:
If you look at ConsumerIterator, we will throw MessageSizeTooLargeException
to the caller if the fetch size is too small.
Thanks,
Jun
On Wed, Jul 31, 2013 at 8:25 AM, Sam Meder wrote:
> We're expecting to occasionally have to deal with pretty large messages
> being sent to Kafka. We will of co
+1 for 296
Thanks,
Jun
On Wed, Jul 31, 2013 at 1:34 PM, Jay Kreps wrote:
> Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or less
> a tie between two logos:
>
> https://issues.apache.org/jira/secure/attachment/12593545/296.png
> https://issues.apache.org/jira/secure/attach
[
https://issues.apache.org/jira/browse/KAFKA-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-992:
Attachment: KAFKA-992.v1.patch
> Double Check on Broker Registration to Avoid False NodeExist Ex
[
https://issues.apache.org/jira/browse/KAFKA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-649:
Attachment: KAFKA-649.v5.patch
One left-bracket mistyping fix.
> Cleanup log4j logg
[
https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725974#comment-13725974
]
Dan F commented on KAFKA-881:
-
I am not necessarily opposed, but I don't understand what "cross
+1 for 298
On Thu, Aug 1, 2013 at 2:04 AM, Jay Kreps wrote:
> Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or less
> a tie between two logos:
>
> https://issues.apache.org/jira/secure/attachment/12593545/296.png
> https://issues.apache.org/jira/secure/attachment/12593547/2
+1 on 296, after looking at the website mockup.
Thanks,
Neha
On Wed, Jul 31, 2013 at 3:09 PM, Benjamin Black wrote:
> +1 on 296
>
> Not even close
> On Jul 31, 2013 1:34 PM, "Jay Kreps" wrote:
>
> > Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or
> less
> > a tie between
+1 on 296
Not even close
On Jul 31, 2013 1:34 PM, "Jay Kreps" wrote:
> Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or less
> a tie between two logos:
>
> https://issues.apache.org/jira/secure/attachment/12593545/296.png
> https://issues.apache.org/jira/secure/attachment/12
+1 296
- Prashanth
On Wed, Jul 31, 2013 at 4:36 PM, Joe Stein wrote:
> +1 298
>
> // Joestein
>
> On Wed, Jul 31, 2013 at 4:34 PM, Jay Kreps wrote:
>
> > +1 296
> >
> > -Jay
> >
> >
> > On Wed, Jul 31, 2013 at 1:34 PM, Jay Kreps wrote:
> >
> > > Okay folks we did a survey on the JIRA (KAFKA-
+1 298
// Joestein
On Wed, Jul 31, 2013 at 4:34 PM, Jay Kreps wrote:
> +1 296
>
> -Jay
>
>
> On Wed, Jul 31, 2013 at 1:34 PM, Jay Kreps wrote:
>
> > Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or
> less
> > a tie between two logos:
> >
> > https://issues.apache.org/jira/
Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or less
a tie between two logos:
https://issues.apache.org/jira/secure/attachment/12593545/296.png
https://issues.apache.org/jira/secure/attachment/12593547/298.jpeg
Personally I like both, but we need to pick one. So let's quickl
+1 296
-Jay
On Wed, Jul 31, 2013 at 1:34 PM, Jay Kreps wrote:
> Okay folks we did a survey on the JIRA (KAFKA-982) and it was more or less
> a tie between two logos:
>
> https://issues.apache.org/jira/secure/attachment/12593545/296.png
> https://issues.apache.org/jira/secure/attachment/1259354
[
https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-982:
Attachment: 298-screenshot.png
> Logo for Kafka
> --
>
> Key: KAFKA-982
>
[
https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-982:
Attachment: 296-screenshot.png
> Logo for Kafka
> --
>
> Key: KAFKA-982
>
[
https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-982:
Attachment: (was: 290-screenshot.png)
> Logo for Kafka
> --
>
> Key: KAF
[
https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-982:
Attachment: (was: 285-screenshot.png)
> Logo for Kafka
> --
>
> Key: KAF
[
https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-982:
Attachment: 285-screenshot.png
> Logo for Kafka
> --
>
> Key: KAFKA-982
>
[
https://issues.apache.org/jira/browse/KAFKA-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-982:
Attachment: 290-screenshot.png
> Logo for Kafka
> --
>
> Key: KAFKA-982
>
[
https://issues.apache.org/jira/browse/KAFKA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-649:
Attachment: KAFKA-649.v4.patch
> Cleanup log4j logging
> -
>
>
[
https://issues.apache.org/jira/browse/KAFKA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725485#comment-13725485
]
Guozhang Wang commented on KAFKA-649:
-
Thanks for the comments Jun.
30,31,32,33. Done.
[
https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-955:
Attachment: KAFKA-955.v2.patch
> After a leader change, messages sent with ack=0 are lost
>
[
https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725452#comment-13725452
]
Guozhang Wang commented on KAFKA-955:
-
Thanks for the comments Jun.
1,2,3. Done.
I also noticed that there are two properties related to messages size on the
server: replica.fetch.max.bytes and message.max.bytes. What happens when
replica.fetch.max.bytes is lower than message.max.bytes? Should there even be
two properties?
/Sam
On Jul 31, 2013, at 5:25 PM, Sam Meder wrote
[
https://issues.apache.org/jira/browse/KAFKA-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725425#comment-13725425
]
Jun Rao commented on KAFKA-984:
---
Thanks for patch v2. Some comments:
20. It seems that we sh
[
https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725399#comment-13725399
]
Jun Rao commented on KAFKA-881:
---
Thanks for the patch. Would it be simpler to just test that
[
https://issues.apache.org/jira/browse/KAFKA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725381#comment-13725381
]
Jun Rao commented on KAFKA-967:
---
Thanks for the patch. We probably should only set the key if
[
https://issues.apache.org/jira/browse/KAFKA-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-991:
Description:
Currently the queue.size in hadoop producer is 10MB. This means that the
KafkaRecordWr
[
https://issues.apache.org/jira/browse/KAFKA-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725351#comment-13725351
]
Jun Rao commented on KAFKA-649:
---
Thanks for patch v3.
30. KafkaApi.readMessageSets(): We don
We're expecting to occasionally have to deal with pretty large messages being
sent to Kafka. We will of course set the fetch size appropriately high, but are
concerned about the behavior when the message exceeds the fetch size. As far as
I can tell the current behavior when a message that is too
[
https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725324#comment-13725324
]
Jun Rao commented on KAFKA-955:
---
Thanks for the patch. Some comments:
1. SocketServer: We sh
Hi Jay,
I can probably look at this either this week or on the weekend.
On Mon, Jul 29, 2013 at 7:37 PM, Jay Kreps wrote:
> It would be great if someone could take a look at this:
> https://issues.apache.org/jira/browse/KAFKA-615
>
> -Jay
>
Evan Huus created KAFKA-993:
---
Summary: Offset Management API is either broken or mis-documented
Key: KAFKA-993
URL: https://issues.apache.org/jira/browse/KAFKA-993
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evan Huus updated KAFKA-993:
Description:
I am in the process of building a set of Go client bindings for the new 0.8
protocol
(https:/
34 matches
Mail list logo