stack commented on HBASE-20347:

Of note, HBASE-20351 was case of my having an old log4j in place. My shell was 
full of spew. Would be good to note that new installs might experience this 
too... and how to 'fix' it.

> [DOC] upgrade section should warn about logging changes
> -------------------------------------------------------
>                 Key: HBASE-20347
>                 URL: https://issues.apache.org/jira/browse/HBASE-20347
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation, logging
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Sean Busbey
>            Priority: Critical
>             Fix For: 2.0.0
> HBASE-10092 deserves a note in the upgrade section, even if we believe that 
> existing out-of-the-box log4j configuration should work seemlessly.

This message was sent by Atlassian JIRA

Reply via email to