I've merged TcpDiscoverySpi and TcpClientDiscoverySpi, now only TcpDiscoverySpi is preset. TcpDiscoverySpi will work in client mode if IgniteConfiguration.isClientMode == true. If you want to start TcpDiscoverySpi in server mode regardless of IgniteConfiguration.isClientMode you can set TcpDiscoverySpi.setForceServerMode(true)
On Mon, May 25, 2015 at 9:14 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > On Mon, May 25, 2015 at 8:20 AM, Yakov Zhdanov <yzhda...@apache.org> > wrote: > > > Why do we need separate SPI class instead of mode in current TCP > discovery? > > > > I also don't like separate SPI for client-based discovery. Can anyone share > why it is an SPI rather than just a configuration property? Moreover, it > seems like the configuration properties for the client-based and > server-based discovery SPIs will be the same, which makes a separate SPI > even more redundant. > > How big of a change is it at this juncture? > > D. >
