[IGNITE-14532] Thin client: Unordered map used for putAll warning is unavoidable

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: thin client
• Ignite Flags: Release Notes Required
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Created: 13/Apr/21 17:01
• Updated: 07/Apr/23 06:58

Description

Thin client uses LinkedHashMap to preserve client-side entry order. Ignite logs a warning and there is no way to fix it for the user:

Unordered map java.util.HashMap is used for putAll operation on cache exact. This can lead to a distributed deadlock. Switch to a sorted map like TreeMap instead.

We should suppress this warning for thin client operations, since it does not make sense. Thin clients have different language-specific APIs, some of them don't even use maps. The same applies to PlatformCache (thick C# & C++).

We should have an internal method that does not produce a warning, and, ideally, does not require a Map. Using LinkedHashMap as an intermediate collection produces unnecessary overhead and allocations, we could use an array of key-value pairs instead.

Issue Links

• is duplicated by: IGNITE-18038 Error warning:“Unordered map java.util.LinkedHashMap is used for putAll operation on cache”
• relates to: IGNITE-13653 Don't print warning if unordered map used for bulk update operation on atomic cache