You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Ali Nazemian (JIRA)" <ji...@apache.org> on 2018/05/03 04:28:00 UTC
[jira] [Created] (METRON-1546) Returning an empty array list at
parse time causes tuple to be considered as uncommitted and stall the
parser topology
Ali Nazemian created METRON-1546:
------------------------------------
Summary: Returning an empty array list at parse time causes tuple to be considered as uncommitted and stall the parser topology
Key: METRON-1546
URL: https://issues.apache.org/jira/browse/METRON-1546
Project: Metron
Issue Type: Bug
Reporter: Ali Nazemian
It appears if (for any reason) an empty List is returned in parser sub-classes (any sub-class of BasicParser) the corresponding tuple won't be committed. Hence, Storm retries it based on the retry strategy which won't be required for this situation. Also, if we hit the "spout.maxUncommittedOffsets" parser topology stalls and it needs to be restarted!
This issue can be reproduced by using a very small value for "spout.maxUncommittedOffsets".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)