[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/1178 Yeah that would explain why I wasn't hitting it in full-dev, but I did hit it in my test deployment. ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1178 FYI - I tested this on a multi-node cluster. I was experiencing the problem and the topology could not write out any profile measurements. I updated the Profiler lib with these changes and restarting the topology. After the restart, I was able to successfully write out measurements to HBase. I also ensured that the `ProfileBuilderBolt` and `HBaseBolt` were running on different workers during this test. ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/1178 The work-around to this issue, and some documentation of it to the extent you feel necessary should go out to the users list. ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1178 Here is one other detail that I forgot to add to the description. This may be important if you are trying to validate this fix on a multi-node cluster. * This serialization error will never show itself if you are running with a single worker as there is no need for Storm to serialize. * Even when running the Profiler in a cluster on multiple workers, it will only show-up if Storm runs the `ProfileBuilderBolt` and the downstream bolts (`HBaseBolt` or `KafkaBolt`) on a separate worker. This is why you may not always see the problem when running on a cluster (and why it was confusing to track down.) ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/1178 This looks good to me +1 thanks @nickwallen ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user cestella commented on the issue: https://github.com/apache/metron/pull/1178 This is really good work, @nickwallen. I'm +1 by inspection here, pending @JonZeolla's +1 ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/1178 Looks good. I wasn't able to finish my testing last night but I am going to take a stab at validating. Based on your comments above though this was great digging, thanks. ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1178 Sure. Done. ---
[GitHub] metron issue #1178: METRON-1757 Storm Profiler Serialization Exception
Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/1178 While you're at it, what do you think about making a tweak to the related instructions? Updating [this](https://github.com/apache/metron/tree/master/metron-analytics/metron-profiler#deploying-profiles-with-the-stellar-shell) to reference `source /etc/default/metron` and then use `$ZOOKEEPER` instead of `ZK:2181` so the steps more copy/pastable. ---
