[
https://issues.apache.org/jira/browse/IGNITE-7608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456946#comment-16456946
]
Anton Vinogradov edited comment on IGNITE-7608 at 4/27/18 7:25 PM:
-------------------------------------------------------------------
[~SomeFire]
I see no difference between {{cache.withAutoSorting()}} and
{{putAll(Collections.sort(...))}}
Good idea is to solve problem only in case it happened.
My proposal is to detect and solve deadlock on {{putall()}} rather than sort
data each time.
What about timeout or something smarter? I'm pretty sure we can solve this
without sorting.
IGNITE-6895 proposing solution for simmilar problem.
This issue can become a part of
https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection
in that case.
was (Author: avinogradov):
[~SomeFire]
I see no difference between {{cache.withAutoSorting()}} and
{{putAll(Collections.sort())}}
Good idea is to solve problem only in case it happened.
Good approach is to detect and solve deadlock on {{putall()}} rather than sort
data each time.
What about timeout or something smarter? I'm pretty sure we can solve this
without sorting.
IGNITE-6895 proposing solution for simmilar problem.
This issue can become a part of
https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection
in that case.
> Sort keys in putAll/removeAll methods
> -------------------------------------
>
> Key: IGNITE-7608
> URL: https://issues.apache.org/jira/browse/IGNITE-7608
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.0, 2.1, 2.2
> Environment: We need to sort keys in cache putAll/removeAll
> operations to avoid deadlocks there.
> Reporter: Alexander Belyak
> Assignee: Ryabov Dmitrii
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
