Hi
I've found that heap size of client nodes used in total size of grid heap size: [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, 127.0.0.1, 192.168.100.10], sockAddrs=[ksm-homepc/169.254.90.143:0, /0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /192.168.100.10: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] 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. -- Sergey Kozlov |
It seems that we should write: servers-heap: xxGB, clients-heap: yyGB
On Fri, Sep 11, 2015 at 4:32 PM, Sergey Kozlov <[hidden email]> wrote: > Hi > > I've found that heap size of client nodes used in total size of grid heap > size: > > [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, > 127.0.0.1, 192.168.100.10], sockAddrs=[ksm-homepc/169.254.90.143:0, > /0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /192.168.100.10: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] > > 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. > > -- > Sergey Kozlov > -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
What's the reason to know total client heap size?
On Fri, Sep 11, 2015 at 1:59 PM, Alexey Kuznetsov <[hidden email]> wrote: > It seems that we should write: servers-heap: xxGB, clients-heap: yyGB > > On Fri, Sep 11, 2015 at 4:32 PM, Sergey Kozlov <[hidden email]> > wrote: > > > Hi > > > > I've found that heap size of client nodes used in total size of grid heap > > size: > > > > [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, > > 127.0.0.1, 192.168.100.10], sockAddrs=[ksm-homepc/169.254.90.143:0, > > /0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /192.168.100.10: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] > > > > 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. > > > > -- > > Sergey Kozlov > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > -- Sergey Kozlov |
On Fri, Sep 11, 2015 at 4:27 AM, Sergey Kozlov <[hidden email]> wrote:
> What's the reason to know total client heap size? > Even though the total client heap size is not as meaningful, since we are showing servers and clients in the log message, for consistency reasons I think it makes sense to show total allocated servers heap and clients heap. > On Fri, Sep 11, 2015 at 1:59 PM, Alexey Kuznetsov <[hidden email] > > > wrote: > > > It seems that we should write: servers-heap: xxGB, clients-heap: yyGB > > > > On Fri, Sep 11, 2015 at 4:32 PM, Sergey Kozlov <[hidden email]> > > wrote: > > > > > Hi > > > > > > I've found that heap size of client nodes used in total size of grid > heap > > > size: > > > > > > [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, > > > 127.0.0.1, 192.168.100.10], sockAddrs=[ksm-homepc/169.254.90.143:0, > > > /0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /192.168.100.10: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] > > > > > > 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. > > > > > > -- > > > Sergey Kozlov > > > > > > > > > > > -- > > Alexey Kuznetsov > > GridGain Systems > > www.gridgain.com > > > > > > -- > Sergey Kozlov > |
Free forum by Nabble | Edit this page |