Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

ort for rolling back checkpoints, e.g., > when a transaction is aborted. We need to be aware of that and ideally > anticipate a bit those needs in the KIP. > > > > Thanks > > Eno > > > > > >> On 1 Feb 2017, at 10:18, Damian Guy wrote: > >> &g

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

r to just use an parameter that is "number-or-commit > intervals". > > > -Matthias > > > On 2/1/17 7:29 AM, Damian Guy wrote: > > Thanks for the comments Eno. > > As for exactly once, i don't believe this matters as we are just > restoring > > the cha

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

gt; Thanks Damian. > > One more question: "Checkpointing is disabled if the checkpoint interval > is set to a value <=0." > > > Does it make sense to disable check pointing? What's the tradeoff here? > > > -Matthias > > > On 2/2/17 1:51 AM, Damian

Re: [DISCUSS] KIP-118: Drop Support for Java 7 in Kafka 0.11

Thanks Ismael. Makes sense to me. On Fri, 3 Feb 2017 at 10:39 Ismael Juma wrote: > Hi all, > > I have posted a KIP for dropping support for Java 7 in Kafka 0.11: > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-118%3A+Drop+Support+for+Java+7+in+Kafka+0.11 > > Most people were supporti

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

nvinced otherwise. > > Thanks > Eno > > > > > On 3 Feb 2017, at 10:03, Damian Guy wrote: > > > > Hi Matthias, > > > > It possibly doesn't make sense to disable it, but then i'm sure someone > > will come up with a reason they don't

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Hi Matthias, Thanks for the KIP. Should TopologyBuilder#build() and KStreamBuilder#build accept a StreamsConfig as an argument? Should we add a KStreamBuilder#topologyBuilder() for cases where people want to mix and match DSL & PAPI? Or do you think we already provide enough support for that via

Re: KIP-121 [Discuss]: Add KStream peek method

Hi Steven, Thanks for the KIP. I think this is a worthy addition to the API. Thanks, Damian On Tue, 7 Feb 2017 at 09:30 Eno Thereska wrote: > Hi, > > I like the proposal, thank you. I have found it frustrating myself not to > be able to understand simple things, like how many records have been

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

ge to guard users to accidentally switch it off. > > -Matthias > > > On 2/3/17 2:03 AM, Damian Guy wrote: > > Hi Matthias, > > > > It possibly doesn't make sense to disable it, but then i'm sure someone > > will come up with a reason they don't want it

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

tore]: 1000/33476/298721.4720994145/30.738439479029754 Streams Performance [records/latency/rec-sec/MB-sec source+store]: 1000/33196/301241.1133871551/30.99771056753826 On Wed, 8 Feb 2017 at 09:02 Damian Guy wrote: > Matthias, > > Fair point. I'll update it the KIP. > Thanks

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

this > value? > > Right now, in the KIP and in this discussion, "5 mins" looks like a magic > number to me. :-) > > -Michael > > > > On Thu, Feb 9, 2017 at 11:03 AM, Damian Guy wrote: > > > I've ran the SimpleBenchmark with checkpoint on and o

Re: KIP-121 [VOTE]: Add KStream peek method

+1 On Thu, 9 Feb 2017 at 10:26 Michael Noll wrote: > +1 (non-binding) > > And thanks again for suggesting and driving this, Steven! :-) > > Best, > Michael > > > > > On Thu, Feb 9, 2017 at 6:06 AM, Matthias J. Sax > wrote: > > > +1 > > > > On 2/8/17 4:51 PM, Gwen Shapira wrote: > > > +1 (bindin

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 On Thu, 9 Feb 2017 at 15:41 Bill Bejeck wrote: > +1 > > On Thu, Feb 9, 2017 at 10:31 AM, Ismael Juma wrote: > > > Hi everyone, > > > > Since everyone in the discuss thread was in favour (10 people > responded), I > > would like to initiate the voting process for KIP-118: Drop Support for > >

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

> > > > > Guozhang > > > > > > > > > > > > On Thu, Feb 9, 2017 at 11:02 AM, Guozhang Wang > > wrote: > > > > > >> A quick question re: `We will add the above config parameter to > > >> *StreamsConfig*. During

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

config variable and just > use the existing commit interval. > > Less tuning knobs. > > Eno > > > On 10 Feb 2017, at 09:27, Damian Guy wrote: > > > > Gouzhang, > > > > You've confused me. The failure scenarios you have described are the same >

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

t;> Say we don't need the checkpointing and would like to gain the lil bit > >> of performance improvement by turning it off. > >>> The trade off is between giving people control knobs vs complicating > the > >> complete set of knobs. > >>> > >&

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

int file for this > case. And even if there is no switch and we enable EoS all the time, we > can get rid of the checkpoint file overall (making the parameter obsolete). > > IMHO, if the config parameter is not really useful, we should not have it. > > > -Matthias > > >

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

> And about printing the topology for debuggability: I agrees this is a > > potential drawback, and I'd suggest maintain some functionality to build > a > > "dry topology" as Mathieu suggested; the difficulty is that, internally > we > > need a different "copy" of the topology for each thread so th

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

, since it won't change any > > public APIs and we can still add this config in the future if we do > observe > > some users reporting it has huge perf impacts. > > > > > > > > Guozhang > > > > On Fri, Feb 10, 2017 at 12:20 PM, Damian Guy &

KTable.count(...)

Hi, I'm slightly confused by KTable.count(..). The javadoc says: Count number of records of this stream by the selected key into a new instance of {@link KTable}. So.. if i send 5 records with the same key to the input topic, as per below final KafkaProducer producer = new KafkaProducer<>(prod

Re: KTable.count(...)

is behavior: > > > http://docs.confluent.io/2.1.0-alpha1/streams/concepts.html#ktable-changelog-stream > > http://docs.confluent.io/2.1.0-alpha1/streams/quickstart.html#inspect-the-output-data > > Maybe we can update the Javadoc to make this behavior more explicit? > > Thanks, > L

Re: Pluggable Log Compaction Policy

Hi Bill, Have you looked at: http://kafka.apache.org/documentation.html#compaction It supports deletes so if you keyed by transaction_id you could, in theory, delete them. Cheers, Damian On 20 January 2016 at 18:35, Bill Warshaw wrote: > Hello, > > I'm working on a team that is starting to us

New Consumer Poll bug?

I've been having some issues with the New Consumer. I'm aware there is a bug that has been fixed for 0.9.0.1, but is this the same thing? I'm using manual partition assignment due to latency issues making it near impossible to work with the group management features. So, my consumer was going alon

Re: New Consumer Poll bug?

Forgot to reply-all… > On 13 Feb 2016, at 14:49, Damian Guy wrote: > > Hi Ismael, > > In this case it wasn’t a rebalance as I was using consumer.assign(..) I’ll > give it a try with the 0.9.0.1 client to see if i can reproduce. > I’ve tried the 0.9.0.1 client with c

Re: New Consumer Poll bug?

I tried the 0.9.0.1 client and was able to successfully consume the partition without any problems. Thanks, Damian On 13 February 2016 at 14:49, Damian Guy wrote: > Forgot to reply-all… > > > On 13 Feb 2016, at 14:49, Damian Guy wrote: > > Hi Ismael, > > In this case

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

t; We've not considered this and I'm not sure we want to as part of this KIP. Thanks, Damian > > > On Mon, Aug 8, 2016 at 12:41 AM, Damian Guy wrote: > > > Hi, > > > > We have created KIP 71: Enable log compaction and deletion to co-exist` > > > > htt

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

al. It makes sense to use time-based deletion >> retention and compaction together, as you mentioned in the KStream. >> >> Is there a use case where we want to combine size-based deletion retention >> and compaction together? >> >> Jun >> >> On Thu, Aug 11, 20

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

Hi Jason, It is still not clear to me how adding a callback would help. You could remove the periodic task, but you would still need to scan the entire cache to remove the expired offsets. Am i missing something? Thanks, Damian On 11 August 2016 at 10:00, Damian Guy wrote: > Hi Ja

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

finite, I think > we can just leave the KIP as it is. > > Thanks, > > Jun > > On Fri, Aug 12, 2016 at 12:10 AM, Damian Guy wrote: > > > Hi, > > > > The only concrete example i can think of is a case for limiting disk > usage. > > Say, i

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

And I suppose a consumer would do a seek to the start of the > window (as soon as KIP-33 is available) and consume from there in order to > read the current state? > > Thanks, > Jason > > On Fri, Aug 12, 2016 at 8:48 AM, Damian Guy wrote: > > > Thanks Jun > >

[VOTE] KIP:71 Enable log compaction and deletion to co-exist

I would like to initiate the voting process for KIP-71 ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-71%3A+Enable+log+compaction+and+deletion+to+co-exist ). This change will add a new cleanup.policy, compact_and_delete, that when enabled will run both compaction and deletion. Thanks, Da

Re: [VOTE] KIP:71 Enable log compaction and deletion to co-exist

) > > > > On Mon, Aug 15, 2016 at 7:34 PM, Sriram Subramanian > > wrote: > > > > > +1 (binding) > > > > > > On Mon, Aug 15, 2016 at 10:27 AM, Ismael Juma > wrote: > > > > > > > Thanks for the KIP, +1 (binding)

Re: [VOTE] KIP:71 Enable log compaction and deletion to co-exist

Oops, it appears I was a bit trigger happy on closing the vote. Sorry, it will remain open for the requisite 72 hours. Sorry again. Damian On Mon, 15 Aug 2016 at 19:56, Damian Guy wrote: > And that concludes the vote. KIP-71 has been accepted. > Thanks everyone. > > Damian > &

Re: [VOTE] KIP:71 Enable log compaction and deletion to co-exist

ks, > > -Ewen > > > > On Mon, Aug 15, 2016 at 4:26 PM, Jun Rao wrote: > > > > > Thanks for the proposal. +1 > > > > > > Jun > > > > > > On Mon, Aug 15, 2016 at 6:20 AM, Damian Guy > > wrote: > > > > >

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

edence. > > Anyway, it is just a thought - it may end up being very confusing for > > users. > > > > @Jason - I agree this could be used to handle offset expiration as well. > We > > can discuss that separately though; and if we do that we would want to > also > >

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

ies "compact,delete" as opposed to > > > > "compact_and_delete" or "x_and_y_and_z" or "y_and_z" if we ever come > up > > > > with more policies. The order could potentially indicate precedence. > > > > Anyway, it is just a

Re: [VOTE] KIP-63: Unify store and downstream caching in streams

+1 On Thu, 25 Aug 2016 at 11:57 Eno Thereska wrote: > Hi folks, > > We'd like to start the vote for KIP-63. At this point the Wiki addresses > all previous questions and we believe the PoC is feature-complete. > > Thanks > Eno >

Re: [DISCUSS] KIP-76: Enable getting password from executable rather than passing as plaintext in config files

I'm in agreement with Gwen. An API would be a better solution. Running executables from Kafka is dangerous. On Sat, 27 Aug 2016 at 12:02, Ismael Juma wrote: > Hi Matthias, > > Improve Kafka Streams Join Semantics is not mentioned on the KIP page and > that is probably the source of confusion: > >

Re: [VOTE] KIP-77: Improve Kafka Streams Join Semantics

+1 On Mon, 29 Aug 2016 at 18:07 Eno Thereska wrote: > +1 (non-binding) > > > On 29 Aug 2016, at 12:22, Bill Bejeck wrote: > > > > +1 > > > > On Mon, Aug 29, 2016 at 5:50 AM, Matthias J. Sax > > wrote: > > > >> I’d like to initiate the voting process for KIP-77: > >> > >> https://cwiki.apache.o

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

Hi Matthias, Thanks for bringing the conversation across to the thread. I think a main limitation would be, that you cannot mix the 4 patterns > within a single application anymore (iff you use a "caches state"). If > you have processor with a "cached state" this disables direct usage of > contex

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

t;cached state" would be used, it would not work any more. > > > -Matthias > > On 09/04/2016 05:58 PM, Damian Guy wrote: > > Hi Matthias, > > > > Thanks for bringing the conversation across to the thread. > > > > I think a main limitation would be, that you can

Re: Queryable state client read guarantees

Hi Mikael, > > Failed to read key hello, org.mkhq.kafka.Topology$StoreUnavailable > > Failed to read key hello, org.mkhq.kafka.Topology$KeyNotFound > > hello -> 10 > > The case where you get KeyNotFound looks like a bug to me. This shouldn't happen. I can see why it might happen and we will creat

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

t;> think, caching is a cool feature, I want to use it, you would simply > > >>> want to enable caching (without breaking your code). > > >>> > > >>> Processor code should always work independently if caching is enabled > > or > > >>&g

Re: Queryable state client read guarantees

Hi Mikael, A fix for KAFKA-4123 (the issue you found with receiving null values) has now been committed to trunk. I've tried it with your github repo and it appears to be working. You will have to make a small change to your code as we now throw I

Re: Queryable state client read guarantees

ence: > > 18 -> 2 > 19 -> Not found > 20 -> Not found > 21 -> 2 > > From the client perspective, I think this violates the guarantee of always > reading the latest value. > > Am I making the wrong assumptions or is there some way to detect that

Re: [kafka-clients] [VOTE] 0.10.1.0 RC2

Hi Jason, Really sorry, but we are going to need to cut another RC. There was a report on the user list w.r.t the NamedCache (in KafkaStreams) throwing a NullPointerException. I've looked into it and it is definitely a bug that needs to be fixed. jira is https://issues.apache.org/jira/browse/KAFK

Re: KStreams / add support for sink processor with dynamic topics

Hi Florian, Do you know the set of subtypes in advance? I.e, could you use: KStream[] branches = stream.branch(predicates); to split the stream based on the subtypes? Thanks, Damian On Tue, 18 Oct 2016 at 00:43 Matthias J. Sax wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > H

Re: [ANNOUNCE] New committer: Rajini Sivaram

Congrats On Tue, 25 Apr 2017 at 09:57, Mickael Maison wrote: > Congratulation Rajini ! > Great news > > On Tue, Apr 25, 2017 at 8:54 AM, Edoardo Comar wrote: > > Congratulations Rajini !!! > > Well deserved > > -- > > Edoardo Comar > > IBM MessageH

Re: Re: Time synchronization between streams

reams will receive VT1. > > > > I.e. state stores actions of Kafka Streams will be like this: > > > > join_left_side_store.put ( K1-W1, V1 ) > > join_left_side_store.put ( K1-W1, V2 ) > > join_right_side_store.put ( K1-W1, VT1 ) > > join_right_side_stor

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Hi Kyle, Thanks for the KIP. I apologize that i haven't had the chance to look at the KIP yet, but will schedule some time to look into it tomorrow. For the implementation, can you raise a PR against kafka trunk and mark it as WIP? It will be easier to review what you have done. Thanks, Damian O

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

method I pass null to the KGroupedStream#repartitionIfRequired method. > I > > > can't supply the store name because if more than one grouped stream > > > repartitions an error is thrown. Is there some name that someone can > > > recommend or should I leave the n

Re: [DISCUSS] KIP-138: Change punctuate semantics

Thanks Michael - LGTM On Fri, 5 May 2017 at 12:04 Michal Borowiecki wrote: > I shall move all alternatives other than the main proposal into the > Rejected Alternatives section and if I hear any objections, I'll move those > back up and we'll discuss further. > > Done. > > > Still looking forwa

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Thanks for the KIP. I'm not convinced on the `RichFunction` approach. Do we really want to give every DSL method access to the `ProcessorContext` ? It has a bunch of methods on it that seem in-appropriate for some of the DSL methods, i.e, `register`, `getStateStore`, `forward`, `schedule` etc. It

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

you question the `RichFunction` approach in > general? Or if you suggest to either extend the scope of this KIP to > include this---or maybe better, do another KIP for it and delay this KIP > until the other one is done? > > > -Matthias > > On 5/15/17 2:35 AM, Damian Guy wrote: &

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

; https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0 > < > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0 > >) > > so people are busier than usual. Stay tuned. > > > > Eno > > > On 15 May 2017, at 13:25, Kyle Winkelm

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

t > is created from a KGroupedStream we should keep a similar name format. > > On May 16, 2017 9:23 AM, "Damian Guy" wrote: > > Hi Kyle, > > Can you put the code examples etc in {code} blocks to make it easier to > read? > > I think this is probably a pretty co

Re: Reg: [VOTE] KIP 157 - Add consumer config options to streams reset tool

+1 On Wed, 17 May 2017 at 05:40 Ewen Cheslack-Postava wrote: > +1 (binding) > > I mentioned this in the PR that triggered this: > > > KIP is accurate, though this is one of those things that we should > probably get a KIP for a standard set of config options across all tools so > additions like

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

; > > >>> > > >>> Instead of overriding the *init(ProcessorContext p)* and* close()* > > >> methods > > >>> in every Rich function with empty body like: > > >>> > > >>> @Override > > >>> void init(Proce

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

+1 to what Xavier said On Wed, 24 May 2017 at 06:45 Xavier Léauté wrote: > I don't think we should wait for entries from each stream, since that might > limit the usefulness of the cogroup operator. There are instances where it > can be useful to compute something based on data from one or more

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

Also, +1 for the KIP On Wed, 24 May 2017 at 08:57 Damian Guy wrote: > +1 to what Xavier said > > On Wed, 24 May 2017 at 06:45 Xavier Léauté wrote: > >> I don't think we should wait for entries from each stream, since that >> might >> limit the usefulness

Re: GlobalKTable limitations

We did originally think of allowing `filter`, `map` etc on a GlobalKTable, though it would have been slightly different to what you are suggesting, i.e., we'd materialize the topic as a Store and then provide views on top of that. They'd also be global, but not materialized as physical state stores

Re: KIP-162: Enable topic deletion by default

+1 Also agree with what Ismael said. On Fri, 26 May 2017 at 15:26 Ismael Juma wrote: > Thanks for the KIP, sounds good to me. One comment: not sure we need to add > the config to server.properties. Do we expect people to change this > default? > > On Fri, May 26, 2017 at 3:03 PM, Gwen Shapira w

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Eno, Under what circumstances would you get a deserialization exception from the state store? I can only think of the case where someone has provided a bad deserializer to a method that creates a state store. In which case it would be a user error and probably should just abort? Thanks, Damian O

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

ge one to later. > > Eno > > > On 26 May 2017, at 16:59, Damian Guy wrote: > > > > Eno, > > > > Under what circumstances would you get a deserialization exception from > the > > state store? I can only think of the case where someone has provided a

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

mbined to compute > >> > >> aggregate > >> > >> > statistics (e.g. impression statistics, and click-through rates), > >> > since > >> > >> > most of the attributes of interest are only present the auction > >> > stream.

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

I agree with what Matthias has said w.r.t failing fast. There are plenty of times when you don't want to fail-fast and must attempt to make progress. The dead-letter queue is exactly for these circumstances. Of course if every record is failing, then you probably do want to give up. On Fri, 2 Jun

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

addition to the kafka > toolkit that I can think of. It just doesn't fit the architecture > of having clients falling behind is a valid option. > > Further. I mentioned already the only bad pill ive seen so far is crc > errors. any plans for those? > > Best Jan > > >

Re: [DISCUSS] KIP-147: Add missing type parameters to StateStoreSupplier factories and KGroupedStream/Table methods

Hi Michal, Thanks for the KIP - is there a way we can do this without having to introduce the new Typed.. Interfaces, overloaded methods etc? Is it possible that we just need to provide a couple of new methods on PersistentKeyValueFactory for windowed and sessionWindowed to return interfaces like

Re: [DISCUSS] KIP-147: Add missing type parameters to StateStoreSupplier factories and KGroupedStream/Table methods

Hmm, i guess this won't work due to adding the additional to the StateStoreSupplier params on reduce, count, aggregate etc. On Sat, 3 Jun 2017 at 09:06 Damian Guy wrote: > Hi Michal, > > Thanks for the KIP - is there a way we can do this without having to > introduce the new T

Re: Sink Processor definition

Hi Michal, In this case Sink Processor is really referring to a SinkNode that can only produce to a kafka topic. Maybe the terminology is incorrect as strictly speaking a processor that writes data to anything could be considered a Sink Processor. On Sat, 3 Jun 2017 at 09:23 Michal Borowiecki wr

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

I'm largely in agreement with what Guozhang has suggested, i.e., StateRestoreContext shouldn't have any setters on it and also need to have the end offset available such that people can use it derive progress. Slightly different, maybe the StateRestoreContext interface could be: long beginOffset()

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

experience for our users. > > > > Since we are getting late into the release cycle, it may be a bit too > late > > to make big changes in the 0.11 release. Perhaps we should at least > > consider overriding the delay in config/server.properties to 0 to improve > > t

Re: Pointer to stream data from Kafka to HDFS

Hi, Assuming you are using Avro then you might want to take a look at: https://github.com/confluentinc/camus If not you can still adopt the pattern used to get data into HDFS. We use something similar at my place of employment. Thanks, Damian On 6 November 2015 at 08:46, Woodbine, Kevin wrote:

Is a Kafka 0.9 broker supposed to connect to itself?

I would think not I'm bringing up a new 0.9 cluster and i'm getting the below Exception (and the same thing on all nodes) - the IP address is the IP for the host the broker is running on. I think DNS is a bit stuffed on these machines and maybe that is the cause, but... any ideas? [2015-11-17

Re: Is a Kafka 0.9 broker supposed to connect to itself?

the broker got a > request more than the default allowed size (~10MB). How many > topic/partitions do you have on this cluster? Do you have clients running > on the broker host? > > Thanks, > > Jun > > > On Tue, Nov 17, 2015 at 4:10 AM, Damian Guy wrote: > >>

[jira] [Resolved] (KAFKA-6412) Improve synchronization in CachingKeyValueStore methods

[ https://issues.apache.org/jira/browse/KAFKA-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6412. --- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4372 [https://github.com

[jira] [Resolved] (KAFKA-6378) NullPointerException on KStream-GlobalKTable leftJoin when KeyValueMapper returns null

[ https://issues.apache.org/jira/browse/KAFKA-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6378. --- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4424 [https://github.com

[jira] [Resolved] (KAFKA-6577) Connect standalone SASL file source and sink test fails without explanation

[ https://issues.apache.org/jira/browse/KAFKA-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6577. --- Resolution: Fixed Fix Version/s: 1.2.0 Issue resolved by pull request 4610 [https://github.com

[jira] [Created] (KAFKA-5956) StreamBuilder#table and StreamsBuilder#globalTable should use serdes from Materialized

Damian Guy created KAFKA-5956: - Summary: StreamBuilder#table and StreamsBuilder#globalTable should use serdes from Materialized Key: KAFKA-5956 URL: https://issues.apache.org/jira/browse/KAFKA-5956

[jira] [Resolved] (KAFKA-5956) StreamBuilder#table and StreamsBuilder#globalTable should use serdes from Materialized

[ https://issues.apache.org/jira/browse/KAFKA-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5956. --- Resolution: Fixed Issue resolved by pull request 3936 [https://github.com/apache/kafka/pull/3936

[jira] [Resolved] (KAFKA-5489) Failing test: InternalTopicIntegrationTest.shouldCompactTopicsForStateChangelogs

[ https://issues.apache.org/jira/browse/KAFKA-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5489. --- Resolution: Cannot Reproduce Closing this as i haven't seen it fail in a while and i'm

[jira] [Resolved] (KAFKA-5765) Move merge() from StreamsBuilder to KStream

[ https://issues.apache.org/jira/browse/KAFKA-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5765. --- Resolution: Fixed Fix Version/s: (was: 1.1.0) 1.0.0 Issue resolved by

[jira] [Created] (KAFKA-5986) Streams State Restoration never completes when logging is disabled

Damian Guy created KAFKA-5986: - Summary: Streams State Restoration never completes when logging is disabled Key: KAFKA-5986 URL: https://issues.apache.org/jira/browse/KAFKA-5986 Project: Kafka

[jira] [Created] (KAFKA-6001) Remove from usages of Materialized in Streams

Damian Guy created KAFKA-6001: - Summary: Remove from usages of Materialized in Streams Key: KAFKA-6001 URL: https://issues.apache.org/jira/browse/KAFKA-6001 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-5985) Mention the need to close store iterators

[ https://issues.apache.org/jira/browse/KAFKA-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5985. --- Resolution: Fixed Issue resolved by pull request 3994 [https://github.com/apache/kafka/pull/3994

[jira] [Resolved] (KAFKA-4890) State directory being deleted when another thread holds the lock

[ https://issues.apache.org/jira/browse/KAFKA-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4890. --- Resolution: Duplicate > State directory being deleted when another thread holds the l

[jira] [Resolved] (KAFKA-6023) ThreadCache#sizeBytes() should check overflow

[ https://issues.apache.org/jira/browse/KAFKA-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6023. --- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4041 [https://github.com

[jira] [Resolved] (KAFKA-6069) Streams metrics tagged incorrectly

[ https://issues.apache.org/jira/browse/KAFKA-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6069. --- Resolution: Fixed Fix Version/s: 1.0.1 1.1.0 Issue resolved by pull request

[jira] [Resolved] (KAFKA-6186) RocksDB based WindowStore fail to create db file on Windows OS

[ https://issues.apache.org/jira/browse/KAFKA-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6186. --- Resolution: Duplicate > RocksDB based WindowStore fail to create db file on Windows

[jira] [Created] (KAFKA-6259) Make KafkaStreams.cleanup() clean global state directory

Damian Guy created KAFKA-6259: - Summary: Make KafkaStreams.cleanup() clean global state directory Key: KAFKA-6259 URL: https://issues.apache.org/jira/browse/KAFKA-6259 Project: Kafka Issue Type

[jira] [Created] (KAFKA-6349) ConcurrentModificationException during streams state restoration

Damian Guy created KAFKA-6349: - Summary: ConcurrentModificationException during streams state restoration Key: KAFKA-6349 URL: https://issues.apache.org/jira/browse/KAFKA-6349 Project: Kafka

[jira] [Created] (KAFKA-6360) RocksDB segments not removed when store is closed causes re-initialization to fail

Damian Guy created KAFKA-6360: - Summary: RocksDB segments not removed when store is closed causes re-initialization to fail Key: KAFKA-6360 URL: https://issues.apache.org/jira/browse/KAFKA-6360 Project

[jira] [Resolved] (KAFKA-4913) creating a window store with one segment throws division by zero error

[ https://issues.apache.org/jira/browse/KAFKA-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4913. --- Resolution: Fixed Fix Version/s: (was: 0.11.0.1) 0.11.1.0 Issue

[jira] [Resolved] (KAFKA-5487) Rolling upgrade test for streams

[ https://issues.apache.org/jira/browse/KAFKA-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5487. --- Resolution: Fixed Fix Version/s: (was: 0.11.0.1) 0.11.1.0 Issue

[jira] [Created] (KAFKA-5556) KafkaConsumer throws: java.lang.IllegalStateException: > Attempt to retrieve exception from future which hasn't failed

Damian Guy created KAFKA-5556: - Summary: KafkaConsumer throws: java.lang.IllegalStateException: > Attempt to retrieve exception from future which hasn't failed Key: KAFKA-5556 URL: https://issues.apache.

[jira] [Resolved] (KAFKA-5508) Documentation for altering topics

[ https://issues.apache.org/jira/browse/KAFKA-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5508. --- Resolution: Fixed Fix Version/s: 0.11.0.1 0.11.1.0 Issue resolved by pull

[jira] [Created] (KAFKA-5562) Do streams state directory cleanup on a single thread

Damian Guy created KAFKA-5562: - Summary: Do streams state directory cleanup on a single thread Key: KAFKA-5562 URL: https://issues.apache.org/jira/browse/KAFKA-5562 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-5566) Instable test QueryableStateIntegrationTest.shouldAllowToQueryAfterThreadDied

[ https://issues.apache.org/jira/browse/KAFKA-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5566. --- Resolution: Fixed Fix Version/s: 0.11.0.1 0.11.1.0 Issue resolved by pull

[jira] [Created] (KAFKA-5578) Streams Task Assignor should consider the staleness of state directories when allocating tasks

Damian Guy created KAFKA-5578: - Summary: Streams Task Assignor should consider the staleness of state directories when allocating tasks Key: KAFKA-5578 URL: https://issues.apache.org/jira/browse/KAFKA-5578

[jira] [Resolved] (KAFKA-5157) Options for handling corrupt data during deserialization

[ https://issues.apache.org/jira/browse/KAFKA-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-5157. --- Resolution: Fixed Issue resolved by pull request 3423 [https://github.com/apache/kafka/pull/3423

[jira] [Resolved] (KAFKA-3741) Allow setting of default topic configs via StreamsConfig

[ https://issues.apache.org/jira/browse/KAFKA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-3741. --- Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request 3459 [https

<    1   2   3   4   5   6   7   8   >