Hi,
During the running of Samza, one of brokers in our Kafka cluster went
down, the states of relative topics are shown as pictures below. Then all the
task can’t fetch any messages any more, even after restarted the samza job. But
at the same time , another app consuming the same topic
Great to hear this development on the kinesis consumer!
Let me answer some of your questions here.
*1. "Kinesis does not have a listener/push framework (unless I missed
something)"*
Let me point out that Kinesis has both a push and a pull based model. You
can choose to implement either for your
GitHub user navina opened a pull request:
https://github.com/apache/samza/pull/48
SAMZA-1082 : Implement Leader Election using ZK
Simple implementation of leader election recipe along with unit tests
You can merge this pull request into a Git repository by running:
$ git pull h
This is a call for a vote on a release of Apache Samza 0.12.0. Thanks to
everyone who has contributed to this release. We are very glad to see some
new contributors in this release.
The release candidate can be downloaded from here:
http://home.apache.org/~jagadish/samza-0.12.0-rc2/
The release c
Starting on an integration project between a Kinesis stream and Samza, despite
have no background in either, but I am familiar with most other
messaging/queuing systems.
Decided to keep all state management within Samza instead of using Kinesis'
client library. My plan was to use the default K
Hi all,
LinkedIn will be hosting a Streams Processing meetup next Thursday,
February 16 with speakers from LinkedIn, Uber, and Optimizely.
Abstracts and event information is available at:
https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/237171557/
Hope to see you there!
Ed Yakabo
