[
https://issues.apache.org/jira/browse/IGNITE-12584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026648#comment-17026648
]
Ivan Pavlukhin commented on IGNITE-12584:
-----------------------------------------
[~77aditya77], as you can see in logs "Query execution is too long" message is
a warning. Do you have any other problems except messages in logs? By default a
query is treated long if it executes longer than 3 seconds. This timeout can be
redefined with
{{org.apache.ignite.configuration.IgniteConfiguration#setLongQueryWarningTimeout}}
if needed.
> Query execution is too long issue!
> ----------------------------------
>
> Key: IGNITE-12584
> URL: https://issues.apache.org/jira/browse/IGNITE-12584
> Project: Ignite
> Issue Type: Bug
> Reporter: Aditya
> Priority: Major
> Attachments: uploadthis.txt
>
>
> When querying via some java application and if the topology is in such a way
> that two clients connect to one server node, then some times we are getting
> an exception saying query execution is too long.
>
> This is the SQL schema for table
>
> stmt.executeUpdate("CREATE TABLE DOCIDS (" +
> " id LONG PRIMARY KEY, url VARCHAR, score LONG, appname VARCHAR) " +
> " WITH \"template=replicated\"");
>
> stmt.executeUpdate("CREATE INDEX idx_doc_name_url ON DOCIDS (appname, url)");
>
> Query ->
> SqlFieldsQuery query = new SqlFieldsQuery("SELECT count(id) FROM DOCIDS");
> FieldsQueryCursor<List<?>> cursor = cache.query(query);
> For warning prints, please check the attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
