Hi Chris
We are using them like you described.
Performance is very good compared to the database used before.
Beware that until https://issues.apache.org/jira/browse/KAFKA-7380
is done the startup will be blocked until all global stores are restored
(sequentially).
This can take a little for larg
Hi Chris
Yes, for every state store in a kafka streams application, the state
restore listener is executed.
-Bill
On Tue, Nov 13, 2018 at 10:36 PM Chris Toomey wrote:
> Thanks Bill. So poking around the code a bit, it looks like perhaps any
> kafka streams execution that produces a state store
I did some digging into our broker logs, and it looks like the failure is
coming from Cruise Control - it's trying to cast an Integer into a String
and throwing an Exception. I'll take things over there for follow-up.
Sorry for bothering! :)
On Tue, Nov 13, 2018 at 9:05 PM Andrew Brown
wrote:
>
Thanks Bill. So poking around the code a bit, it looks like perhaps any
kafka streams execution that produces a state store would execute this
"restore state store" operation, even creating a new state store, is that
correct? If so that indeed could be just what I need.
On Tue, Nov 13, 2018 at 6:
Hi Chris,
I'm not sure I totally understand your requirements but the
StateRestoreListener (
https://kafka.apache.org/20/javadoc/org/apache/kafka/streams/processor/StateRestoreListener.html)
class provides callbacks when restoring state stores (including
GlobalStores) and may provide what you are
Hi!
I'm trying to set metric.reporters as a cluster-wide dynamic config
(specifically for setting up Cruise Control, as it happens), and I've found
that our 2.0.0 brokers aren't picking up the new config - they only do so
when the brokers restart.
I'm not setting metric.reporters in the server.pr
Definitely Ryanne -- that's what I meant by "topics would be compacted".
But that doesn't obviate checking bootstrapping progress.
On Tue, Nov 13, 2018 at 5:04 PM Ryanne Dolan wrote:
> Chris, consider using log compaction.
>
> Ryanne
>
> On Tue, Nov 13, 2018, 3:17 PM Chris Toomey wrote:
>
> >
Chris, consider using log compaction.
Ryanne
On Tue, Nov 13, 2018, 3:17 PM Chris Toomey wrote:
> We're considering using GlobalKTables / KeyValueStores for locally caching
> topic content in services. The topics would be compacted such that only the
> latest key/value pair would exist for a giv
We're considering using GlobalKTables / KeyValueStores for locally caching
topic content in services. The topics would be compacted such that only the
latest key/value pair would exist for a given key.
One question that's come up is how to determine, when bootstrapping the
app, when the cache has
+1 (non-binding)
Verified signatures and checksums of release artifacts
Performed quickstart steps on rc artifacts (both scala 2.11 and 2.12)
Andras
On Tue, Nov 13, 2018 at 10:51 AM Eno Thereska
wrote:
> Built code and ran tests. Getting a single integration test failure:
>
> kafka.log.LogClea
Built code and ran tests. Getting a single integration test failure:
kafka.log.LogCleanerParameterizedIntegrationTest >
testCleansCombinedCompactAndDeleteTopic[3] FAILED
java.lang.AssertionError: Contents of the map shouldn't change
expected: (340,340), 5 -> (345,345), 10 -> (350,350), 14 ->
(
11 matches
Mail list logo
