[JBoss JIRA] Created: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
2:26 a.m.
Document queryThresholdInSecs and allow functionality to ensure user queries take no
longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use that
value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the instance
setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:28 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Graeme Gillies updated TEIID-1596:
----------------------------------
Affects Version/s: 7.4
Component/s: Server
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1596:
---------------------------------------
queryThresholdInSecs is not directly used by the engine - there is no side effect in the
runtime from changing this setting. It is used and typically configured through RHQ.
It's not expected that users will modify this value directly in the configuration
file.
On a related note, there was a recent change so that the client can specify a default
query timeout. It sounds like you would also want a server side setting as well. That
would be its own enhancement, which would also cover any tie into vdb specific overrides.
We de-emphasized the use of maxSourceRows in Teiid since it is a weak method of
determining query performance and generally requires the source system to run the full (at
least in terms of execution, even if only a limited set of results is returned) query
anyway. You really don't actually end up protecting the backend, but you do possibly
prevent excessive query processing in Teiid.
There is a pending request enhancement that is to prevent source query execution based
upon a cost determination. That may be more along the lines of what you're looking
for, since that protects the backend - and can cover both queries that have execution
complexity and those that simply return lots of rows.
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:37 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1596:
---------------------------------------
Graeme,
Based upon the previous comment, what needs to be done to resolve this JIRA?
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:31 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1596.
-----------------------------------
Resolution: Incomplete Description
There's been no update on this issue in three weeks. Marking as incomplete
description since it's not clear what if any enhancements that are not covered by
other JIRAs should be worked from this. Please reopen if needed.
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:37 p.m.
New subject: [JBoss JIRA] Closed: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1596.
---------------------------------
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:46 a.m.
New subject: [JBoss JIRA] Reopened: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Graeme Gillies reopened TEIID-1596:
-----------------------------------
Hi,
I'd like to re-open this issue, having thinking more about it I have a better set of
requirements.
At the moment, we need to ensure that for any user querying teiid, their query cannot run
longer than 180 seconds. This is to keep load low on our database server slaves (which
teiid points to) and ensure any big queries don't stall replication.
How we achieve this at the moment is, in each datasource we setup in jboss to point to
real databases, we set
{code}
<query-timeout>180</query-timeout>
{code}
In the datasource xml. This works, but is kind of ugly, as it closes the connection out
from under teiid (which throws a big exception, which isn't exactly clear to anyone
what exactly happened), and it seems to cause some problems as well with the connection
not being returned to the connection pool cleanly (though this may be another issue
altogether).
What we would like, is some sort of configuration option like maxSourceRows where we can
set in teiid itself, the maximum amount of time a query is allowed to execute for before
killing it cleanly in teiid, and throwing back a teiid exception with a message like
"Query took longer than X seconds to execute" or similar.
Let me know if you require any further information or clarification.
Regards,
Graeme
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Graeme Gillies updated TEIID-1596:
----------------------------------
Affects Version/s: 7.5
(was: 7.4)
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.5
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:20 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1596.
-----------------------------------
Resolution: Duplicate Issue
Marking as a dup, since there is an existing issue to cover server side timeouts
TEIID-1573
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.5
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:25 p.m.
New subject: [JBoss JIRA] (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
[
https://issues.jboss.org/browse/TEIID-1596?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1596.
---------------------------------
Document queryThresholdInSecs and allow functionality to ensure user
queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.5
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the
option queryThresholdInSecs does. The xml file states "Long running query threshold,
after which a alert can be generated by tooling if configured", what tooling is this
exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per
instance. Unfortunately this isn't flexible enough sometimes, and it would be better
if this option could be configured per VDB and per data role as well (some people can get
more data than others).
I would expect the determination of what maxSourceRows is for a query should be as
follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two
data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use
that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the
instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb,
instance, but also the setting queryThresholdInSecs, and either that option or another
option should be put in place that allows us to hard limit the length of time a query can
run. This is because in teiid we want to be able to say users cannot write a big huge
query that will take more than X amount of seconds to execute, to stop someone in teiid
giving it a huge query and hammering all the backend databases. Configuring this option by
vdb and data role (as some people are more trusted and can run longer queries) would be
fantastic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4601
days inactive
4782
days old
9 comments
3 participants
participants (3)
-
Graeme Gillies (JIRA) -
Steven Hawkins (Closed) (JIRA)
-
Steven Hawkins (JIRA)