Hi Evgenii, Thanks for the quick response and clarification :)
Does this mean the C# client is looking at the collection provided to it and choosing treemap vs hashmap for an internal call to the Ignite Java layer based on whether the content of the collection provided is sorted? Thanks, Raymond. On Sat, Jun 13, 2020 at 2:23 AM Evgenii Zhuravlev <[email protected]> wrote: > The same works for other operations too(like removeAll). > > Evgenii > > пт, 12 июн. 2020 г. в 07:22, Evgenii Zhuravlev <[email protected]>: > >> Raymond, >> >> Collections used in putAll should be sorted, because otherwise if they >> have the same entries but in a different order, it can lead to the classic >> deadlock. It is expected behavior. >> >> Best Regards, >> Evgenii >> >> чт, 11 июн. 2020 г. в 21:38, Raymond Wilson <[email protected]>: >> >>> We are using Ignite v2.8.0 and the C# client. Some of our operations use >>> PutAll() to save a collection of items in a single operation. This >>> operation is emitting the following warning into the log: >>> >>> 2020-06-10 15:04:14,199 [77] WRN [ImmutableClientServer] >>> <Spatial-SubGridDirectory-Immutable> Unordered map java.util.HashMap is >>> used for putAll operation on cache Spatial-SubGridDirectory-Immutable. This >>> can lead to a distributed deadlock. Switch to a sorted map like TreeMap >>> instead. >>> >>> Does this require a Jira ticket? >>> >>> Thanks, >>> Raymond. >>> >>> >>> -- >>> <http://www.trimble.com/> >>> Raymond Wilson >>> Solution Architect, Civil Construction Software Systems (CCSS) >>> 11 Birmingham Drive | Christchurch, New Zealand >>> +64-21-2013317 Mobile >>> [email protected] >>> >>> >>> <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch> >>> >> -- <http://www.trimble.com/> Raymond Wilson Solution Architect, Civil Construction Software Systems (CCSS) 11 Birmingham Drive | Christchurch, New Zealand +64-21-2013317 Mobile [email protected] <https://worksos.trimble.com/?utm_source=Trimble&utm_medium=emailsign&utm_campaign=Launch>
