Hi Jeff!
There is a workaround for the problem of huge discovery messages.
Try changing IgniteConfiguration.includeProperties
<https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#getIncludeProperties()>
parameter to an empty array. It will make Ignite filter out all environment
variables.
It should improve node connection time in your case.
Add the following lines to IgniteConfiguration in your XML:
<property name="includeProperties">
<array></array>
</property>
Denis
ср, 10 янв. 2018 г. в 11:37, Denis Mekhanikov <dmekhani...@gmail.com>:
> Hi Jeff.
>
> Looks like my letter wasn't noticed by the developer community.
>
> I sent a message to the dev list one more time:
> http://apache-ignite-developers.2346864.n4.nabble.com/Irrelevant-data-in-discovery-messages-td25927.html
>
> In the meanwhile make sure, that this is really the cause of the discovery
> process being slow. Try deploying nodes on the same environment, but
> without additional jar files on the classpath. Will it make discovery work
> faster?
>
> Denis
>
> ср, 10 янв. 2018 г. в 8:39, Jeff Jiao <jeffjiaoyim...@gmail.com>:
>
>> Hi Denis,
>>
>> Does Ignite dev team give any feedback for this?
>>
>> Thanks
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
