Hello! I've never seen anything like that and I recommend getting full thread dumps from all nodes in cluster if you ever see this again.
Regards, -- Ilya Kasnacheev вт, 17 дек. 2019 г. в 21:52, Mitchell Rathbun (BLOOMBERG/ 731 LEX) < [email protected]>: > We recently ran into an issue where we are hanging we attempting to > iterate through the results from IgniteCache.query. The basic code is as > follows: > > QueryCursor<Cache.Entry<Ts3SecurityCacheKey, Integer>> queryResults = > ts3KeysMetadataCache.query(new ScanQuery<>()); > > queryResults.forEach(e -> { > // Do stuff > }); > > Through debugging, it can be seen that we never reach the code in the > forEach statement or afterwards. It seems like somehow the data was > corrupted, since if we delete the work directory and restart the issue is > fixed. I tried getting a thread dump but it isn't super clear to me what > the issue is from looking at that. There are no blocked threads. Any idea > what could be causing this? Also, is there a configuration setting that > would cause the code above to eventually throw an exception instead of hang > forever? >
