[
https://issues.apache.org/jira/browse/IMPALA-7185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530501#comment-16530501
]
ASF subversion and git services commented on IMPALA-7185:
---------------------------------------------------------
Commit e07fbc1b6342836b3e2e472a91c61c5f75d48733 in impala's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=e07fbc1 ]
IMPALA-7185: low statestore custom cluster interval
This changes the default statestore interval for the custom cluster
tests. This can reduce the time taken for the cluster to start and
metadata to load. On some tests this resulted in saving 5+ seconds
per test. Overall it shaved around a minute off the custom cluster
tests.
Testing:
Ran 10 iterations of the tests.
Change-Id: Ia5d1612283ff420d95b0dd0ca5a2a67f56765f79
Reviewed-on: http://gerrit.cloudera.org:8080/10845
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Reduce statestore frequency for custom cluster tests by default
> ---------------------------------------------------------------
>
> Key: IMPALA-7185
> URL: https://issues.apache.org/jira/browse/IMPALA-7185
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
>
> It takes several seconds to run the first query after cluster startup because
> of the statestore propagation delay for the catalog, which adds some real
> time to custom cluster tests. We should think about lowering the default
> update interval for those tests to make them start up faster.
> We could just prefix the statestored_args with lower values, allowing
> individual tests to override if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
