[
https://issues.apache.org/jira/browse/IGNITE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231567#comment-17231567
]
Ilya Kasnacheev commented on IGNITE-13706:
------------------------------------------
Also, OP_CACHE_PUT_ALL documentation never mentions anything about key sorting:
https://apacheignite.readme.io/docs/binary-client-protocol-key-value-operations#op_cache_put_all
Neither does org.apache.ignite.client.ClientCache#putAll javadoc.
> 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
> Priority: Major
>
> 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)
