Hi, Ilya!
I've fixed the flaky test.
Could you have a look?
Thank you!
чт, 7 нояб. 2019 г. в 17:12, Ilya Kasnacheev :
> Hello!
>
> When I run this test, each case takes 10-40 seconds of hardcore disk usage
> for some reason.
>
> Oops, sorry. I have just commented your ticket.
>
> Regards,
> --
>
Hello!
When I run this test, each case takes 10-40 seconds of hardcore disk usage
for some reason.
Oops, sorry. I have just commented your ticket.
Regards,
--
Ilya Kasnacheev
чт, 7 нояб. 2019 г. в 16:18, Denis Garus :
> >> but keep data in-memory?
>
> I don't use any data in tests for this i
>> but keep data in-memory?
I don't use any data in tests for this issue; only compute task.
>> I have commented JIRA with example of test failure.
Unfortunately, I don't see your comment in JIRA [1].
1. https://issues.apache.org/jira/browse/IGNITE-12300
чт, 7 нояб. 2019 г. в 15:45, Ilya Kas
Hello!
I can see that, but for some reason I can see a lot of disk I/O while
running this test. Is it possible to only use persistence for auth
purposes, but keep data in-memory?
I have commented JIRA with example of test failure.
Regards,
--
Ilya Kasnacheev
чт, 7 нояб. 2019 г. в 15:36, Denis
Hi, Ilya!
Thank you for the review!
> For some reason, when I run it locally, it starts to use persistence, do
> you have ideas why that would happen?
The reason is "Authentication can be enabled only for cluster with enabled
persistence." [1]
> It also seems to me that
>
org.apache.ignite.inte
Hello!
I will re-run tests against fresh master, and then commit if they pass.
For some reason, when I run it locally, it starts to use persistence, do
you have ideas why that would happen?
It also seems to me that
org.apache.ignite.internal.processors.security.compute.closure.ComputeTaskCancelR
Hello, Igniters!
I've raised the PR [1] for the issue [2].
Could somebody review it?
1. https://github.com/apache/ignite/pull/7017
2. https://issues.apache.org/jira/browse/IGNITE-12300
