[
https://issues.apache.org/jira/browse/IGNITE-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev updated IGNITE-4644:
----------------------------------------
Fix Version/s: (was: 2.0)
2.1
> 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
> Fix For: 2.1
>
>
> 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)
