You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Philipp Shergalis (Jira)" <ji...@apache.org> on 2024/10/23 08:36:00 UTC
[jira] [Assigned] (IGNITE-23502) Long (100-300ms) read lock inserting a value under high load in aipersist
[ https://issues.apache.org/jira/browse/IGNITE-23502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philipp Shergalis reassigned IGNITE-23502:
------------------------------------------
Assignee: Philipp Shergalis
> Long (100-300ms) read lock inserting a value under high load in aipersist
> -------------------------------------------------------------------------
>
> Key: IGNITE-23502
> URL: https://issues.apache.org/jira/browse/IGNITE-23502
> Project: Ignite
> Issue Type: Bug
> Reporter: Philipp Shergalis
> Assignee: Philipp Shergalis
> Priority: Major
> Labels: ignite-3
>
> Under high load even inserting 1 value in aipersist we *sometimes* hold read lock for 100-300ms
> Can be reproduced running UpsertKvBenchmark on labs server, branch i{{{}gnite-22835-phil{}}} on 3ab6379da866fc5afac336bca53a6f4731025638 commit (just added some logging to branch ignite-22835-2)
>
> There are 123 entries in log for cases when we hold a lock for more than 100 ms. Examples:
> {code:java}
> [2024-10-18T10:07:12,109][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-6][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 145 IN handleUpdate
> [2024-10-18T10:07:12,518][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-12][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 123 IN handleUpdate
> [2024-10-18T10:07:12,518][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-16][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 123 IN handleUpdate
> [2024-10-18T10:07:12,518][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-1][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 121 IN handleUpdate
> [2024-10-18T10:07:12,518][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-2][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 122 IN handleUpdate
> Iteration 6: [2024-10-18T10:07:15,020][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-4][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 254 IN handleUpdate
> [2024-10-18T10:07:15,020][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-10][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 254 IN handleUpdate
> [2024-10-18T10:07:15,020][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-11][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 254 IN handleUpdate
> [2024-10-18T10:07:15,020][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-14][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 254 IN handleUpdate
> [2024-10-18T10:07:15,020][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-2][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 254 IN handleUpdate
> [2024-10-18T10:07:15,020][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-8][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 254 IN handleUpdate
> [2024-10-18T10:07:23,820][WARN ][org.apache.ignite.internal.benchmark.UpsertKvBenchmark.upsert-jmh-worker-5][PersistentPageMemoryMvPartitionStorage] LONG READ LOCK 188 IN handleUpdate{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)