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

[jira] [Commented] (IGNITE-5100) Exchange queue is not used properly

    [ https://issues.apache.org/jira/browse/IGNITE-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012329#comment-16012329 ] 

ASF GitHub Bot commented on IGNITE-5100:
----------------------------------------

GitHub user zstan opened a pull request:

    https://github.com/apache/ignite/pull/1955

    IGNITE-5100 don`t remove active exchange events from exchange list

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-5100

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1955.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1955
    
----
commit f8157297707b30d6230e666752db3419b0a34b9f
Author: Evgeny Stanilovskiy <es...@gridgain.com>
Date:   2017-05-16T13:04:18Z

    IGNITE-5100 don`t remove active exchange events from exchange list

----


> Exchange queue is not used properly
> -----------------------------------
>
>                 Key: IGNITE-5100
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5100
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.6
>            Reporter: Alexei Scherbakov
>            Assignee: Stanilovsky Evgeny
>            Priority: Critical
>             Fix For: 2.1
>
>
> Currently exchange futures share same queue for pending(incomplete) and completed exchanges.
> The queue has fixed hardcoded size of 1000.
> This leads to a problem when > 1000 nodes try to enter grid.
> In such case oldest exchanges will be removed by ExchangeFutureSet size limit, leading to whole exchange hanging.
> Solution: 
> 1. Use separate queues for pending and completed exchanges.
> 2. Pending exchange queue must be unbounded.
> 3. Add system property to control exchange history.



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