Jeff, Your have indeed a lot of data sent over discovery. Almost all of it is taken by node attributes. Try reducing Java classpath and PATH environment variable. Also increasing of TCP window could help, because now a lot of small messages are sent instead of a few big ones.
Cross-sending it to dev list: Guys, turns out, we are sending a lot of irrelevant information in discovery messages. Some messages contain *TcpDiscoveryNode* objects, which in turn have such attributes like *PATH, java.class.path, sun.boot.class.path, java.library.path, org.apache.ignite.jvm.args, *etc. Some of these attributes may contain huge strings, that can sum up to megabytes of data. I think, we should filter-out such attributes, because they are not used anywhere, but make messages grow enormous and slow down discovery. What do you think? Denis чт, 4 янв. 2018 г. в 10:42, Jeff Jiao <[email protected]>: > dev2.cap < > http://apache-ignite-users.70518.x6.nabble.com/file/t757/dev2.cap> > > Hi Denis, > > the attachment is the packages that server transport to client when > connect, > we catched it using tool (Microsoft network monitor), can you please take a > look and see what you can find? > > we only configured 12 caches in our Ignite, most of them have 3 or 4 > indexes, only few has 7 or 8 indexes configured... > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
