You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Dmitry Karachentsev (JIRA)" <ji...@apache.org> on 2017/02/02 09:16:06 UTC

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

Dmitry Karachentsev created IGNITE-4644:
-------------------------------------------

             Summary: 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


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 skip it.

Should be fixed somehow or make timeout configurable.



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