phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4151) Tests extending BaseQueryIT are flapping
Date Fri, 01 Sep 2017 21:02:00 GMT

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

James Taylor commented on PHOENIX-4151:
---------------------------------------

Since we can turn guideposts on at the table level, we can have tests that use stats in tests
derived from ParallelStatsDisabledIT. Perhaps we should rename the class to prevent confusion?

I think we need to narrow down the cause. Can we get a better stack trace? You could try removing
the CURRENT_SCN setting. In theory it shouldn't matter, though.

> Tests extending BaseQueryIT are flapping
> ----------------------------------------
>
>                 Key: PHOENIX-4151
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4151
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>
> Sample failures:
> {code}
> ERROR] testNotInListOfFloat[NotQueryIT_1](org.apache.phoenix.end2end.NotQueryIT)  Time
elapsed: 0.001 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.NotQueryIT.<init>(NotQueryIT.java:56)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.NotQueryIT.<init>(NotQueryIT.java:56)
> {code}
> {code}
> [ERROR] testValidStringConcatExpression[indexDDL=CREATE INDEX %s ON %s (a_integer, a_string)
INCLUDE (    B_STRING,     A_DATE) %s,mutable=false,columnEncoded=false](org.apache.phoenix.end2end.QueryIT)
 Time elapsed: 0.014 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.QueryIT.<init>(QueryIT.java:66)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.QueryIT.<init>(QueryIT.java:66)
> {code}
> {code}
> [ERROR] testNullMultiCondCaseStatement[CaseStatementIT_1](org.apache.phoenix.end2end.CaseStatementIT)
 Time elapsed: 0.007 s  <<< ERROR!
> java.lang.RuntimeException: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.CaseStatementIT.<init>(CaseStatementIT.java:58)
> Caused by: java.sql.SQLTimeoutException: Operation timed out.
> 	at org.apache.phoenix.end2end.CaseStatementIT.<init>(CaseStatementIT.java:58)
> {code}
> My hunch is that timeouts are happening when creating tables or indices. Probably some
sort of a timestamp/scn issue. [~jamestaylor] - any ideas? Would injecting our own clock in
EnvironmentEdge help?



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

Mime
View raw message