Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-200553473
@arunmahadevan @HeartSaVioR Looking at the perf analysis from @roshannaik
It looks to be there is enough evidence to consider this as serious issue in
performance. Given that eventlogging is new feature and we do have evidence its
causing perf issue I am +1 on disabling it by default. I understand that once
they disabled they can't enable it in a running topology and that is OK. For
most usecases this might be used in dev cluster than a production cluster. Also
this is a blocker for 1.0 release , lets get this merged in and see if there is
a better a way to enable it by default and we can that in 1.1 release.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
