[
https://issues.apache.org/jira/browse/PHOENIX-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086371#comment-17086371
]
Hadoop QA commented on PHOENIX-4521:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/13000343/PHOENIX-4521.master.v7.patch
against master branch at commit c627f94b50802bde493bfef1a2a090d9568eff6f.
ATTACHMENT ID: 13000343
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ +
",START_TIME,QUERY_GROUP,QUERY_ID,QUERY,TENANT_ID,THREAD_NUMBER,CONCURRENCY_LEVEL"),
+ LOGGER.info("Queryset timeout of " + executionDurationInMs + "
ms reached; current time is " + threadElapsedTime + " ms."
+ + "\nStopping queryset execution for query " +
query.getId() + " on thread " + threadName + "...");
+ Pair<Long, Long> r = getResults(rs, queryIteration,
isSelectCountStatement, queryStartTime);
+ * @return a Pair whose first value is the resultRowCount, and whose
second value is whether the query timed out.
+ Pair<Long, Long> getResults(ResultSet rs, String queryIteration, boolean
isSelectCountStatement, Long queryStartTime) throws Exception {
+ return new Pair(resultRowCount,
EnvironmentEdgeManager.currentTimeMillis() - queryStartTime);
+ <!-- This column type defines what will generally happen to
VARCHAR fields unless they are explicitly defined or overridden elsewhere -->
+ <!--Note: 1. Minimum of executionDurationInMs or
numberOfExecutions. Which ever is reached first
+ 2. DDL included in query are executed only once on start
of querySet execution.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3768//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3768//console
This message is automatically generated.
> Allow Pherf scenario to define per query max allowed query execution duration
> after which thread is interrupted
> ---------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4521
> URL: https://issues.apache.org/jira/browse/PHOENIX-4521
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James R. Taylor
> Assignee: Christine Feng
> Priority: Major
> Labels: phoenix-hardening
> Attachments: PHOENIX-4521.master.v1.patch,
> PHOENIX-4521.master.v2.patch, PHOENIX-4521.master.v2.patch,
> PHOENIX-4521.master.v3.patch, PHOENIX-4521.master.v4.patch,
> PHOENIX-4521.master.v5.patch, PHOENIX-4521.master.v6.patch,
> PHOENIX-4521.master.v7.patch
>
> Time Spent: 12h 50m
> Remaining Estimate: 0h
>
> Some clients interrupt the client thread if it doesn't complete in a required
> amount of time. It would be good if Pherf supported setting this up so we
> mimic client behavior more closely, as we're theorizing this may be causing
> some issues.
>
> PLAN
> # Make necessary changes so new timeoutDuration property is recognized and
> parsed correctly from the scenario .xml file (completed)
> # Implement a per-query, per-iteration timeout
> # Write ITs and UTs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
