You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2020/11/13 15:25:00 UTC
[jira] [Created] (IGNITE-13706) Thin Client Put_All uses
LinkedHashMap, causes warning and may deadlock
Ilya Kasnacheev created IGNITE-13706:
----------------------------------------
Summary: Thin Client Put_All uses LinkedHashMap, causes warning and may deadlock
Key: IGNITE-13706
URL: https://issues.apache.org/jira/browse/IGNITE-13706
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.9
Reporter: Ilya Kasnacheev
Thin client protocol handler for Put_All (1004) operation will create a linked hash map and then invoke putAll on this map.
This leads to couple of issues:
* Thin client may easily deadlock the cluster by issuing parallel transactional putAlls with different order of keys.
* "Unordered map with putAll" warning is printed to log, causing user confusion, even if client actually uses SortedMap with putAll().
What we really need is BinaryObject-aware SortedMap / making sure that keys/KeyCacheObjects are always comparable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)