[
https://issues.apache.org/jira/browse/IGNITE-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675206#comment-16675206
]
Stanislav Lukyanov commented on IGNITE-8486:
--------------------------------------------
OK, to wrap it up.
Though potentially beneficial, this change is also potentially dangerous. Since
we're not solving any particular known issues with this patch, it seems better
to be conservative and not apply it until we know it really helps some users.
Closing as Won't Fix for now and attaching the patch from the PR in case we
decide to apply it later.
> Update ConcurrentLinkedDeque in Ignite's master repository to the latest JDK
> version
> ------------------------------------------------------------------------------------
>
> Key: IGNITE-8486
> URL: https://issues.apache.org/jira/browse/IGNITE-8486
> Project: Ignite
> Issue Type: Improvement
> Reporter: Stanislav Lukyanov
> Assignee: Stanislav Lukyanov
> Priority: Major
> Fix For: 2.8
>
> Attachments: 3995[1].diff, jsr166-to-ignite.diff
>
>
> Ignite still uses copies of several JSR 166 (j.u.concurrent) classes in it's
> sources. Those copies are now outdated compared to the latest versions used
> in JDK.
> In particular, `ConcurrentLinkedDeque` has received a couple of correctness
> fixes recently (https://bugs.openjdk.java.net/browse/JDK-8188900,
> https://bugs.openjdk.java.net/browse/JDK-8189387). It would be good to have
> them in Ignite as well to protect ourselves from possible issues.
> The task is to update Ignite's `ConcurrentLinkedDeque8` to the latest version
> of `ConcurrentLinkedDeque`, although keeping compatibility with earlier Java
> version (e.g. JDK's version now uses Java 9's VarHandles which we can't use
> yet).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
