ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shtykh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1476) Heap size in topology snapshot should be splitted into client and server heaps
Date Thu, 26 Nov 2015 06:12:10 GMT

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

Roman Shtykh commented on IGNITE-1476:

How about splitting CPUs too?
Topology snapshot [ver=1, servers=2(CPUs=2, heap=4.0GB), clients=0(CPUs=0, heap=0GB)]
Added new node to topology: ...
Topology snapshot [ver=2, servers=2(CPUs=2, heap=4.0GB), clients=1(CPUs=2, heap=2.0GB]

> Heap size in topology snapshot should be splitted into client and server heaps
> ------------------------------------------------------------------------------
>                 Key: IGNITE-1476
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1476
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Sergey Kozlov
> I've found that heap size of client nodes used in total size of grid heap size:
> {noformat}
> [11:35:56,444][INFO][main][GridDiscoveryManager] Topology snapshot [ver=4, servers=4,
clients=0, CPUs=4, heap=8.0GB]
> [11:36:04,556][INFO][disco-event-worker-#45%null%][GridDiscoveryManager] Added new node
to topology: TcpDiscoveryNode [id=3cc4213b-b4a7-4f45-88b3-07cbdc3488b6, addrs=[0:0:0:0:0:0:0:1,,], sockAddrs=[ksm-homepc/, /0:0:0:0:0:0:0:1:0, /,
/], discPort=0, order=5, intOrder=5, lastExchangeTime=1441960564491, loc=false,
ver=1.4.0#20150910-sha1:071586e2, isClient=true]
> [11:36:04,558][INFO][disco-event-worker-#45%null%][GridDiscoveryManager] Topology snapshot
[ver=5, servers=4, clients=1, CPUs=4, heap=9.0GB]
> {noformat}
> But really only server nodes heap used for a grid and it might confuse the user for available
heap on grid if a topology has a few server nodes and many clients.

This message was sent by Atlassian JIRA

View raw message