New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
max_query_time
is not working correctly
#1427
Comments
It works properly when running query without where constraints, but with facets: For rt table:
For distributed table still worse than expected, but still better than was:
Profilling a query shows this:
|
There are also a significant lag for any status queries during this select. Time is lower for distributed index:
And is enormous while selecting a single rt index:
|
Also when running query on these index, I've played around with Maybe this will be related. |
for distributed table For the RT index it depends on amount of disk chunks and could not exceed some minimum value depends on setup time for every disk chunk. It could be better to retest your case with the master version to make sure that some points are fixed in the current version. |
Still, query with
Seems like it's not working either on 5.0.2:
Will |
the |
|
looking at However I'd check current |
Thank you very much @tomatolog Works as expected on version The only question left: any estimate when this versions will become stable so we could use them in prod?
|
6.2.12 is considered stable, it's the latest release - https://manual.manticoresearch.com/Changelog#Version-6.2.12 There's nothing more stable at the moment: the nightly build might have a few fixes, but it also has a few improvements that may be a source of unknown yet bugs. 6.2.12 is a maintenenance release with 12 bug fixes made after the release of 6.2.0 which in its turn was tested in a large Manticore installation for a few weeks before releasing. |
You could try |
Describe the bug
Seems like option max_query_time is not working at all.
If I understand correcly, this query should fail immediately, but is is running for 27 sec:
main is a distributed index, source - string attribute, which exists in all child indices.
It fails for single rt index too:
Expected behavior
max_query_time
should limit query execution time.Describe the environment:
Additional context
mysql> show create table person;
mysql> show table person status;
Note max_sec here is always <= 5 sec.
set profiling=1; select * from person where source='foo' option max_query_time=1; show profile;
The text was updated successfully, but these errors were encountered: