Jeff,
All node attributes, including environment variables and classpath are
transmitted in discovery messages.
So try to create an environment, where your app won't have this irrelevant
information.
To check, what is included into the node attributes, you can use the
following code:
ClusterNode locNode = ignite.cluster().localNode();
for (Map.Entry<String, Object> e : locNode.attributes().entrySet())
System.out.println(e.getKey() + "=" + e.getValue());
> for the TCP window increasing, does Ignite has some attribute that we can
> configure?
or we may need to modify our production system.
Sorry, just ignore this recommendation. I figured out, that the size of
packages, that I see in your dump, depends on MTU network parameter. It's
better not to change it.
Denis
пт, 5 янв. 2018 г. в 6:18, Jeff Jiao <jeffjiaoyim...@gmail.com>:
> Hi Denis,
>
> Thanks for the analysis.
>
> Today we tried to reduce the Java class path(.../lib/*) when start a server
> node, but it still sends all the jar files(absolute path) to client.
>
> and we also find that, it looks like client node sends its info(path...) to
> server node, and then server node sends the client's info back to client
> again...
>
> for the TCP window increasing, does Ignite has some attribute that we can
> configure? or we may need to modify our production system.
>
> btw, we are using Ignite 2.3.0.
>
> Thanks,
> Jeff
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
