This also seems somewhat related to the mail on this group a few days back
- with subject 'Messages lost after broker failure'.
If someone had set auto.offset.reset to largest, then reverse would happen
- i.e samza skipping over kafka partition queue in face of such failures.
On Tue, May 2, 2017
Hi All,
We recently observed an issue in our Samza application (version
0.12.0) where we found that that the message offsets "jumped back" causing
many of the messages to be re-processed.
On digging deeper - here is what we found:
- There was a some network related issues at that time causing t
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 the StreamProcessors
to finish, which seems unnecessary. And we can provide a waitUntilFinish()
counterpart to the us
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/58866/#review173529
---
Ship it!
- Navina Ramesh
On May 1, 2017, 11:24 p.m., Boris Sh
GitHub user xinyuiscool opened a pull request:
https://github.com/apache/samza/pull/154
SAMZA-1246: ApplicatonRunner.stats() should include exception in case of
failure
Current when ApplicationRunner.stats() only returns the enum representing
the status. It also need to include the
GitHub user navina opened a pull request:
https://github.com/apache/samza/pull/153
SAMZA-1251 - Remove DebounceTimer dependency from ZkLeaderElector
Fyi: This PR depends on PR #148
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/149
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/150
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/152
---
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
GitHub user jmakes opened a pull request:
https://github.com/apache/samza/pull/152
SAMZA-1250: JobRunner.kill doesn't terminate cleanly with YarnJob.
1. The ClientHelper now checks inactive application IDs so it can get
status for terminated jobs in addition to running jobs
2. J
GitHub user lhaiesp opened a pull request:
https://github.com/apache/samza/pull/151
fix HdfsSystemAdmin when staging directory is empty
getSystemStreamMetadata has the potential side effect to persist metadata
to a staging directory on hdfs. This could fail if staging directory is e
GitHub user jmakes opened a pull request:
https://github.com/apache/samza/pull/150
SAMZA-1214: Bug - system-scoped stream default configs may not be honored
* Re-introduced deprecated system-stream configs into config table
* Fixed position of task.consumer.batch.size in config t
GitHub user vjagadish1989 opened a pull request:
https://github.com/apache/samza/pull/149
SAMZA-1249: Fix equality for WindowKey for Non-keyed tumbling windows
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vjagadish1989/samza s
13 matches
Mail list logo
