The QUEUED field is a BIGINT that contains timestamp from System.currentTimeMillis(), so it should be pretty easy to sort, shouldn’t it? Looks like the field STATUS (used in where clause) and field QUEUED (used in order clause) are not working optimal when used together.
Hello!
ORDER BY will have to sort the whole table.
I think that using index on QUEUED will be optimal here. What is the
selectivity of this field? If it s boolean, you might as well use UNION
queries.
Have you tried joining JOBS via WHERE EXISTS?
Regards,
--
Ilya Kasnacheev
пт, 9 апр. 2021
Hello!
If this is your concern, I recommend switching from login/password to
certificate based authentication.
It is much stronger and uses encrypted files as is.
Regards,
--
Ilya Kasnacheev
чт, 8 апр. 2021 г. в 16:32, shivakumar :
> Hi Igniters,
> Does Ignite support reading the encrypted p
Hello!
What is the return code of the Java process?
I recommend checking dmesg output for OOMKiller messages. Seems to be a
popular failure mode these days.
Regards,
--
Ilya Kasnacheev
пт, 9 апр. 2021 г. в 11:58, rakshita04 :
> Hi Team,
>
> Do you have any update on this issue?
>
> regards,
Hi Team,
Do you have any update on this issue?
regards,
Rakshita chaudhary
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello, Alexandr!
The problem still actual, we deployed same 10 nodes on google kubernetes and
got a normal time.
For now we did not define any limits or requests, our ignite is the only
deployment on the kubernetes.
We use flannel network plugin (host-gw), are there any recommendations for
the net