[jira] [Created] (IGNITE-13304) Improve javadocs for classes related to cache configuration enrichment

Vyacheslav Koptilin created IGNITE-13304: Summary: Improve javadocs for classes related to cache configuration enrichment Key: IGNITE-13304 URL: https://issues.apache.org/jira/browse/IGNITE-13304

[jira] [Created] (IGNITE-13303) Update mockito from 1.10.19 to 3.x

Alexey Kuznetsov created IGNITE-13303: - Summary: Update mockito from 1.10.19 to 3.x Key: IGNITE-13303 URL: https://issues.apache.org/jira/browse/IGNITE-13303 Project: Ignite Issue Type:

Re: [DISCUSSION] Cache warmup

Hello Kirill, Thanks a lot for driving this activity. If I am not mistaken, this discussion relates to IEP-40. > I suggest adding a warmup phase after recovery here [1] after [2], before discovery. This means that the user's thread, which starts Ignite via Ignition.start(), will wait for ana

[jira] [Created] (IGNITE-13302) Java thin client connect/disconnect during topology update may lead to partition divergence in ignite-sys-cache

Stepachev Maksim created IGNITE-13302: - Summary: Java thin client connect/disconnect during topology update may lead to partition divergence in ignite-sys-cache Key: IGNITE-13302 URL:

[jira] [Created] (IGNITE-13301) IgniteScheduler has to run inside the Ignite Sandbox.

Denis Garus created IGNITE-13301: Summary: IgniteScheduler has to run inside the Ignite Sandbox. Key: IGNITE-13301 URL: https://issues.apache.org/jira/browse/IGNITE-13301 Project: Ignite

[DISCUSSION] Cache warmup

Now, after restarting node, we have only cold caches, which at first requests to them will gradually load data from disks, which can slow down first calls to them. If node has more RAM than data on disk, then they can be loaded at start "warmup", thereby solving the issue of slowdowns during

[jira] [Created] (IGNITE-13300) Ignite sandbox vulnerability allows to execute user code in privileged proxy

Aleksey Plekhanov created IGNITE-13300: -- Summary: Ignite sandbox vulnerability allows to execute user code in privileged proxy Key: IGNITE-13300 URL: https://issues.apache.org/jira/browse/IGNITE-13300

[jira] [Created] (IGNITE-13299) Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests.

Stanilovsky Evgeny created IGNITE-13299: --- Summary: Flacky GridServiceDeployClusterReadOnlyModeTest and all including tests. Key: IGNITE-13299 URL: https://issues.apache.org/jira/browse/IGNITE-13299

Re: Extended logging for rebalance performance analysis

Discussed in personal correspondence with Stas, decided to improve the message: Completed rebalancing [grp=grp0, supplier=3f2ae7cf-2bfe-455a-a76a-01fe27a1, partitions=2, entries=60, duration=8ms, bytesRcvd=5,9 KB, topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0],

Re: PDS suites fail with exit code 137

Hi Ivan P., I configured it for both PDS (Indexing) and PDS 4 (was asked by Nikita Tolstunov). It totally worked, not a single 137 since then. Occasional 130 will be fixed in [1], it has a different problem behind it. Now I'm trying to find someone who knows TC configuration better and will be