You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2017/09/01 20:07:00 UTC

[jira] [Created] (PHOENIX-4151) Tests extending BaseQueryIT are flapping

Samarth Jain created PHOENIX-4151:
-------------------------------------

             Summary: 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)