Re: "Failed to update metadata" in integration test for exactly once stream and custom store

Yeah, I'll open a PR. 2017-07-12 11:07 GMT-06:00 Matthias J. Sax : > Ups. That is definitely a bug in the test. Thanks for pointing it out! > > Do you wanna open a PR it? If not, I can take care, too. > > -Matthias > > On 7/12/17 8:48 AM, Joel Dice . wrote: >> After some

Re: "Failed to update metadata" in integration test for exactly once stream and custom store

Ups. That is definitely a bug in the test. Thanks for pointing it out! Do you wanna open a PR it? If not, I can take care, too. -Matthias On 7/12/17 8:48 AM, Joel Dice . wrote: > After some debugging, I figured it out. The name of my custom store > was "mapStore", so the store tried to log

Re: "Failed to update metadata" in integration test for exactly once stream and custom store

After some debugging, I figured it out. The name of my custom store was "mapStore", so the store tried to log changes to a topic with that name, but my test case never created such a topic. Unsurprisingly, the producer couldn't get metadata for a nonexistent topic, so it failed with a timeout.

Re: "Failed to update metadata" in integration test for exactly once stream and custom store

Seems Streams cannot connect (or looses connection) to the brokers. Not sure why. You can also have a look here for our own EOS Streams integration test: https://github.com/apache/kafka/blob/trunk/streams/src/test/java/org/apache/kafka/streams/integration/EosIntegrationTest.java -Matthias On

"Failed to update metadata" in integration test for exactly once stream and custom store

Hi all, I wrote an integration test to see how Kafka Streams handles exactly once processing with a custom state store, and it's failing with this error: org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 6 ms I'm not sure whether this is a bug in my code, a