Jason Erickson created SAMZA-945:
------------------------------------
Summary: Samza should report when a task is hung on a large message
Key: SAMZA-945
URL: https://issues.apache.org/jira/browse/SAMZA-945
Project: Samza
Issue Type: Improvement
Affects Versions: 0.9.1
Environment: Running ThreadJobFactory
* samza-kafka_2.10 version 0.9.1
* kafka_2.10 version 0.8.2.1 on the client
* kafka broker 0.9.0.0
Reporter: Jason Erickson
I had a puzzling issue with one of my samza tasks. It works correctly
except for messages on one partition. I had 9 partitions on the topic. If
I send 1000 messages, I only receive about 890 of them.
The issue turned out to be that one of the messages exceeded 1 MB and I had
messed up the configuration of {{max.message.bytes}} for the samza client.
However, rather than give an error message or even a timeout, thread
responsible for the partition with the large message on it got stuck.
See
[thread|http://mail-archives.apache.org/mod_mbox/samza-dev/201604.mbox/%3CCAHtYtjnPa8AaRON7GhSasbu=ynqh8jrqisqjh-fkzeehedg...@mail.gmail.com%3E]
on samza-dev archives for further details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
