Github user aarcro commented on the issue:
https://github.com/apache/zeppelin/pull/830
I had to remove this to get my %sql interpreter running again (on EMR).
From what I can tell on the yarn resource manager, something owned by the
hadoop user was trying to write to zeppelin's log file. I assume zeppelin's
log4j config, shouldn't get used by the spark proc behind it, right?
---
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.
---
