GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/157
SAMZA-1258. Integration tests. Happy Path.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/navina/samza unitTestHappyPath3
Alternatively you can
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/156
SAMZA-1257: make sure a dataChange listener in LeaderElection is always
initialized.
@xinyuiscool, @navina please review.
You can merge this pull request into a Git repository by running:
$ git
GitHub user jmakes opened a pull request:
https://github.com/apache/samza/pull/155
SAMZA-1256: Improve trace logging for troubleshooting the fluent API
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jmakes/samza operator-trace-l
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/151
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Some more logs from Kakja
WARN [2017-05-01 15:21:19,132]
kafka.server.ReplicaFetcherThread:[Logging$class:warn:83] -
[ReplicaFetcherThread-0-3] - [ReplicaFetcherThread-0-3], Replica 0 for
partition [Topic3,17] reset its fetch offset from 45039137 to current
leader 3's latest offset 45039132
INFO
Looking further, the reason for this "jump back" seems not so straight
forward:
In Kafka's Simple Consumer code:
private def sendRequest(request: RequestOrResponse): NetworkReceive = {
lock synchronized {
var response: NetworkReceive = null
try {
getOrMakeConnection()
blockin
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/127
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Thanks Xinyu, that would be a nice improvement!
- Chris
On Mon, May 1, 2017 at 9:58 PM, xinyu liu wrote:
> Looked again at Chris's beam-samza-runner implementation. Seems
> LocalApplicationRunner.run() should be asynchronous too. Current
> implementation is actually using a latch to wait for th
