GitHub user shanthoosh opened a pull request:
https://github.com/apache/samza/pull/240
SAMZA-1304: Handling duplicate stream processor registration.
When a stream processor registers with same processorId as already existing
processor in processor group, it's registration should
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/239
SAMZA-1165. cleanup old zk versions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sborya/samza zkCleanUpBarrier1
Alternatively you can review
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/238
---
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
Hey Evgeny,
We haven't seen this with our jobs, but here are some thoughts and
questions for you to consider.
Is the container able to keep up with its inputs? The further behind, the
more it will fill buffers.
Samza has one buffer, which is controlled by configs
Hello. Heap size of running samza container is about 7 Gb and there are a huge
numbers of IncomingMessageEnvelope as unreachable objects in thread dump.
What's the reason of this? It's just a samza task with empty process method.
