Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/96
---
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 enable
This may only be tangentially related.
We identified and fixed a producer deadlock bug in Kafka producer in Samza
0.12 - https://issues.apache.org/jira/browse/SAMZA-1069 .
On Tue, Apr 11, 2017 at 8:55 AM, Jagadish Venkatraman <
jagadish1...@gmail.com> wrote:
> - Are all tasks in the container no
- Are all tasks in the container not receiving messages?
- The errors that you pointed out are on the BrokerProxy threads. Usually,
they are re-created upon failures.
- I'm wondering what the main thread is doing?
- Is the call from the main-thread to send hanging? If so, do you have a
log? (The pr
Hello again,
just a quick update regarding this message loss issue.
Our further investigation proved that Samza job was unable to read 10 out of 80
partitions from input topic. Tasks that were consuming those partitions were
stuck. All those tasks were running on the same container. When trying t
