[ https://issues.apache.org/jira/browse/IGNITE-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Chetaev updated IGNITE-6108: ------------------------------------ Description: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Time for every 100_000_000 in seconds in log named "logs_without memory_policy". * 100_000_000 = 209 * 200_000_000 = 323 * 300_000_000 = 547 * 400_000_000 = 722 Yardstick logs in attachments. was: I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Time for every 100_000_000 in seconds in log named: * 100_000_000 = 209 * 200_000_000 = 323 * 300_000_000 = 547 * 400_000_000 = 722 Yardstick logs in attachments. > Hangs in streamer when using store > ---------------------------------- > > Key: IGNITE-6108 > URL: https://issues.apache.org/jira/browse/IGNITE-6108 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.1 > Reporter: Aleksey Chetaev > Priority: Critical > Attachments: logs_without memory_policy.zip, > log_with_memory_policy.zip > > > I have hangs in IgniteStreamer benchmarks when using store with WAL mode > different from NONE. > Configuration: 1 client 4 servers.Cache mode: transaction. Range > 400_000_000. > Problems: > * Time for next 100_000_000 entries every is always greater than for the > previous one. > * We can found hangs for greater that 1 minutes in drivers logs for example > 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". > Time for every 100_000_000 in seconds in log named "logs_without > memory_policy". > * 100_000_000 = 209 > * 200_000_000 = 323 > * 300_000_000 = 547 > * 400_000_000 = 722 > Yardstick logs in attachments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)