It is possible to implement a test plugin which will
override DiscoveryNodeValidationProcessor.
Also IMO it is better to start different Ignite versions in different
processes to avoid potential problems with custom classloaders (there is
already some helper classes for multi-jvm tests).
Thanks
Semen,
As far as I know, it is possible to allow nodes with different versions to
join topology.
Some products based on Ignite provides this feature.
We'd like to check that changes at Ignite will not break compatibility
feature of these products.
Could you provide some tips how to connect diffe
Hi Vyacheslav,
Currently Ignite nodes with different versions can not join the same
cluster, look at OsDiscoveryNodeValidationProcessor (this check is called
from discovery ServerImpl IgniteSpiContext.validateNode).
Thanks
On Wed, Jul 12, 2017 at 11:09 AM, Vyacheslav Daradur
wrote:
> Hi Ignite
Hi Igniters.
There is a need to test backward compatibility with previous release within
a task[1].
As far as I understand: it needs to provide methods in the
Ignite-test-framework to start instance of specific version of Ignite.
I popose to add such api in the project, for example: "Ignite
star
