ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10032) Web Agent: Optimize collecting topology from cluster
Date Sat, 27 Oct 2018 16:19:00 GMT

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

ASF GitHub Bot commented on IGNITE-10032:

GitHub user akuznetsov-gridgain opened a pull request:


    IGNITE-10032 Web Agent: Optimized polling of cluster topology.


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

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

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


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

    This closes #5096
commit 4bd36a24b5588e2cbbfddab838b8b3b4cf11ecd6
Author: Alexey Kuznetsov <akuznetsov@...>
Date:   2018-10-27T16:15:24Z

    IGNITE-10032 Web Agent: Optimized polling of cluster topology.


> Web Agent: Optimize collecting topology from cluster
> ----------------------------------------------------
>                 Key: IGNITE-10032
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10032
>             Project: Ignite
>          Issue Type: Improvement
>          Components: wizards
>            Reporter: Alexey Kuznetsov
>            Assignee: Alexey Kuznetsov
>            Priority: Major
>             Fix For: 2.8
> In current implementation Web Agent collect every 5 seconds topology via REST with attributes.
But attributes are immutable and can be collected only when topology changed.
> We can cache node IDs and collect lightweight topology on every 5 seconds and if we detected
that topology changed - collect full topology with attributes. 

This message was sent by Atlassian JIRA

View raw message