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

Nick Dimiduk commented on PHOENIX-2529:
---------------------------------------

[~jamestaylor]

bq. Why is it complaining about a zombie test that isn't even a Phoenix test?

Probably the script is grepping for processes and the match expression is too 
generous.

bq. is there a way our current test run could print out any zombie tests? I 
think this is a frequent cause of failures for Phoenix, but it always only 
shows up as the test run timing out.

Our scripts are forked from HBase's scripts, which in turn were forked from 
Hadoop's. I think both of the above have been improved in HBase and could be 
brought into Phoenix. Long-term, I think all of the above are consolidating 
onto the new [Apache Yetus|https://yetus.apache.org/] tools, and we should 
consider the same. [~busbey] has been overseeing recent Yetus releases and has 
offered to provide more user documentation. I also believe [~elserj] recently 
ported Accumulo over to Yetus, or at least has some practical experience using 
it.

> Fixing date generation pattern in Phoenix-Pherf
> -----------------------------------------------
>
>                 Key: PHOENIX-2529
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2529
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.6.0
>            Reporter: Karan Singhal
>            Assignee: Karan Singhal
>              Labels: patch, performance
>             Fix For: 4.6.0, 4.7.0
>
>         Attachments: PHOENIX-2529.patch
>
>
> pherf is generating date in two different patterns using two different API's 
> , SimpleDateformat( pattern -> yyyy-MM-dd HH:mm:ss.SSS z with time zone ) and 
> Joda Date format (pattern -> yyyy-MM-dd HH:mm:ss.SSS without time zone). We 
> need to follow one pattern which have time zone in it using Joda Date Format.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to