Ben: your solutions seems to focus on partition-wide CAS. Have you
considered per-key CAS? That would make the feature more useful in my
opinion, as you'd greatly reduce the contention.
On Fri, Jun 12, 2015 at 6:54 AM Gwen Shapira wrote:
> Hi Ben,
>
> Thanks for creating the ticket. Having check
Gwen: Right now I'm just looking for feedback -- but yes, if folks are
interested, I do plan to do that implementation work.
Daniel: Yes, that's exactly right. I haven't thought much about
per-key... it does sound useful, but the implementation seems a bit
more involved. Want to add it to the tick
Hi,
I am running a standalone kafka cluster and writing some sample messages
using the java client API KafkaProducer. The RecordMetaData I am receiving
from server(KafkaProducer send method return value) contains offset -1. Is
offset information available only at consumer end and not in producer s
Hi,
What is the value set for acks config property?
If acks=0 then the producer will not wait for any acknowledgment from the
server and
offset given back for each record will always be set to -1.
Manikumar
On Fri, Jun 12, 2015 at 7:17 PM, Gokulakannan M (Engineering - Data
Platform) wrote:
>
Hi,
I was trying to give burrow a try and got a ZK error "invalid ACL
specified". Any suggestions on what's going wrong?
1434044348908673512 [Critical] Cannot get ZK notifier lock: zk: invalid ACL
specified
Here's my config:
[general]
logdir=log
logconfig=logging.cfg
pidfile=burrow.pid
c
I have been thinking a little about this. I don't think CAS actually
requires any particular broker support. Rather the two writers just write
messages with some deterministic check-and-set criteria and all the
replicas read from the log and check this criteria before applying the
write. This mecha
The invalid ACL error is an error that is passed back from Zookeeper. What
version of Zookeeper are you using, and have you set up ACLs within it? I'm
not able to see this on our ZK (3.4.6 with no ACLs).
-Todd
On Fri, Jun 12, 2015 at 9:34 AM, Roger Hoover
wrote:
> Hi,
>
> I was trying to give b
Pleased to announce that the kafka-python community released v0.9.4 to pypi
last night. This release is focused on stability enhancements, cleanups,
and bugfixes. We had a record 13 different contributors w/ merged PRs, and
even more folks from the community supporting w/ issues, comments, and
disc
Thanks, Todd. I'm also using ZK 3.4.6 with no ACLs. I'm surprised and
currently stumped by this error.
On Fri, Jun 12, 2015 at 9:49 AM, Todd Palino wrote:
> The invalid ACL error is an error that is passed back from Zookeeper. What
> version of Zookeeper are you using, and have you set up ACLs
Can you open an issue on the github page please, and we can investigate
further there?
-Todd
On Fri, Jun 12, 2015 at 10:22 AM, Roger Hoover
wrote:
> Thanks, Todd. I'm also using ZK 3.4.6 with no ACLs. I'm surprised and
> currently stumped by this error.
>
> On Fri, Jun 12, 2015 at 9:49 AM, To
Hi, I'm new to Kafka and having trouble with log compaction.
I'm attempting to set up topics that will aggressively compact, but so far
I'm having trouble getting complete compaction at all. The topic is
configured like so:
Topic:beer_archive PartitionCount:20 ReplicationFactor:1
Configs:min.cle
Will do. Thanks
Sent from my iPhone
> On Jun 12, 2015, at 10:43 AM, Todd Palino wrote:
>
> Can you open an issue on the github page please, and we can investigate
> further there?
>
> -Todd
>
> On Fri, Jun 12, 2015 at 10:22 AM, Roger Hoover
> wrote:
>
>> Thanks, Todd. I'm also using ZK 3.
Issue is here: https://github.com/linkedin/Burrow/issues/3
On Fri, Jun 12, 2015 at 11:34 AM, Roger Hoover
wrote:
> Will do. Thanks
>
> Sent from my iPhone
>
> > On Jun 12, 2015, at 10:43 AM, Todd Palino wrote:
> >
> > Can you open an issue on the github page please, and we can investigate
> >
We have Kafka clusters in three datacenters with Mirror Maker replicating
across three data centers. We are monitoring JMX metrics of our clusters.
I have question regarding FetchRequestPurgatory
(kafka.server:type=FetchRequestPurgatory,name=PurgatorySize), description on
Wiki says "Number of re
Thank you Adam, that helps me know what to look for.
On Thu, Jun 11, 2015 at 12:49 PM, Adam Dubiel wrote:
> I just tried it out on my 0.8.2 cluster and it worked just fine - the ISR
> grew, replica factor changed and data was physically moved to new brokers.
> Was there not output/no logs? I see
So I just realized that when creating multiple partitions for a topic, it
is the responsibility of the producer and the consumer to decide where to
put data.
So if I am a consumer, how do I know what partition to read data from?
What if the producer only put data in 1 partition out of 50.
And so
EXCELLENT WORK. Thank you!
On Wed, Jun 10, 2015 at 11:19 AM, Keith Bourgoin
wrote:
> I would guess within a week or two, but it's hard to say for sure. Emmett
> Butler, the other main contributor, has been hard at work on it when he has
> the time.
>
> On Wed, Jun 10, 2015 at 12:18 PM Vijay Pat
Thank you for the replies. I was able to lower the replication factor by
using the kafka-reassign-partitions.sh tool. What initially threw me off
was kafka-reassign-partitions.sh --generate was giving this error:
Partitions reassignment failed due to replication factor: 3 larger than
available b
The producer can use a key to determine which partition to put data in. For
example we use a partitioning scheme based on the header of the message so that
all messages with a specific header go to a specific partition. The consumer
can also include the same logic to process those messages.
>
Thanks. I thought I was setting acks as 1 but was setting as 0 due to a bug
in my code. Works fine now.
On Fri, Jun 12, 2015 at 7:17 PM, Gokulakannan M (Engineering - Data
Platform)
>
> Hi,
>
> What is the value set for acks config property?
> If acks=0 then the producer will not wait for any ack
20 matches
Mail list logo
