Found this thread after posting an alternative idea after we starting
hitting this issue ourselves for a job that has a lot of state stores and
topic partitions. My suggestion was to have consumer groups have a
configurable minimum member count before consumption begins, but that has
its own trade
Apologies, just discovered KIP-134, which would address our specific
problem directly via delaying consumer join.
On Mon, Jul 10, 2017 at 4:53 PM, Greg Fodor wrote:
> With Kafka Streams, it's common to spin up and shut down clusters of
> consumers by performing a graceful shutdown
With Kafka Streams, it's common to spin up and shut down clusters of
consumers by performing a graceful shutdown and restart during a deploy.
One thing we've been running into is that during the startup and shutdown
of a kafka streams clusters you often can have multiple rebalances as the
consumer
We've noticed that there's a lot of contention on get/set of schemas by ID
in CachedSchemaRegistryClient if that object is shared across threads. All
of the methods on CachedSchemaRegistryClient are synchronized and
getBySubjectAndId is called when deserializing a record:
https://github.com/conflue
topic
while allowing CreateTime timestamps to land on the other topics.
On Thu, Jul 6, 2017 at 9:32 PM, Greg Fodor wrote:
> I managed to answer some of my own questions :)
>
> For future google'ers:
>
> to deal with retention.ms see https://issues.apache.org/
> jira/browse/KA
Greg Fodor created KAFKA-5571:
-
Summary: Possible deadlock during shutdown in setState in kafka
streams 10.2
Key: KAFKA-5571
URL: https://issues.apache.org/jira/browse/KAFKA-5571
Project: Kafka
Sure thing: https://issues.apache.org/jira/browse/KAFKA-5571
On Fri, Jul 7, 2017 at 2:59 AM, Damian Guy wrote:
> Hi Greg,
>
> Would you mind creating a JIRA for this with the thread dump ( i don't see
> it attached to your message).
>
> Thanks,
> Damian
>
>
I'm running a 10.2 job across 5 nodes with 32 stream threads on each node
and find that when gracefully shutdown all of them at once via an ansible
scripts, some of the nodes end up freezing -- at a glance the attached
thread dump implies a deadlock between stream threads trying to update
their sta
https://issues.apache.org/jira/browse/KAFKA-5344
In our case, we can live with setting the retention.ms during backfills.
Still would like to know if there are any better practices for dealing with
mis-stamped records during backills w/ state store topics.
On Thu, Jul 6, 2017 at 12:32 PM, Greg Fodor wrote:
>
threads per host.
- Peak TPS seems to be approximately 5k-10k tuples/sec per node. We're
reprocessing historical data in kafka.
On Thu, Jul 6, 2017 at 10:45 AM, Greg Fodor wrote:
> That's great news, thanks!
>
> On Thu, Jul 6, 2017 at 6:18 AM, Damian Guy wrote:
>
>> H
Hey all, we are currently working on migrating our system to kafka 10.2
from 10.0 and one thing that we have hit that I wanted some advice on is
dealing with the new log retention/rolling semantics that are based on
timestamps.
We send telemetry data from installed clients into kafka via kafka RES
t;> Thanks Greg. I'll look into it more tomorrow. Just finding it difficult
> >> to reproduce in a test.
> >> Thanks for providing the sequence, gives me something to try and repo.
> >> Appreciated.
> >>
> >> Thanks,
> >> Damian
> >
, Greg Fodor wrote:
> The issue I am hitting is not the directory locking issues we've seen in
> the past. The issue seems to be, as you mentioned, that the state dir is
> getting deleted by the store cleanup process, but there are still tasks
> running that are trying to flush th
re were some minor changes around this in
> > 0.11.0 to make it less likely to happen, but we've only ever seen the
> > locking fail in the event of a rebalance. When everything is running
> state
> > dirs shouldn't be deleted if they are being used as the lock
, this does not seem to be happening during a rebalancing event, but
after the cluster is stable.
On Tue, Jul 4, 2017 at 12:29 PM, Greg Fodor wrote:
> Upon another run, I see the same error occur during a rebalance, so either
> my log was showing a rebalance or there is a shared underlying
Upon another run, I see the same error occur during a rebalance, so either
my log was showing a rebalance or there is a shared underlying issue with
state stores.
On Tue, Jul 4, 2017 at 11:35 AM, Greg Fodor wrote:
> Also, I am on 0.10.2.1, so poll interval was already set to MAX_VALUE.
>
Also, I am on 0.10.2.1, so poll interval was already set to MAX_VALUE.
On Tue, Jul 4, 2017 at 11:28 AM, Greg Fodor wrote:
> I've nuked the nodes this happened on, but the job had been running for
> about 5-10 minutes across 5 nodes before this happened. Does the log show a
>
setting `state.cleanup.delay.ms` to a higher value (default is 10
> minutes),
> to try and avoid it happening during a rebalance (I know this isn't a fix,
> but will make it less likely to happen).
>
> Thanks,
> Damian
>
> On Tue, 4 Jul 2017 at 12:43 Greg Fodor wrote:
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15627097#comment-15627097
]
Greg Fodor commented on KAFKA-4113:
---
Hey [~guozhang], I have been able to reprodu
gracefully shut down our jobs in certain cases so there's a chance that
might be related. Anyhow, now that I have a better understanding of things
I will be able to investigate if we experience missing keys in the future,
thanks!
On Oct 20, 2016 2:08 PM, "Greg Fodor (JIRA)" wrote
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15593018#comment-15593018
]
Greg Fodor commented on KAFKA-4113:
---
Oh, so it should be doing exactly what makes s
loser.cgi?path=/kafka/0.10.1.0/k
>> > > afka_2.10-0.10.1.0.tgz
>> > >
>> > > Thanks to the 115 contributors on this release!
>> > >
>> > > Alex Glikson, Alex Loddengaard, Alexey Ozeritsky, Alexey Romanchuk,
>> > Andrea
>> &
Greg Fodor created KAFKA-4317:
-
Summary: RocksDB checkpoint files lost on kill -9
Key: KAFKA-4317
URL: https://issues.apache.org/jira/browse/KAFKA-4317
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587991#comment-15587991
]
Greg Fodor commented on KAFKA-4113:
---
I guess what I would argue is that KStreamBui
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587966#comment-15587966
]
Greg Fodor commented on KAFKA-4113:
---
Having played around with Kafka Streams f
[
https://issues.apache.org/jira/browse/KAFKA-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583149#comment-15583149
]
Greg Fodor commented on KAFKA-3545:
---
Yes
> Generalized Serdes for L
[
https://issues.apache.org/jira/browse/KAFKA-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor resolved KAFKA-3545.
---
Resolution: Fixed
Fix Version/s: 0.10.1.0
> Generalized Serdes for List/
g those many serde calls per store). But if you do
> observe significant performance degradation I'd personally love to learn
> more and help on that end.
>
>
> Guozhang
>
>
>
>
>
> On Tue, Oct 11, 2016 at 10:10 AM, Greg Fodor wrote:
>
> > Thanks Eno -- m
perations#write-buffer
> <https://github.com/facebook/rocksdb/wiki/Basic-Operations#write-buffer>
>
> They can override these settings by creating an impl of RocksDBConfigSetter
> and setting StreamsConfig.ROCKSDB_CONFIG_SETTER_CLASS_CONFIG in Kafka Streams.
>
> Hope this h
size to 0. That should
> give you the old behaviour:
> streamsConfiguration.put(StreamsConfig.CACHE_MAX_BYTES_BUFFERING_CONFIG,
> 0L);
>
> Your PR is an alternative, but it requires changing the APIs and would
> require a KIP.
>
> Thanks
> Eno
>
> > On 9 Oct 2016, at 23:4
[
https://issues.apache.org/jira/browse/KAFKA-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15560765#comment-15560765
]
Greg Fodor commented on KAFKA-4281:
---
PR: https://github.com/apache/kafka/pull/1998
JIRA opened here: https://issues.apache.org/jira/browse/KAFKA-4281
On Sun, Oct 9, 2016 at 2:02 AM, Greg Fodor wrote:
> I went ahead and did some more testing, and it feels to me one option
> for resolving this issue is having a method on KGroupedStream which
> can be used to configu
Greg Fodor created KAFKA-4281:
-
Summary: Should be able to forward aggregation values immediately
Key: KAFKA-4281
URL: https://issues.apache.org/jira/browse/KAFKA-4281
Project: Kafka
Issue Type
records are forwarded immediately it resolves
the issue I am seeing. Having it be done on a per-KGroupedStream basis
would provide maximum flexibility.
On Sun, Oct 9, 2016 at 1:06 AM, Greg Fodor wrote:
> I'm taking 0.10.1 for a spin on our existing Kafka Streams jobs and
> I'm hitti
I'm taking 0.10.1 for a spin on our existing Kafka Streams jobs and
I'm hitting what seems to be a serious issue (at least, for us) with
the changes brought about in KIP-63. In our job, we have a number of
steps in the topology where we perform a repartition and aggregation
on topics that require l
[
https://issues.apache.org/jira/browse/KAFKA-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor resolved KAFKA-4043.
---
Resolution: Not A Problem
> User-defined handler for topology rest
[
https://issues.apache.org/jira/browse/KAFKA-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472271#comment-15472271
]
Greg Fodor commented on KAFKA-4043:
---
Ah, that should work for us. Thanks!
&g
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468374#comment-15468374
]
Greg Fodor commented on KAFKA-3769:
---
It's just the sensor calls inside of Sele
[
https://issues.apache.org/jira/browse/KAFKA-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464171#comment-15464171
]
Greg Fodor edited comment on KAFKA-4120 at 9/5/16 5:34 PM:
---
[
https://issues.apache.org/jira/browse/KAFKA-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464171#comment-15464171
]
Greg Fodor commented on KAFKA-4120:
---
We were able to work around it by just creati
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463861#comment-15463861
]
Greg Fodor commented on KAFKA-3769:
---
I've done some additional profiling a
Greg Fodor created KAFKA-4120:
-
Summary: byte[] keys in RocksDB state stores do not work as
expected
Key: KAFKA-4120
URL: https://issues.apache.org/jira/browse/KAFKA-4120
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443912#comment-15443912
]
Greg Fodor commented on KAFKA-4043:
---
I suppose it looks like there's also not
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433738#comment-15433738
]
Greg Fodor commented on KAFKA-3758:
---
Excited to try this, as our state stores
Greg Fodor created KAFKA-4043:
-
Summary: User-defined handler for topology restart
Key: KAFKA-4043
URL: https://issues.apache.org/jira/browse/KAFKA-4043
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416351#comment-15416351
]
Greg Fodor commented on KAFKA-3752:
---
Oh apologies for mis-reading the ticket, bu
[
https://issues.apache.org/jira/browse/KAFKA-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415664#comment-15415664
]
Greg Fodor commented on KAFKA-3752:
---
Hey [~guozhang], we're hitting this issu
[
https://issues.apache.org/jira/browse/KAFKA-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor resolved KAFKA-3770.
---
Resolution: Fixed
Fixed via KAFKA-3786
> KStream job should be able to specify linger
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326778#comment-15326778
]
Greg Fodor commented on KAFKA-3769:
---
Discussion/resolution moved to: h
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3811:
--
Attachment: screenshot-latency.png
> Introduce Kafka Streams metrics recording lev
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324869#comment-15324869
]
Greg Fodor commented on KAFKA-3811:
---
Also, I've attached a screenshot + snap
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3811:
--
Attachment: Muon-latency.zip
> Introduce Kafka Streams metrics recording lev
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324847#comment-15324847
]
Greg Fodor commented on KAFKA-3811:
---
I've also attached a screenshot of YourK
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3811:
--
Attachment: screenshot-1.png
> Introduce Kafka Streams metrics recording lev
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3811:
--
Attachment: Muon-Snapshot.zip
> Introduce Kafka Streams metrics recording lev
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324838#comment-15324838
]
Greg Fodor commented on KAFKA-3811:
---
Hey [~aartigupta], I ran an attached you
Greg Fodor created KAFKA-3811:
-
Summary: Introduce KStream metrics recording levels
Key: KAFKA-3811
URL: https://issues.apache.org/jira/browse/KAFKA-3811
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3811:
--
Summary: Introduce Kafka Streams metrics recording levels (was: Introduce
KStream metrics recording
[
https://issues.apache.org/jira/browse/KAFKA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313461#comment-15313461
]
Greg Fodor commented on KAFKA-3785:
---
https://github.com/apache/kafka/pull/
[
https://issues.apache.org/jira/browse/KAFKA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3785:
--
Component/s: consumer
> Fetcher spending unnecessary time during metrics record
Greg Fodor created KAFKA-3785:
-
Summary: Fetcher spending unnecessary time during metrics recording
Key: KAFKA-3785
URL: https://issues.apache.org/jira/browse/KAFKA-3785
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313434#comment-15313434
]
Greg Fodor commented on KAFKA-3770:
---
Cut a new PR since I screwed up the rebase on
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312913#comment-15312913
]
Greg Fodor commented on KAFKA-3758:
---
also, if we did not run at an elevated numbe
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312912#comment-15312912
]
Greg Fodor commented on KAFKA-3758:
---
Hey, we're running 16 threads -- for th
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311179#comment-15311179
]
Greg Fodor commented on KAFKA-3769:
---
Thanks Jay!
Guozhang, what are your thought
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308306#comment-15308306
]
Greg Fodor commented on KAFKA-3758:
---
No, the kstream job was running across 2 ser
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306381#comment-15306381
]
Greg Fodor commented on KAFKA-3769:
---
Consider the PR a first pass, please advise on
[
https://issues.apache.org/jira/browse/KAFKA-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306371#comment-15306371
]
Greg Fodor commented on KAFKA-3770:
---
https://github.com/apache/kafka/pull/
Greg Fodor created KAFKA-3770:
-
Summary: KStream job should be able to specify linger.ms
Key: KAFKA-3770
URL: https://issues.apache.org/jira/browse/KAFKA-3770
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306321#comment-15306321
]
Greg Fodor commented on KAFKA-3769:
---
It seems it might be desirable to have a wa
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306318#comment-15306318
]
Greg Fodor commented on KAFKA-3769:
---
Actually, additionally it looks like the code
[
https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306306#comment-15306306
]
Greg Fodor commented on KAFKA-3769:
---
https://github.com/apache/kafka/pull/
Greg Fodor created KAFKA-3769:
-
Summary: KStream job spending 60% of time writing metrics
Key: KAFKA-3769
URL: https://issues.apache.org/jira/browse/KAFKA-3769
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor reopened KAFKA-3758:
---
> KStream job fails to recover after Kafka broker stop
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305503#comment-15305503
]
Greg Fodor commented on KAFKA-3758:
---
Oh, actually, I'm not so sure. This was n
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor resolved KAFKA-3758.
---
Resolution: Duplicate
> KStream job fails to recover after Kafka broker stop
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305501#comment-15305501
]
Greg Fodor commented on KAFKA-3758:
---
Ah yes this looks like the same issue, th
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302542#comment-15302542
]
Greg Fodor commented on KAFKA-3758:
---
Also, the log is truncated at the top to the p
[
https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3758:
--
Attachment: muon.log.1.gz
> KStream job fails to recover after Kafka broker stop
Greg Fodor created KAFKA-3758:
-
Summary: KStream job fails to recover after Kafka broker stopped
Key: KAFKA-3758
URL: https://issues.apache.org/jira/browse/KAFKA-3758
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297745#comment-15297745
]
Greg Fodor commented on KAFKA-3745:
---
Actually this seems like a good enough solutio
[
https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297733#comment-15297733
]
Greg Fodor commented on KAFKA-3745:
---
Yes, the join key needs to be added to the f
[
https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297477#comment-15297477
]
Greg Fodor commented on KAFKA-3745:
---
Yep, I admit this is definitely not the
[
https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297250#comment-15297250
]
Greg Fodor commented on KAFKA-3745:
---
sure. we are left joining a KTable again
Greg Fodor created KAFKA-3745:
-
Summary: Consider adding join key to ValueJoiner interface
Key: KAFKA-3745
URL: https://issues.apache.org/jira/browse/KAFKA-3745
Project: Kafka
Issue Type
eptions are not logged in log4j yet before it
>> pop up to the StreamThread. I will file a JIRA for this issue.
>>
>>
>> Guozhang
>>
>> On Thu, May 12, 2016 at 5:57 PM, Greg Fodor wrote:
>>
>>> Hey Guozhang, output was silent (since the log4j is str
09 PM, Guozhang Wang wrote:
> Greg,
>
> Could you post the output from stdout when running the console as well?
>
>
> Guozhang
>
> On Thu, May 12, 2016 at 4:52 PM, Greg Fodor wrote:
>
>> We noticed that some errors were happening in one of our KafkaStreams
>>
We noticed that some errors were happening in one of our KafkaStreams
jobs but they were not appearing in our logs or being sent to our
error reporting service (Airbrake) -- they only became visible on
stdout when running from the console. I believe the reason is because
of this explicit catch-reth
[
https://issues.apache.org/jira/browse/KAFKA-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor updated KAFKA-3619:
--
Description:
The .lock files in the state store directories do not seem to be having their
file
s and change the RB
> title with the JIRA number?
>
> Thanks!
>
> Guozhang
>
> On Mon, Apr 25, 2016 at 12:13 AM, Greg Fodor wrote:
>
>> Apologies for a second posting to the list, but the ASF JIRA is
>> preventing me from creating KAFKA- tickets so I wanted to r
Greg Fodor created KAFKA-3619:
-
Summary: State lock file handle leaks
Key: KAFKA-3619
URL: https://issues.apache.org/jira/browse/KAFKA-3619
Project: Kafka
Issue Type: Bug
Components
e contributor list.
>>
>>
>> Guozhang
>>
>> On Mon, Apr 25, 2016 at 9:14 AM, Greg Fodor wrote:
>>
>> > If I go there, and hit "Create", the Project List at the top has lots
>> > of apache projects does not contain any items contai
g/jira/browse/KAFKA/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
>
> Thanks,
> Liquan
>
> On Mon, Apr 25, 2016 at 12:04 AM, Greg Fodor wrote:
>
>> I am trying to file a bug, but when I go to create a ticket on the ASF
>> Jira, Kafka is not visible in the l
Apologies for a second posting to the list, but the ASF JIRA is
preventing me from creating KAFKA- tickets so I wanted to report this
issue. This seems to be a critical bug with KStreams, the .lock files
in the state store directories do not seem to be having their file
handles freed (despite the l
I am trying to file a bug, but when I go to create a ticket on the ASF
Jira, Kafka is not visible in the list of projects in the first field
of the ticket. I see the hundred+ other Apache projects, but no Kafka
:(
1.map(/*set key*/).through("topic2").aggregateByKey(...);
>
> stream3 = stream1.map(/*a different
> key*/).through("topci3").aggregateByKey(...);
>
> -----
>
> Guozhang
>
>
> On Thu, Apr 14, 2016 at 10:05 AM, Greg Fodor wrote:
>
>> Hi
Hi all, I'm working on a Kafka Streaming job and I've hit a case I
didn't see straightforward support for. I have an input stream topic
I'd like to perform two separate aggregations on, but building up two
parallel sub-topologies with the same source topic at the source
results in an error: "Topic
[
https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Fodor resolved KAFKA-3544.
---
Resolution: Not A Problem
> Missing topics on star
[
https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240723#comment-15240723
]
Greg Fodor commented on KAFKA-3544:
---
Ah this makes sense. Fortunately thanks to
[
https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236512#comment-15236512
]
Greg Fodor edited comment on KAFKA-3544 at 4/12/16 3:0
1 - 100 of 123 matches
Mail list logo
