You're right! (Of course you knew that already). I did what I should have done earlier and checked out the project from just before PIRK-11 was committed, and indeed one can change log levels there.
Back to making this work. On Thu, Sep 22, 2016 at 10:23 PM, Ellison Anne Williams (JIRA) < j...@apache.org> wrote: > > [ https://issues.apache.org/jira/browse/PIRK-65?page=com. > atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=15515142#comment-15515142 ] > > Ellison Anne Williams commented on PIRK-65: > ------------------------------------------- > > So, log4j should work just fine on a cluster - before we upgraded to > log4j2, logging worked just fine on a hadoop cluster... > > > Debug Logging Not Working within Distributed Applications > > --------------------------------------------------------- > > > > Key: PIRK-65 > > URL: https://issues.apache.org/jira/browse/PIRK-65 > > Project: PIRK > > Issue Type: Bug > > Reporter: Ellison Anne Williams > > Assignee: Walter Ray-Dulany > > > > It appears that debug logging is not working within distributed > applications - only within standalone components. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >