[ 
https://issues.apache.org/jira/browse/HBASE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298884#comment-16298884
 ] 

stack commented on HBASE-10092:
-------------------------------

These are the failures...

[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR] 
org.apache.hadoop.hbase.security.token.TestZKSecretWatcher.testKeyUpdate(org.apache.hadoop.hbase.security.token.TestZKSecretWatcher)
[ERROR]   Run 1: TestZKSecretWatcher.testKeyUpdate:178 expected null, but 
was:<AuthenticationKey[ id=2, expiration=9223372036854775807 ]>
[ERROR]   Run 2: TestZKSecretWatcher.testKeyUpdate:147 
expected:<AuthenticationKey[ id=5, expiration=9223372036854775807 ]> but 
was:<AuthenticationKey[ id=4, expiration=9223372036854775807 ]>
[ERROR]   Run 3: TestZKSecretWatcher.testKeyUpdate:147 
expected:<AuthenticationKey[ id=6, expiration=9223372036854775807 ]> but 
was:<AuthenticationKey[ id=4, expiration=9223372036854775807 ]>
[INFO] 
[ERROR] Errors: 
[ERROR]   TestDLSFSHLog>AbstractTestDLS.testThreeRSAbort:404 » TableNotFound 
testThreeRS...
[INFO] 
[ERROR] Tests run: 3410, Failures: 1, Errors: 1, Skipped: 33
[INFO] 

No other timeouts. The above are 'known' flakey/being worked on.

Let me commit this. Can work on teething issues in follow-up.

> Move to slf4j
> -------------
>
>                 Key: HBASE-10092
>                 URL: https://issues.apache.org/jira/browse/HBASE-10092
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: Balazs Meszaros
>            Priority: Critical
>             Fix For: 2.0.0-beta-1
>
>         Attachments: 10092.txt, 10092v2.txt, HBASE-10092-preview-v0.patch, 
> HBASE-10092.master.001.patch, HBASE-10092.master.002.patch, 
> HBASE-10092.master.003.patch, HBASE-10092.master.004.patch, HBASE-10092.patch
>
>
> Allows logging with less friction.  See http://logging.apache.org/log4j/2.x/  
> This rather radical transition can be done w/ minor change given they have an 
> adapter for apache's logging, the one we use.  They also have and adapter for 
> slf4j so we likely can remove at least some of the 4 versions of this module 
> our dependencies make use of.
> I made a start in attached patch but am currently stuck in maven dependency 
> resolve hell courtesy of our slf4j.  Fixing will take some concentration and 
> a good net connection, an item I currently lack.  Other TODOs are that will 
> need to fix our little log level setting jsp page -- will likely have to undo 
> our use of hadoop's tool here -- and the config system changes a little.
> I will return to this project soon.  Will bring numbers.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to