Sascha, Ignite does not allow disable discovery. You can configure discovery SPI, in order to assign different ip-addresses and ports for different nodes.
I see, to implement discovery SPI is one of a way to do as you wanted. On Mon, Aug 22, 2016 at 12:09 AM, SaschaC <[email protected]> wrote: > Hi, > > I've been trying to find out how I can put Ignite into a single-node mode, > but I cannot find any information on how to do that. > > My usecase is that I only need to use a local cache in Ignite. I'm > integrating ignite into another product which runs on a cluster and Ignite > is being started in-process on each of the product's nodes, but each Ignite > process should exist in isolation. I don't want the ignite processes to try > to find one-another. > > I could write my own discovers SPI that does nothing but there must be an > easier way. It seems Ignite is forcing me into a clustered setup which is > kind of weird. Running ignite on a single node in a standalone setup should > be the hello-world scenario and yet I don't seem to be able to find any > info > on this. To be clear, I'm not looking for a hack, but a clean way of doing > this. Don't want Ignite to make any attempts at performing any kind of > network activities. > > Thanks > Sascha > > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Howto-setup-a-single-node- > standalone-Ignite-tp7197.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
