You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ksenia Rybakova (JIRA)" <ji...@apache.org> on 2017/07/03 13:11:01 UTC
[jira] [Comment Edited] (IGNITE-3474) Grid hung during load test
with warning "Failed to wait for partition map exchange"
[ https://issues.apache.org/jira/browse/IGNITE-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072413#comment-16072413 ]
Ksenia Rybakova edited comment on IGNITE-3474 at 7/3/17 1:11 PM:
-----------------------------------------------------------------
[~sboikov] Semen,
I've checked scenario #2 with 20 clients and 64 servers - issue is still there.
New logs (version 1.8.8)
http://172.25.2.2/ftp/gg/load-tests/ignite/fosters/20170703-ignite-1.8.8-load-queries-16fed552-c20-s64-p50K-r2M-12caches-b1-d1h-FAILED_IGN-4662.zip
http://195.144.253.150:81/ftp/gg/load-tests/ignite/fosters/20170703-ignite-1.8.8-load-queries-16fed552-c20-s64-p50K-r2M-12caches-b1-d1h-FAILED_IGN-4662.zip
was (Author: krybakova):
[~sboikov] Semen,
I've checked scenario #2 with 20 clients and 64 servers - issue is still there.
New logs (version 1.8.8)
> Grid hung during load test with warning "Failed to wait for partition map exchange"
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-3474
> URL: https://issues.apache.org/jira/browse/IGNITE-3474
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.6
> Reporter: Ksenia Rybakova
> Assignee: Semen Boikov
> Priority: Critical
> Attachments: 132548_id2_172.25.1.33_part.log, ignite-base-load-config.xml, run-load.properties, run-load.xml
>
>
> During load test grid hung:
> {noformat}
> [09:22:17,688][WARN ][exchange-worker-#137%null%][GridCachePartitionExchangeManager] Failed to wait for partition map exchange [topVer=AffinityTopologyVersion [topVer=97, minorTopVer=0], node=0fe0c0f2-65e1-4ad5-a8c9-92db997fcb7d]. Dumpin
> g pending objects that might be the cause:
> ...
> {noformat}
> See attached file with more info from logs.
> Notes:
> The issue was also reproduced with IGNITE-3239 fixed. So, IGNITE-3239 doesn't seem to be a root cause.
> Configs:
> 1)
> - Benchmark name: IgniteCacheRandomOperationBenchmark
> - Operations: put, put_all, get, get_all, invoke, invoke_all, remove, remove_all, put_if_absent, replace
> - Heap: 4Gb for servers, 1Gb for clients
> - 80 clients, 20 servers, 8 hosts
> - Number of caches: 100
> - Preload amount 250K
> - Key range 500K
> - Types of caches (atomicity mode): different (atomic, transactional)
> - Types of caches (tiered storage mode): different (onheap without eviction, onheap with eviction, offheap_tired, offheap_values)
> - Types of caches (indexing): different (with and without indexes)
> - Types of caches (cache mode): different (partitioned, replicated)
> - Backups count: 1
> - Duration: 1h
> 2)
> - Benchmark name: IgniteCacheRandomOperationBenchmark
> - Operations: scan_query, sql_query, continuous_query
> - Heap: 4Gb for servers, 1Gb for clients
> - 20 clients, 80 servers, 8 hosts
> - Number of caches: 12
> - Types of caches (atomicity mode): different (atomic, transactional)
> - Types of caches (tiered storage mode): different (onheap without eviction, onheap with eviction, offheap_tired, offheap_values)
> - Types of caches (indexing): different (with and without indexes)
> - Types of caches (cache mode): different (partitioned, replicated)
> - Backups count: 1
> - Duration: 1h
> Attachments:
> - part of log with the problem (for one of the servers) for config #2
> - xml configs and property file that were used to run yardstick for config #2
> Complete logs can be provided on demand.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)