Wouter Bancken created IGNITE-14159:
---------------------------------------
Summary: IgniteSpiAdapter consistency check also logs warnings for
optional configurations
Key: IGNITE-14159
URL: https://issues.apache.org/jira/browse/IGNITE-14159
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Wouter Bancken
*Context*
We are using a setup with a server node and a thick client and since our
upgrade to Ignite 2.9.1 we always get the following notice when the thick
client joins the cluster:
{code:java}
>>> -------------------------------------------------------------------
>>> + Courtesy notice that joining node has inconsistent configuration. +
>>> + Ignore this message if you are sure that this is done on purpose. +
>>> -------------------------------------------------------------------
>>> Remote Node ID: ...
>>> Remote SPI with the same name is not configured: ...
>>> => Local node: ...
{code}
This notice is triggered because our custom CollisionSPI is not configured for
the thick client while it is configured for the server node since it does not
make sense to configure a CollisionSPI for a thick client.
*Cause*
This new behaviour is caused by commit
[https://github.com/apache/ignite/commit/0ef1debd2fc9452376a9e1ce36f0a9a945469783#diff-0511a13c0739b281c29879279241f4efe824249513527473de0f93674848d301]
Before Ignite 2.9.1 the warning was not logged since the SPI configuration is
optional.
The code in IgniteSpiAdapter explicitly mentions that the notice should not be
logged for optional configurations:
https://github.com/apache/ignite/blob/2d2044a63440e9b9d8495f35819ccee26d8324e4/modules/core/src/main/java/org/apache/ignite/spi/IgniteSpiAdapter.java#L515
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
