Stop Ignite opening 47500 and 47100

[karthik]

In our Project we are not allowed to open any port. Is it possible to disable
TcpDiscoveySpi and TcpCommunicationSpi . I use Ignite only on single node in
sever mode.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[Alexey Goncharuk]

Hi,

You can implement your own no-op discovery and communication SPIs and plug
them in IgniteConfiguration, then no network ports will be opened.

--AG

2017-11-17 16:05 GMT+03:00 karthik <[hidden email]>:

> In our Project we are not allowed to open any port. Is it possible to
> disable
> TcpDiscoveySpi and TcpCommunicationSpi . I use Ignite only on single node
> in
> sever mode.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[karthik]

I have been trying to implement my own discovery spi and communication spi.
But i am unable achieve it without errors. I just need Ignite Cache.
It will be helpful if you can you provide the code or at least mention what
classes and where i need to make changes.
Thanks in advance.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[Dmitriy Pavlov]

Hi, please see examples
in org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneNoopCommunicationSpi
and StandaloneNoopDiscoverySpi.

also please make sure classes are annotated @IgniteSpiNoop

This annotation helps Ignite ingernal stuff to identify this implementation
should be considered as stub.

Sincerely,
Dmitriy Pavlov

пн, 20 нояб. 2017 г. в 11:10, karthik <[hidden email]>:

> I have been trying to implement my own discovery spi and communication spi.
> But i am unable achieve it without errors. I just need Ignite Cache.
> It will be helpful if you can you provide the code or at least mention what
> classes and where i need to make changes.
> Thanks in advance.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>