You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2017/04/05 15:16:41 UTC

[jira] [Assigned] (IGNITE-4644) Value from IgniteQueue in atomic mode could be lost

     [ https://issues.apache.org/jira/browse/IGNITE-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Vinogradov reassigned IGNITE-4644:
----------------------------------------

    Assignee: Anton Vinogradov

> Value from IgniteQueue in atomic mode could be lost
> ---------------------------------------------------
>
>                 Key: IGNITE-4644
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4644
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.8
>            Reporter: Dmitry Karachentsev
>            Assignee: Anton Vinogradov
>
> Assume following case (operations are going concurrently):
> 1) Client1 -> offer. Add new index in queue.
> 2) On Client1 happens JVM pause or short-time problem with connectivity to cluster longer than 3 sec.
> 3) Client2 -> poll. Get index from cache, but no value available.
> 4) Client2 checks for value about 3 sec and if no value appears, just skips it.
> Should be fixed somehow or make timeout configurable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)