Github user liurenjie1024 commented on a diff in the pull request:
https://github.com/apache/storm/pull/2076#discussion_r111876262
--- Diff:
storm-core/src/jvm/org/apache/storm/serialization/KryoTupleDeserializer.java ---
@@ -50,7 +54,8 @@ public Tuple deserialize(byte[] ser) {
List<Object> values = _kryo.deserializeFrom(_kryoInput);
return new TupleImpl(_context, values, taskId, streamName, id);
} catch(IOException e) {
- throw new RuntimeException(e);
+ LOG.error("Failed to deserialize tuple.", e);
--- End diff --
In our case this happens because storm's internal message exchange protocol
is vulnerable to foreign attack. If deserialization fails, you should warn the
user and go on with processing.
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
